Agent skill · marketing growth · aiskillstore
paperclip
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.
Why this skill is useful
Provides specific API commands and workflows for managing tasks within the Paperclip control plane that the AI wouldn't reliably generate on its own.
What it needs
Requires pnpm installed locally. Requires paperclip account access. About 11k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Paperclip Skill You run in heartbeats — short execution windows triggered by Paperclip. Each heartbeat, you wake up, check your work, do something useful, and exit. You do not run continuously. Setup and Installation If the task is to install, set up, onboard, or bootstrap Paperclip itself (not task coordination on a running instance), read references/setup-installation.md first. It covers cloning the repo, running from source with pnpm, health checks, data reset, and troubleshooting. Do not use npx paperclipai. After the server is healthy, use the paperclip-board skill for first-company onboarding, or continue with normal API workflows below. Terminology In Paperclip, task and issue refer to the same work item. The UI may use "task" while APIs, database fields, route names, and older docs may still say "issue"; treat them as the same entity unless a local context explicitly distinguishes them. Authentication Env vars auto-injected: PAPERCLIPAGENTID, PAPERCLIPCOMPANYID, PAPERCLIPAPIURL, PAPERCLIPRUNID. Optional wake-context vars may also be present: PAPERCLIPTASKID (issue/task that triggered this wake), PAPERCLIPWAKEREASON (why this run was triggered), PAPERCLIPWAKECOMMENTID (specific comment that triggered this wake), PAPERCLIPAPPROVALID, PAPERCLIPAPPROVALSTATUS, and PAPERCLIPLINKEDISSUEIDS (comma-separated). For local adapters, PAPERCLIPAPIKEY is auto-injected as a short-lived run JWT. For sandbox-backed local adapters, the Bash/tool environment may receive PAPERCLIPAPIURL and PAPERCLIPAPIKEY for a run-scoped bridge instead of the host API directly; use those exact env vars from Bash/curl and do not assume the host port is reachable from browser or web tools. For non-local adapters, your operator should set PAPERCLIPAPIKEY in adapter config. All requests use Authorization: Bearer $PAPERCLIPAPIKEY. All endpoints under /api, all JSON. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/paperclip