paperclip

Manage Paperclip control plane tasks and coordinate agent assignments via JSON endpoints.

6|1|Updated Apr 7, 2026
One-click install
npx skills add https://github.com/kmshihab7878/claude-code-setup --skill paperclip-kmshihab7878
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: paperclip
Source: https://github.com/kmshihab7878/claude-code-setup/tree/main/skills/paperclip
Command: npx skills add https://github.com/kmshihab7878/claude-code-setup --skill paperclip-kmshihab7878

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Provides a governed, repeatable interface for agents to interact with the Paperclip control plane so tasks are claimed, progressed, delegated, and closed reliably during short heartbeat runs without human error or improper ownership changes.

Core Features & Use Cases

  • Heartbeat workflow: wake, inspect inbox, prioritize, checkout, perform work, update status, and exit on each run.
  • Governance & safety: enforces checkout before work, mandates X-Paperclip-Run-Id on mutating requests, and prescribes blocked-task dedup and escalation rules.
  • Task operations: read assignments, fetch heartbeat context and comments incrementally, create subtasks, delegate, manage routines, and perform company skill imports.
  • Project and company flows: supports project setup, OpenClaw invite prompt generation, company skill imports, and CEO/manager approval follow-ups.

Quick Start

Wake the agent, read your inbox and any triggering comment, checkout the assigned issue, perform the assigned work, and update the issue with a comment and the run id header.

Frequently Asked Questions about paperclip

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

FAQPage Schema
How do I coordinate agent task assignments during heartbeat runs?

Agent task coordination during heartbeat runs is managed by checking assignments, checking out issues, performing work, and updating task status. This enforces proper ownership and mandates the X-Paperclip-Run-Id header on all mutating API requests.

What is the required workflow for checking out and updating control plane tasks?

Checking out control plane tasks requires waking the agent, reading the inbox, checking out the assigned issue, performing the work, and posting a comment with the run ID header. This governed workflow prevents improper ownership changes.

Do I need specific environment variables to authenticate agent task management requests?

Yes, agent task management requires PAPERCLIP_* environment variables for authentication. Without these variables configured, control plane interactions and task delegation requests cannot be authorized.

Can I create subtasks and delegate work to other agents within a heartbeat cycle?

Yes, you can create subtasks, delegate assignments, and manage routines within a heartbeat cycle. The workflow supports fetching context incrementally and posting comments to coordinate agent work reliably.

Why does my task status update fail when mutating control plane issues?

Task status updates fail when mutating control plane issues if the X-Paperclip-Run-Id header is missing. Mandating this header on mutating API requests ensures governed, repeatable ownership changes during heartbeat runs.

How do I handle blocked tasks and escalation in an agent coordination workflow?

Blocked tasks in an agent coordination workflow are handled using prescribed dedup and escalation rules. The workflow enforces checkout before work begins, ensuring blocked issues are escalated properly without human error.