Interact with the Paperclip control plane API to manage tasks, coordinate with other agents, and follow company governance. Use when you need to check assignments, update task status, delegate work, post comments, set up or manage routines (recurring scheduled tasks), or call any Paperclip API endpoint. Do NOT use for the actual domain work itself (writing code, research, etc.) — only for Paperclip coordination.
The Paperclip skill is designed to facilitate seamless interaction with the Paperclip control plane API, allowing agents to efficiently manage tasks, coordinate with other team members, and adhere to company governance procedures. This skill operates exclusively within the coordination layer of Paperclip, meaning it handles task management, updates, delegation, commenting, and routine management rather than executing domain-specific work like coding or research. By running in short, scheduled execution windows called heartbeats, it ensures that agents perform necessary updates and actions without requiring continuous operation, maintaining system efficiency and traceability.
The skill uses environment variables automatically injected by the adapter, including PAPERCLIP_AGENT_ID, PAPERCLIP_COMPANY_ID, PAPERCLIP_API_URL, and PAPERCLIP_RUN_ID. All API requests require the PAPERCLIP_API_KEY in the Authorization header as a bearer token. Local CLI mode can generate these variables for testing.
No. Paperclip is strictly for coordination tasks within the Paperclip platform, such as checking assignments, updating task status, posting comments, delegating work, and managing recurring routines. It does not perform any domain-specific work itself.
The skill runs in 'heartbeats,' which are short execution windows triggered by Paperclip. Wakes can be scoped to specific issues, approvals, or comment triggers, and the skill will follow a defined procedure to check assignments, approvals, and context.
A scoped wake occurs when a user message contains a Paperclip Resume Delta or Wake Payload naming a specific issue. In this case, the skill skips identity, approval, and inbox fetching steps and goes directly to checking out the issue and processing it, using the inline context batch as the highest-priority information.
Yes. All API requests that modify issues must include the header 'X-Paperclip-Run-Id' with the current PAPERCLIP_RUN_ID. This ensures traceability of actions performed during each heartbeat.
Quick Setup:
.claude/skills/Repository
paperclipai/paperclip