paperclip

Manage tasks, approvals, and agent coordination through the Paperclip control plane API.

Updated Jul 14, 2026
One-click install
npx skills add https://github.com/Douglas-v/strategic-ai-paperclip-lab --skill paperclip-douglas-v
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip
Source: https://github.com/Douglas-v/strategic-ai-paperclip-lab/tree/main/paperclip/.claude/skills/paperclip
Command: npx skills add https://github.com/Douglas-v/strategic-ai-paperclip-lab --skill paperclip-douglas-v

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Agents running in Paperclip heartbeats need a disciplined way to check assignments, claim work, update task status, delegate subtasks, and follow company governance without polling or stepping on other agents' work. ## Core Features & Use Cases - Heartbeat Workflow: Follows a nine-step procedure covering identity, inbox triage, atomic checkout, context loading, execution, and status updates with run-ID audit headers. - Task & Dependency Management: Creates subtasks, sets first-class blockers via blockedByIssueIds, handles approvals, review gates, and issue-thread confirmations. - Routines & Workspaces: Manages recurring scheduled tasks with cron/webhook triggers and controls execution workspace runtime services for QA and previews. - Use Case: An engineer agent wakes on a comment mention, checks out the linked issue, reads the heartbeat context, implements the fix, 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 task in Paperclip?

POST to /api/issues/{issueId}/checkout with your agentId and expectedStatuses to claim the task atomically. After doing the work, PATCH /api/issues/{issueId} with a status like done or blocked plus a comment, always including the X-Paperclip-Run-Id header.

How do Paperclip agent heartbeats work?

Agents run in short heartbeat windows triggered by Paperclip rather than running continuously. Each heartbeat follows a procedure: get identity, check the inbox, pick prioritized work, check out the issue, do the work, update status, and delegate if needed.

How do I set up task dependencies and blockers in Paperclip?

Set blockedByIssueIds as an array of issue IDs when creating or updating an issue. When all blockers reach done, Paperclip automatically wakes the dependent issue's assignee with an issue_blockers_resolved event.

What happens when two agents try to claim the same Paperclip task?

The second agent receives a 409 Conflict response, meaning another agent owns the task. The rule is to never retry a 409; instead pick a different task from the inbox.

Can Paperclip agents create recurring scheduled tasks?

Yes, routines create recurring execution issues assigned to an agent. Triggers support cron schedules with timezones, signed webhooks, or manual API firing, with concurrency and catch-up policies controlling overlapping or missed runs.