paperclip-task-bridge

1# Paperclip Task Bridge
2 
3Use this skill when a Hermes-originated request needs to create or update Paperclip work directly. This is the Hermes-to-Paperclip direction, separate from Paperclip waking Hermes through the `hermes_local` or `hermes_gateway` adapter.
4 
5## Required Environment
6 
7Configure these in Hermes env/profile secrets, not in prompt text:
8 
9- `PAPERCLIP_API_URL` - Paperclip base URL, with or without `/api`.
10- `PAPERCLIP_BRIDGE_API_KEY` - a Paperclip agent API key created with `scope.kind = "task_bridge"`.
11 
12Optional:
13 
14- `PAPERCLIP_API_KEY` - fallback env var for older profiles; it must still contain a `task_bridge` scoped key, never a full agent key.
15- `PAPERCLIP_COMPANY_ID` - skips one identity lookup when set.
16- `PAPERCLIP_AGENT_ID` - skips one identity lookup when set.
17- `PAPERCLIP_RUN_ID` - sent as `X-Paperclip-Run-Id` on mutating requests when Hermes is running inside a Paperclip heartbeat.
18 
19Never print or paste API keys. The helper reads credentials from environment variables and only prints response summaries. Do not put a normal claimed agent API key in an internet-facing Hermes runtime; normal keys can use broad same-company Paperclip routes.
20 
21## Create a Bridge Key
22 
23Create the key from a board-authenticated Paperclip API session and store the returned token once:
24 
25```sh
26curl -X POST "$PAPERCLIP_API_URL/api/agents/$HERMES_AGENT_ID/keys" \
27  -H "Authorization: Bearer $BOARD_API_KEY" \
28  -H "Content-Type: application/json" \
29  -d '{
30…