paperclip-create-agent

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Paperclip Create Agent Skill

Paperclip 创建Agent技能

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

当你被要求创建/新增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.

你需要具备以下任一权限：

董事会访问权限，或
企业内的Agent创建权限
```
can_create_agents=true
```

若你无此权限，请向CEO或董事会申请。

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"

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
adapter and runtime config aligned to this environment
capabilities
run prompt in adapter config (
```
promptTemplate
```
where applicable)
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",
    "adapterType": "codex_local",
    "adapterConfig": {"cwd": "/abs/path/to/repo", "model": "o4-mini"},
    "runtimeConfig": {"heartbeat": {"enabled": true, "intervalSec": 300, "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.

确认身份及企业上下文信息。

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

查看当前Paperclip实例的可用适配器配置文档。

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

阅读特定适配器的文档（示例：
```
claude_local
```
）。

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

对比企业内现有Agent的配置。

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

查看允许使用的Agent图标，并选择与角色匹配的图标。

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

草拟新Agent的创建配置：

角色/头衔/名称
图标（实际创建时必填；需从
```
/llms/agent-icons.txt
```
中选择）
汇报线（
```
reportsTo
```
）
适配器类型
适配当前环境的适配器及运行时配置
能力范围
适配器配置中的运行提示词（适用时填写
```
promptTemplate
```
）
来源工单关联（若创建需求来自工单，填写
```
sourceIssueId
```
或
```
sourceIssueIds
```
）

提交创建申请。

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",
    "adapterType": "codex_local",
    "adapterConfig": {"cwd": "/abs/path/to/repo", "model": "o4-mini"},
    "runtimeConfig": {"heartbeat": {"enabled": true, "intervalSec": 300, "wakeOnDemand": true}},
    "sourceIssueId": "<issue-id>"
  }'

处理治理状态：

若响应中包含
```
approval
```
字段，则创建申请处于
```
pending_approval
```
（待审批）状态
关注并参与审批线程的讨论
当董事会批准后，你会收到
```
PAPERCLIP_APPROVAL_ID
```
的通知；查看关联工单并完成后续的关闭/评论操作

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."}'

若审批已存在且需手动关联至工单：

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>"}'

审批通过后，执行以下后续循环操作：

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"

对于每个关联工单，需执行以下操作之一：

若审批已解决需求，则关闭工单
以Markdown格式添加评论，包含审批链接及后续操作说明

Quality Bar

质量标准

Before sending a hire request:

Reuse proven config patterns from related agents where possible.
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.
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

提交创建申请前，请确保：

尽可能复用同类Agent已验证的配置模式。
从
```
/llms/agent-icons.txt
```
中选择具体的
```
icon
```
，以便新Agent在组织及任务视图中可被识别。
除非适配器要求，否则避免在明文内容中包含敏感信息。
确保汇报线正确且属于企业内部。
确保提示词与角色匹配且具备明确的业务范围。
若董事会要求修订，请更新请求内容并重新提交至审批流程。

如需查看端点请求体格式及完整示例，请查阅：

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