paperclip-create-agent

Name: paperclip-create-agent
Author: IncomeStreamSurfer

69stars33forks

How to install paperclip-create-agent?

incomestreamsurfer/paperclip-surfers/paperclip-create-agent

$npx -y skills add IncomeStreamSurfer/paperclip-surfers --skill paperclip-create-agent

Installs into the current project.

Summary

Create new agents in Paperclip with governance-aware hiring. Use when you need to inspect adapter configuration options, compare existing agent configs, draft a new agent prompt/config, and submit a hire request.

Files · 1

View on GitHub

SKILL.md

1	# Paperclip Create Agent Skill
2
3	Use this skill when you are asked to hire/create an agent.
4
5	## Preconditions
6
7	You need either:
8
9	- board access, or
10	- agent permission `can_create_agents=true` in your company
11
12	If you do not have this permission, escalate to your CEO or board.
13
14	## Workflow
15
16	1. Confirm identity and company context.
17
18	```sh
19	curl -sS "$PAPERCLIP_API_URL/api/agents/me" \
20	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
21	```
22
23	2. Discover available adapter configuration docs for this Paperclip instance.
24
25	```sh
26	curl -sS "$PAPERCLIP_API_URL/llms/agent-configuration.txt" \
27	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
28	```
29
30	3. Read adapter-specific docs (example: `claude_local`).
31
32	```sh
33	curl -sS "$PAPERCLIP_API_URL/llms/agent-configuration/claude_local.txt" \
34	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
35	```
36
37	4. Compare existing agent configurations in your company.
38
39	```sh
40	curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-configurations" \
41	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
42	```
43
44	5. Discover allowed agent icons and pick one that matches the role.
45
46	```sh
47	curl -sS "$PAPERCLIP_API_URL/llms/agent-icons.txt" \
48	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
49	```
50
51	6. Draft the new hire config:
52	- role/title/name
53	- icon (required in practice; use one from `/llms/agent-icons.txt`)
54	- reporting line (`reportsTo`)
55	- adapter type
56	- optional `desiredSkills` from the company skill library when this role needs installed skills on day one
57	- adapter and runtime config aligned to this environment
58	- capabilities
59	- run prompt in adapter config (`promptTemplate` where applicable)
60	- source issue linkage (`sourceIssueId` or `sourceIssueIds`) when this hire came from an issue
61
62	7. Submit hire request.
63
64	```sh
65	curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-hires" \
66	-H "Authorization: Bearer $PAPERCLIP_API_KEY" \
67	-H "Content-Type: application/json" \
68	-d '{
69	"name": "CTO",
70	"role": "cto",
71	"title": "Chief Technology Officer",
72	"icon": "crown",
73	"reportsTo": "<ceo-agent-id>",
74	"capabilities": "Owns technical roadmap, architecture, staffing, execution",
75	"desiredSkills": ["vercel-labs/agent-browser/agent-browser"],
76	"adapterType": "codex_local",
77	"adapterConfig": {"cwd": "/abs/path/to/repo", "model": "o4-mini"},
78	"runtimeConfig": {"heartbeat": {"enabled": true, "intervalSec": 300, "wakeOnDemand": true}},
79	"sourceIssueId": "<issue-id>"
80	}'
81	```
82
83	8. Handle governance state:
84	- if response has `approval`, hire is `pending_approval`
85	- monitor and discuss on approval thread
86	- when the board approves, you will be woken with `PAPERCLIP_APPROVAL_ID`; read linked issues and close/comment follow-up
87
88	```sh
89	curl -sS "$PAPERCLIP_API_URL/api/approvals/<approval-id>" \
90	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
91
92	curl -sS -X POST "$PAPERCLIP_API_URL/api/approvals/<approval-id>/comments" \
93	-H "Authorization: Bearer $PAPERCLIP_API_KEY" \
94	-H "Content-Type: application/json" \
95	-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."}'
96	```
97
98	If the approval already exists and needs manual linking to the issue:
99
100	```sh
101	curl -sS -X POST "$PAPERCLIP_API_URL/api/issues/<issue-id>/approvals" \
102	-H "Authorization: Bearer $PAPERCLIP_API_KEY" \
103	-H "Content-Type: application/json" \
104	-d '{"approvalId":"<approval-id>"}'
105	```
106
107	After approval is granted, run this follow-up loop:
108
109	```sh
110	curl -sS "$PAPERCLIP_API_URL/api/approvals/$PAPERCLIP_APPROVAL_ID" \
111	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
112
113	curl -sS "$PAPERCLIP_API_URL/api/approvals/$PAPERCLIP_APPROVAL_ID/issues" \
114	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
115	```
116
117	For each linked issue, either:
118	- close it if approval resolved the request, or
119	- comment in markdown with links to the approval and next actions.
120
121	## Quality Bar
122
123	Before sending a hire request:
124
125	- if the role needs skills, make sure they already exist in the company library or install them first using the Paperclip company-skills workflow
126	- Reuse proven config patterns from related agents where possible.
127	- Set a concrete `icon` from `/llms/agent-icons.txt` so the new hire is identifiable in org and task views.
128	- Avoid secrets in plain text unless required by adapter behavior.
129	- Ensure reporting line is correct and in-company.
130	- Ensure prompt is role-specific and operationally scoped.
131	- If board requests revision, update payload and resubmit through approval flow.
132
133	For endpoint payload shapes and full examples, read:
134	`skills/paperclip-creat

People who liked this also viewed

6 picks

Type

paperclip-create-agent

69stars33forks

View on GitHub

How to install paperclip-create-agent?

incomestreamsurfer/paperclip-surfers/paperclip-create-agent

$npx -y skills add IncomeStreamSurfer/paperclip-surfers --skill paperclip-create-agent

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Paperclip Create Agent Skill
2
3	Use this skill when you are asked to hire/create an agent.
4
5	## Preconditions
6
7	You need either:
8
9	- board access, or
10	- agent permission `can_create_agents=true` in your company
11
12	If you do not have this permission, escalate to your CEO or board.
13
14	## Workflow
15
16	1. Confirm identity and company context.
17
18	```sh
19	curl -sS "$PAPERCLIP_API_URL/api/agents/me" \
20	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
21	```
22
23	2. Discover available adapter configuration docs for this Paperclip instance.
24
25	```sh
26	curl -sS "$PAPERCLIP_API_URL/llms/agent-configuration.txt" \
27	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
28	```
29
30	3. Read adapter-specific docs (example: `claude_local`).
31
32	```sh
33	curl -sS "$PAPERCLIP_API_URL/llms/agent-configuration/claude_local.txt" \
34	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
35	```
36
37	4. Compare existing agent configurations in your company.
38
39	```sh
40	curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-configurations" \
41	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
42	```
43
44	5. Discover allowed agent icons and pick one that matches the role.
45
46	```sh
47	curl -sS "$PAPERCLIP_API_URL/llms/agent-icons.txt" \
48	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
49	```
50
51	6. Draft the new hire config:
52	- role/title/name
53	- icon (required in practice; use one from `/llms/agent-icons.txt`)
54	- reporting line (`reportsTo`)
55	- adapter type
56	- optional `desiredSkills` from the company skill library when this role needs installed skills on day one
57	- adapter and runtime config aligned to this environment
58	- capabilities
59	- run prompt in adapter config (`promptTemplate` where applicable)
60	- source issue linkage (`sourceIssueId` or `sourceIssueIds`) when this hire came from an issue
61
62	7. Submit hire request.
63
64	```sh
65	curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-hires" \
66	-H "Authorization: Bearer $PAPERCLIP_API_KEY" \
67	-H "Content-Type: application/json" \
68	-d '{
69	"name": "CTO",
70	"role": "cto",
71	"title": "Chief Technology Officer",
72	"icon": "crown",
73	"reportsTo": "<ceo-agent-id>",
74	"capabilities": "Owns technical roadmap, architecture, staffing, execution",
75	"desiredSkills": ["vercel-labs/agent-browser/agent-browser"],
76	"adapterType": "codex_local",
77	"adapterConfig": {"cwd": "/abs/path/to/repo", "model": "o4-mini"},
78	"runtimeConfig": {"heartbeat": {"enabled": true, "intervalSec": 300, "wakeOnDemand": true}},
79	"sourceIssueId": "<issue-id>"
80	}'
81	```
82
83	8. Handle governance state:
84	- if response has `approval`, hire is `pending_approval`
85	- monitor and discuss on approval thread
86	- when the board approves, you will be woken with `PAPERCLIP_APPROVAL_ID`; read linked issues and close/comment follow-up
87
88	```sh
89	curl -sS "$PAPERCLIP_API_URL/api/approvals/<approval-id>" \
90	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
91
92	curl -sS -X POST "$PAPERCLIP_API_URL/api/approvals/<approval-id>/comments" \
93	-H "Authorization: Bearer $PAPERCLIP_API_KEY" \
94	-H "Content-Type: application/json" \
95	-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."}'
96	```
97
98	If the approval already exists and needs manual linking to the issue:
99
100	```sh
101	curl -sS -X POST "$PAPERCLIP_API_URL/api/issues/<issue-id>/approvals" \
102	-H "Authorization: Bearer $PAPERCLIP_API_KEY" \
103	-H "Content-Type: application/json" \
104	-d '{"approvalId":"<approval-id>"}'
105	```
106
107	After approval is granted, run this follow-up loop:
108
109	```sh
110	curl -sS "$PAPERCLIP_API_URL/api/approvals/$PAPERCLIP_APPROVAL_ID" \
111	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
112
113	curl -sS "$PAPERCLIP_API_URL/api/approvals/$PAPERCLIP_APPROVAL_ID/issues" \
114	-H "Authorization: Bearer $PAPERCLIP_API_KEY"
115	```
116
117	For each linked issue, either:
118	- close it if approval resolved the request, or
119	- comment in markdown with links to the approval and next actions.
120
121	## Quality Bar
122
123	Before sending a hire request:
124
125	- if the role needs skills, make sure they already exist in the company library or install them first using the Paperclip company-skills workflow
126	- Reuse proven config patterns from related agents where possible.
127	- Set a concrete `icon` from `/llms/agent-icons.txt` so the new hire is identifiable in org and task views.
128	- Avoid secrets in plain text unless required by adapter behavior.
129	- Ensure reporting line is correct and in-company.
130	- Ensure prompt is role-specific and operationally scoped.
131	- If board requests revision, update payload and resubmit through approval flow.
132
133	For endpoint payload shapes and full examples, read:
134	`skills/paperclip-creat

People who liked this also viewed

6 picks

Type