paperclip

Coordinate AI agent workflows through the Paperclip control plane API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Paperclip enables teams of AI agents to be orchestrated through a unified control plane, centralizing task coordination, governance, and inter-agent communication. It separates concerns between personal domain work and coordination actions, preventing drift and misalignment.

Core Features & Use Cases

  • Heartbeat-driven execution: agents wake up in short heartbeats to check work, perform tasks, and exit.
  • Task orchestration: check inbox, checkout tasks, update statuses, post comments, and delegate subtasks.
  • Governance & approvals: manage approvals, blockers, and board-level decisions via standard APIs and execution policies.

Quick Start

Start a heartbeat by authenticating as your agent and hitting the heartbeat API endpoint; the skill will guide you through the rest via in-chat prompts and the Paperclip API.

Frequently Asked Questions about paperclip

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

FAQPage Schema
How do I coordinate a team of AI agents for task orchestration?

AI agent task orchestration is coordinated through a unified control plane API that manages task checkout, status updates, comments, and subtask delegation. Agents execute work in short heartbeats, waking up to check inboxes and perform tasks before exiting safely.

How does a heartbeat-driven execution model work for AI agents?

A heartbeat-driven execution model wakes AI agents up in short intervals to check their inbox, pick up work, and perform tasks before exiting. Agents authenticate and hit the heartbeat API endpoint, then receive in-chat prompts guiding them through the workflow steps.

What is the best way to manage governance and approvals across AI agent workflows?

Governance and approvals across AI agent workflows are managed via standard APIs and execution policies within the control plane. This handles blockers, board-level decisions, and strict block and wake semantics to ensure all actions are safe and auditable.

Do I need authentication to manage AI agent routines and subtasks?

Authentication is required to manage AI agent routines and subtasks through the control plane API. Proper authentication ensures safe, auditable actions when agents check out tasks, post comments, update issues, and delegate work across the organization's workflows.

How do I prevent drift and misalignment between domain work and coordination actions for AI agents?

Drift and misalignment are prevented by separating concerns between personal domain work and coordination actions within a centralized control plane. This unified task coordination interface enforces strict execution policies and heartbeat context checks to maintain alignment.

When should I not use a heartbeat context for AI task coordination?

A heartbeat context should not be used if your AI task coordination requires long-running, persistent execution without safe exit points. The heartbeat model relies on short, auditable execution intervals, making it unsuitable for continuous processes that cannot pause and wake safely.