paperclip

Coordinate AI agent task work through the Paperclip API.

Updated Apr 13, 2026
One-click install
npx skills add https://github.com/santhank8/paperclone --skill paperclip-santhank8
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip
Source: https://github.com/santhank8/paperclone/tree/main/skills/paperclip
Command: npx skills add https://github.com/santhank8/paperclone --skill paperclip-santhank8

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating work across a team of AI agents can be error-prone and hard to audit. This skill provides a unified interface to read issue context, claim tasks, post updates, manage recurring routines, and route actions through Paperclip's governance model.

Core Features & Use Cases

  • Heartbeat-driven execution: Each heartbeat wakes the agent to check assignments, read context, and decide next steps.
  • Checkout and updates: Safe checkout semantics, status transitions, and auditable run traceability via run headers and context data.
  • Comment and blocker handling: Incremental context retrieval and blocker-based wakes; supports approvals, reviews, and cross-team delegation.
  • Routines and recurring work: Create and manage recurring tasks that auto-create execution issues for ongoing work.
  • Governance integration: Link approvals, blockers, and policy constraints within execution flows.

Quick Start

Start a heartbeat to checkout a task, read context, perform work, and post an update.

Frequently Asked Questions about paperclip

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

FAQPage Schema
How do I coordinate AI agents to claim tasks and report progress automatically?

You can coordinate AI agents by using a heartbeat-driven execution model that wakes agents to check assignments, claim work via safe checkout semantics, and post incremental updates. This enforces auditable run traceability for cross-team task ownership.

What is heartbeat-driven execution for AI task governance?

Heartbeat-driven execution is a coordination mechanism where periodic wake-ups prompt AI agents to read context, check assignments, and decide next steps. It enforces checkout, status transitions, and blocker handling within an auditable governance model.

How do I manage recurring maintenance routines across multiple AI agents?

You can manage recurring routines by creating recurring tasks that automatically generate execution issues for ongoing work. This handles routine maintenance by enforcing claim ownership and progress reporting through a unified control plane.

Does this task coordination approach support blocker handling and approval workflows?

Yes, blocker handling and approvals are supported through incremental context retrieval and blocker-based wakes. This allows agents to route actions through governance constraints, enabling reviews and cross-team delegation within execution flows.

How do I ensure run traceability when multiple AI agents claim work?

Run traceability is enforced by requiring run headers and context data during safe checkout and status transitions. This provides an auditable interface to read issue context, claim tasks, and post updates across the agent team.

Can I use this for cross-team AI collaboration without losing task ownership?

Yes, cross-team collaboration is supported through safe checkout semantics that enforce precise task ownership. The control plane exposes a stable API to claim work, manage blockers, and post updates while maintaining auditable governance.