paperclip

Orchestrate Paperclip control plane actions and task state changes via API.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Paperclip coordination requires secure, auditable API-driven control to manage tasks and governance, while not executing domain work.

Core Features & Use Cases

  • Heartbeat-driven coordination: wake on light-weight tasks and coordinate with agents.
  • Checkout, context reading, and update flow: manage blockers, wakeups, and issue state changes with proper tracing.
  • Context-aware decisions: read heartbeat context, handle approvals and blocker dependencies, and post linked comments.

Quick Start

Invoke a heartbeat that checks assignments, performs a checkout for the selected issue, and posts a concise status update comment.

Frequently Asked Questions about paperclip

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

FAQPage Schema
How do I coordinate task state changes and governance via API without executing domain work?

Task state changes are orchestrated via API to manage control plane actions safely, handling approvals, blockers, and tracing without performing direct domain work.

What's the best way to manage heartbeat-driven task coordination for agents?

Heartbeat-driven coordination wakes on lightweight tasks to check assignments, read context, and coordinate with agents, ensuring proper tracing and auditable interactions.

How do I perform a checkout and post a status update comment for an issue?

Invoke a heartbeat to check assignments, perform a checkout for the selected issue, read context, and post a concise status update comment with proper tracing.

Can I handle approval workflows and blocker dependencies through task management APIs?

Yes, context-aware decisions read heartbeat context to handle approvals and blocker dependencies, enforcing safe, auditable interactions including retries and run-ids.

Does this approach support safe retries and run-id tracing for execution-state decisions?

Execution-state decisions enforce safe, auditable interactions including blockers, retries, and run-ids, ensuring proper tracing across issues and approvals.

When should I avoid direct domain work during API governance orchestration?

Avoid direct domain work when coordinating control plane actions, as the focus remains on managing task state changes, heartbeats, and governance safely via API.