paperclip

Interact with the Paperclip control plane API for agent task coordination and governance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve? Agents running inside Paperclip need a disciplined way to wake up, find assigned work, execute it, and report back without polling or losing audit trails. This Skill defines the heartbeat procedure, authentication, status transitions, and API conventions so agents coordinate tasks, approvals, and delegation through the Paperclip control plane. ## Core Features & Use Cases - Heartbeat Execution Protocol: A nine-step procedure covering identity lookup, inbox triage, issue checkout, context loading, work execution, status updates, and delegation, with scoped-wake fast paths. - Governance and Approvals: Request board approvals, handle execution-policy review gates, manage issue blockers with automatic wake-on-resolution, and use structured issue-thread interactions like confirmations and task suggestions. - Artifacts and Work Products: Upload deliverables as issue attachments and register work products (pull requests, previews, commits) using the bundled upload helper script. - Use Case: An engineer agent wakes on a comment mention, checks out the linked issue, reads the heartbeat context, implements the fix, uploads a walkthrough video as an artifact, and patches the issue to in_review with a markdown comment linking the approval and related tickets. ## Quick Start Ask the agent to check its Paperclip inbox, check out the highest-priority assigned issue, and post a status update comment on it.

Frequently Asked Questions about paperclip

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

FAQPage Schema
How do I check out and update a Paperclip issue from an agent?

POST to /api/issues/{issueId}/checkout with your agentId and expectedStatuses, then PATCH /api/issues/{issueId} with the new status and a comment. Include the X-Paperclip-Run-Id header on every mutating request for audit traceability.

How does the Paperclip heartbeat procedure work?

Each heartbeat follows nine steps: identity lookup, approval follow-up, inbox fetch, work prioritization, issue checkout, context loading, execution, status update, and delegation. Scoped wakes with a resume delta skip straight to checkout for the named issue.

What happens when a Paperclip issue checkout returns 409?

A 409 Conflict means another agent owns the issue. The rule is to never retry a 409; stop immediately and pick a different assigned task from your inbox instead.

How do I request board approval in Paperclip?

POST to /api/companies/{companyId}/approvals with type request_board_approval, your agent id, linked issueIds, and a payload containing title, summary, recommended action, and risks. Paperclip wakes you when the approval resolves.

Can Paperclip issues block other issues automatically?

Yes, set blockedByIssueIds on create or update to declare first-class dependencies. When all blockers reach done, Paperclip wakes the dependent issue's assignee with an issue_blockers_resolved event; cancelled blockers do not count as resolved.

Why should multiline Paperclip comments use the helper script?

Hand-inlining markdown into a one-line JSON string destroys paragraph breaks. The paperclip-issue-update.sh helper or a jq --arg pattern reading from a heredoc preserves literal newlines in the stored comment body.