paperclip-task-bridge
starsforks
How to install paperclip-task-bridge?
getpaperclipai/paperclip/paperclip-task-bridge
$npx -y skills add getpaperclipai/paperclip --skill paperclip-task-bridgeCreate, comment on, update, and list Paperclip tasks from Hermes using scoped Paperclip API credentials.
SKILL.md
| 1 | # Paperclip Task Bridge |
| 2 | |
| 3 | Use 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 | |
| 7 | Configure 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 | |
| 12 | Optional: |
| 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 | |
| 19 | Never 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 | |
| 23 | Create the key from a board-authenticated Paperclip API session and store the returned token once: |
| 24 | |
| 25 | ```sh |
| 26 | curl -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 | "name": "Hermes task bridge", |
| 31 | "scope": { |
| 32 | "kind": "task_bridge", |
| 33 | "parentIssueId": "00000000-0000-4000-8000-000000000000" |
| 34 | } |
| 35 | }' |
| 36 | ``` |
| 37 | |
| 38 | Use `parentIssueId` or `parentIssueIds` when Hermes should only create child tasks under approved work. Use `projectId` or `projectIds` when the approved boundary is a project. A bridge key can create tasks only inside that boundary, can comment/update only bridge-created or assigned issues, and cannot use company-wide issue list/search/read surfaces. |
| 39 | |
| 40 | ## Helper |
| 41 | |
| 42 | Run the helper from this skill directory: |
| 43 | |
| 44 | ```sh |
| 45 | node ./paperclip-task.mjs --help |
| 46 | ``` |
| 47 | |
| 48 | Commands: |
| 49 | |
| 50 | ```sh |
| 51 | node ./paperclip-task.mjs list-assigned |
| 52 | node ./paperclip-task.mjs create-task --parent-id "00000000-0000-4000-8000-000000000000" --title "Investigate checkout failures" --description "Capture failing request and root cause." |
| 53 | node ./paperclip-task.mjs comment --issue PAP-123 --body "Found the failing request path." |
| 54 | node ./paperclip-task.mjs update-status --issue PAP-123 --status in_review --comment "Ready for review." |
| 55 | ``` |
| 56 | |
| 57 | `create-task` defaults to assigning the task to the authenticated Hermes agent so the work is immediately actionable. Use `--unassigned` to create backlog work instead. Use `--assignee-agent-id <uuid>` only when the Paperclip API key has permission to assign work to that agent. |
| 58 | |
| 59 | For multiline bodies, prefer files or stdin: |
| 60 | |
| 61 | ```sh |
| 62 | node ./paperclip-task.mjs create-task --title "Write rollout note" --description-file ./task.md |
| 63 | node ./paperclip-task.mjs comment --issue PAP-123 --body-file - |
| 64 | ``` |
| 65 | |
| 66 | ## Workflow Expectations |
| 67 | |
| 68 | - Keep tasks company-scoped by using the company resolved from the scoped agent key. |
| 69 | - Let Paperclip activity logging come from the normal API endpoints; do not write local logs that include credentials. |
| 70 | - Use comments for durable progress. |
| 71 | - Use `update-status` only when the issue has a real disposition: `done`, `in_review`, `blocked`, `todo`, `in_progress`, `backlog`, or `cancelled`. |
| 72 | - Use `list-assigned` before creating duplicate work when the user asks about current Paperclip assignments. |
People who liked this also viewed
6 picksType
- paperclip-create-agentCreate new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hSkillsJul 2026
- subagent-driven-developmentUse when executing implementation plans with independent tasks in the current sessionSkillsJul 2026
- dispatching-parallel-agentsUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesSkillsJul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later. Use when: user wants a reusable Skill for any website, needs to understand a sitSkillsJul 2026
- wizardGenerate an interactive bash wizard that walks a human through a manual procedure — third-party setup, a one-off migration, an A→B state transition — opening URLs, capturing values, confirming each stSkillsJul 2026
- wonda-cliUsing the Wonda CLI to generate images, videos, music, and audio from the terminal — plus LinkedIn, Reddit, and X/Twitter research and automationSkillsJul 2026
