Paperclip paperclip-create-agent

install

source · Clone the upstream repo

git clone https://github.com/paperclipai/paperclip

Claude Code · Install into ~/.claude/skills/

T=$(mktemp -d) && git clone --depth=1 https://github.com/paperclipai/paperclip "$T" && mkdir -p ~/.claude/skills && cp -r "$T/skills/paperclip-create-agent" ~/.claude/skills/paperclipai-paperclip-paperclip-create-agent && rm -rf "$T"

manifest: skills/paperclip-create-agent/SKILL.md

Paperclip Create Agent Skill

Use this skill when you are asked to hire/create an agent.

Preconditions

You need either:

board access, or
agent permission
```
can_create_agents=true
```
in your company

If you do not have this permission, escalate to your CEO or board.

Workflow

Confirm identity and company context.

curl -sS "$PAPERCLIP_API_URL/api/agents/me" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

Discover available adapter configuration docs for this Paperclip instance.

curl -sS "$PAPERCLIP_API_URL/llms/agent-configuration.txt" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

Read adapter-specific docs (example:
```
claude_local
```
).

curl -sS "$PAPERCLIP_API_URL/llms/agent-configuration/claude_local.txt" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

Compare existing agent configurations in your company.

curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-configurations" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

Read the reusable agent instruction templates before drafting the hire. If the role matches an existing pattern, start from that template and adapt it to the company, manager, adapter, and workspace.

Reference:

skills/paperclip-create-agent/references/agent-instruction-templates.md

Agent-specific templates:

skills/paperclip-create-agent/references/agents/

Discover allowed agent icons and pick one that matches the role.

curl -sS "$PAPERCLIP_API_URL/llms/agent-icons.txt" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

Draft the new hire config:

role/title/name
icon (required in practice; use one from
```
/llms/agent-icons.txt
```
)
reporting line (
```
reportsTo
```
)
adapter type
optional
```
desiredSkills
```
from the company skill library when this role needs installed skills on day one
adapter and runtime config aligned to this environment
leave timer heartbeats off by default; only set
```
runtimeConfig.heartbeat.enabled=true
```
with an
```
intervalSec
```
when the role genuinely needs scheduled recurring work or the user explicitly asked for it
capabilities
run prompt in adapter config (
```
promptTemplate
```
where applicable)
for coding or execution agents, include the Paperclip execution contract: start actionable work in the same heartbeat; do not stop at a plan unless planning was requested; leave durable progress with a clear next action; use child issues for long or parallel delegated work instead of polling; mark blocked work with owner/action; respect budget, pause/cancel, approval gates, and company boundaries.
instruction text such as
```
AGENTS.md
```
, using a reusable template when one fits; for local managed-bundle adapters, put the adapted
```
AGENTS.md
```
content in
```
adapterConfig.promptTemplate
```
unless you are a board user intentionally managing bundle paths/files
source issue linkage (
```
sourceIssueId
```
or
```
sourceIssueIds
```
) when this hire came from an issue

Submit hire request.

curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-hires" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{
    "name": "CTO",
    "role": "cto",
    "title": "Chief Technology Officer",
    "icon": "crown",
    "reportsTo": "<ceo-agent-id>",
    "capabilities": "Owns technical roadmap, architecture, staffing, execution",
    "desiredSkills": ["vercel-labs/agent-browser/agent-browser"],
    "adapterType": "codex_local",
    "adapterConfig": {"cwd": "/abs/path/to/repo", "model": "o4-mini"},
    "runtimeConfig": {"heartbeat": {"enabled": false, "wakeOnDemand": true}},
    "sourceIssueId": "<issue-id>"
  }'

Handle governance state:

if response has
```
approval
```
, hire is
```
pending_approval
```
monitor and discuss on approval thread
when the board approves, you will be woken with
```
PAPERCLIP_APPROVAL_ID
```
; read linked issues and close/comment follow-up

curl -sS "$PAPERCLIP_API_URL/api/approvals/<approval-id>" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

curl -sS -X POST "$PAPERCLIP_API_URL/api/approvals/<approval-id>/comments" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"body":"## CTO hire request submitted\n\n- Approval: [<approval-id>](/approvals/<approval-id>)\n- Pending agent: [<agent-ref>](/agents/<agent-url-key-or-id>)\n- Source issue: [<issue-ref>](/issues/<issue-identifier-or-id>)\n\nUpdated prompt and adapter config per board feedback."}'

If the approval already exists and needs manual linking to the issue:

curl -sS -X POST "$PAPERCLIP_API_URL/api/issues/<issue-id>/approvals" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"approvalId":"<approval-id>"}'

After approval is granted, run this follow-up loop:

curl -sS "$PAPERCLIP_API_URL/api/approvals/$PAPERCLIP_APPROVAL_ID" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

curl -sS "$PAPERCLIP_API_URL/api/approvals/$PAPERCLIP_APPROVAL_ID/issues" \
  -H "Authorization: Bearer $PAPERCLIP_API_KEY"

For each linked issue, either:

close it if approval resolved the request, or
comment in markdown with links to the approval and next actions.

Quality Bar

Before sending a hire request:

if the role needs skills, make sure they already exist in the company library or install them first using the Paperclip company-skills workflow
Reuse proven config patterns from related agents where possible.
Reuse a proven instruction template when the role matches one in
```
skills/paperclip-create-agent/references/agent-instruction-templates.md
```
or
```
skills/paperclip-create-agent/references/agents/
```
; update placeholders and remove irrelevant guidance before submitting the hire.
Set a concrete
```
icon
```
from
```
/llms/agent-icons.txt
```
so the new hire is identifiable in org and task views.
Avoid secrets in plain text unless required by adapter behavior.
Ensure reporting line is correct and in-company.
Ensure prompt is role-specific and operationally scoped.
Keep timer heartbeats opt-in. Most hires should rely on assignment/on-demand wakeups unless the job explicitly needs a schedule.
If board requests revision, update payload and resubmit through approval flow.

For endpoint payload shapes and full examples, read:

skills/paperclip-create-agent/references/api-reference.md

For the reusable

AGENTS.md

starting point index, read:

skills/paperclip-create-agent/references/agent-instruction-templates.md

For the individual agent templates, read:

skills/paperclip-create-agent/references/agents/