paperclip-task-bridge

Create, comment on, update, and list Paperclip tasks from Hermes via scoped API keys.

Updated Jun 16, 2026
One-click install
npx skills add https://github.com/adamtpang/summon.company --skill paperclip-task-bridge-adamtpang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip-task-bridge
Source: https://github.com/adamtpang/summon.company/tree/main/packages/adapters/hermes/skills/paperclip-task-bridge
Command: npx skills add https://github.com/adamtpang/summon.company --skill paperclip-task-bridge-adamtpang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Hermes agents need a controlled way to create and update Paperclip work items without holding a full agent API key that grants broad company-wide access. This Skill bridges Hermes to the Paperclip API using narrowly scoped task_bridge credentials. ## Core Features & Use Cases - Scoped Task Creation: Create Paperclip issues under approved parent issues or projects using a task_bridge scoped API key, with priority, status, work mode, and assignee options. - Comment and Status Updates: Post durable progress comments and transition issues through statuses like in_progress, in_review, blocked, or done. - Assignment Listing: Run list-assigned to check current Paperclip assignments before creating duplicate work. - Use Case: A Hermes agent investigating checkout failures creates a child task under an approved parent issue, comments with findings, and moves the issue to in_review when finished. ## Quick Start Set PAPERCLIP_API_URL and PAPERCLIP_BRIDGE_API_KEY in your Hermes environment, then ask the agent to create a Paperclip task titled "Investigate checkout failures" under your approved parent issue.

Frequently Asked Questions about paperclip-task-bridge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I create a Paperclip task from Hermes?

Run node ./paperclip-task.mjs create-task with --title and optional --description, --parent-id, --priority, and --status flags. The task defaults to being assigned to the authenticated Hermes agent; use --unassigned for backlog work.

What API key does the Paperclip task bridge require?

It requires a Paperclip agent API key created with scope.kind set to task_bridge, passed via PAPERCLIP_BRIDGE_API_KEY. A full agent key must never be used in an internet-facing Hermes runtime because it grants broad company-wide route access.

How do I create a scoped task_bridge API key?

POST to /api/agents/{agentId}/keys from a board-authenticated session with a scope object containing kind task_bridge plus parentIssueId or projectId boundaries. Store the returned token once, since it cannot be retrieved later.

Can the bridge key access all Paperclip issues?

No. A task_bridge key can only create tasks inside its approved parent or project boundary and can only comment on or update bridge-created or assigned issues. It cannot use company-wide issue list, search, or read surfaces.

How do I update a Paperclip issue status from the command line?

Run node ./paperclip-task.mjs update-status with --issue and --status set to one of backlog, todo, in_progress, in_review, done, blocked, or cancelled. Add --comment or --comment-file to attach a progress note with the transition.

Why does the helper fail with a missing environment variable error?

The helper exits with a usage error when PAPERCLIP_API_URL or PAPERCLIP_BRIDGE_API_KEY is unset. Configure both in the Hermes env or profile secrets, and optionally set PAPERCLIP_COMPANY_ID and PAPERCLIP_AGENT_ID to skip identity lookups.