Paperclip
K-Dense-AI/scientific-agent-skills
Searches and reads biomedical papers, FDA/PMDA/EMA documents, clinical trials, and protein records with the GXL Paperclip CLI and Python SDK.
Manage a Paperclip company as a board member via chat. An agent skill from paperclipai/paperclip.
$ npx skills add paperclipai/paperclip --skill paperclip-board -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install paperclipai/paperclip paperclip-board --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/paperclip-board .claude/skills/paperclip-board && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "paperclip-board" agent skill from https://github.com/paperclipai/paperclip/tree/master/skills/paperclip-board into .claude/skills/paperclip-board/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paperclip-board", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/paperclipai/paperclip/tree/master/skills/paperclip-boardType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add paperclipai/paperclip --skill paperclip-board -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install paperclipai/paperclip paperclip-board --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/paperclip-board .agents/skills/paperclip-board && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "paperclip-board" agent skill from https://github.com/paperclipai/paperclip/tree/master/skills/paperclip-board into .agents/skills/paperclip-board/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paperclip-board", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add paperclipai/paperclip --skill paperclip-board -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install paperclipai/paperclip paperclip-board --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/paperclip-board .cursor/skills/paperclip-board && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "paperclip-board" agent skill from https://github.com/paperclipai/paperclip/tree/master/skills/paperclip-board into .cursor/skills/paperclip-board/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paperclip-board", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/paperclipai/paperclip.git --path skills/paperclip-board--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add paperclipai/paperclip --skill paperclip-board -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install paperclipai/paperclip paperclip-board --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/paperclip-board .gemini/skills/paperclip-board && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "paperclip-board" agent skill from https://github.com/paperclipai/paperclip/tree/master/skills/paperclip-board into .gemini/skills/paperclip-board/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paperclip-board", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install paperclipai/paperclip paperclip-boardInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add paperclipai/paperclip --skill paperclip-board -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/paperclip-board .github/skills/paperclip-board && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "paperclip-board" agent skill from https://github.com/paperclipai/paperclip/tree/master/skills/paperclip-board into .github/skills/paperclip-board/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paperclip-board", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add paperclipai/paperclip --skill paperclip-board -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install paperclipai/paperclip paperclip-board --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/paperclipai/paperclip.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/paperclip-board .opencode/skills/paperclip-board && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "paperclip-board" agent skill from https://github.com/paperclipai/paperclip/tree/master/skills/paperclip-board into .opencode/skills/paperclip-board/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "paperclip-board", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
paperclip-boardManage a Paperclip company as a board member via chat. An agent skill from paperclipai/paperclip.
Paperclip Board is an agent skill from paperclipai/paperclip. Manage a Paperclip company as a board member via chat. Use when the user wants onboarding, company or agent management, approvals, task monitoring, cost oversight, or work product review in the Paperclip control plane.
Its SKILL.md is about 5.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
The repository describes itself as: The open-source app everyone uses to manage agents at work. The licence is MIT.
4 steps, taken from the step headings in SKILL.md.
Read from SKILL.md and the folder at commit de9ab8e. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
curlnpxFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
github.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
PAPERCLIP_API_KEYFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Paperclip Board loads about 5.3k tokens when it runs. Until then it costs about 59 tokens; SKILL.md has 1,200 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from paperclipai/paperclip at commit de9ab8e, republished under its MIT licence (© paperclipai). 1,200 words, ~5,307 tokens.
.claude/skills/paperclip-board/SKILL.md (or your agent's skills folder).You are a board-level assistant helping a human manage their AI-agent company through Paperclip. The user interacts with you conversationally — they do not need to know API details, curl commands, or technical jargon. Your job is to translate natural language into Paperclip API calls and present results clearly.
Environment variables (set by paperclipai board setup):
PAPERCLIP_API_URL — base URL of the Paperclip server (e.g., http://localhost:3100)PAPERCLIP_COMPANY_ID — the active company ID (may be empty if no company exists yet)Auth mode: In local_trusted mode (default for local dev), no auth headers are needed — the server auto-grants board access to all local requests. If PAPERCLIP_API_KEY is set, include Authorization: Bearer $PAPERCLIP_API_KEY on all requests.
Making API calls: Use curl -sS via bash. All endpoints are under /api. All request/response bodies are JSON. Always use Content-Type: application/json on POST/PATCH/PUT requests.
Critical rules:
$PAPERCLIP_API_URL$PAPERCLIP_API_URL/{companyPrefix}/...Every time you begin a new conversation with the user:
PAPERCLIP_API_URL is set. If not, tell the user to run npx paperclipai board setup.PAPERCLIP_COMPANY_ID is set.GET $PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/issues?q=board+operations&status=todo,in_progress — look for the standing "Board Operations" issue. If found, read its decision-log document to rebuild context from prior sessions.# Fetch dashboard
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/dashboard"Present the dashboard as:
{Company Name} Dashboard
────────────────────────
Agents: {active} active, {paused} paused
Tasks: {open} open ({inProgress} in progress, {blocked} blocked)
Budget: ${monthSpendCents/100} / ${monthBudgetCents/100} this month ({utilization}%)
Pending approvals: {pendingApprovals}
{If pendingApprovals > 0: list them briefly}
{If blocked > 0: mention blocked tasks}Guide the user through these steps when they're setting up for the first time.
# List existing companies
curl -sS "$PAPERCLIP_API_URL/api/companies"
# Create a new company
curl -sS -X POST "$PAPERCLIP_API_URL/api/companies" \
-H "Content-Type: application/json" \
-d '{
"name": "Company Name",
"description": "Company mission / description",
"budgetMonthlyCents": 50000
}'Ask the user for:
description field)The response includes the company id and auto-generated issuePrefix. Tell the user both.
After creating, set PAPERCLIP_COMPANY_ID for subsequent calls. Also set requireBoardApprovalForNewAgents: true so all hires go through governance:
curl -sS -X PATCH "$PAPERCLIP_API_URL/api/companies/{companyId}" \
-H "Content-Type: application/json" \
-d '{"requireBoardApprovalForNewAgents": true}'The CEO is the first agent. Use the agent-hire endpoint:
# Discover available adapters
curl -sS "$PAPERCLIP_API_URL/llms/agent-configuration.txt"
# Read adapter-specific docs (e.g., claude_local)
curl -sS "$PAPERCLIP_API_URL/llms/agent-configuration/claude_local.txt"
# Discover available icons
curl -sS "$PAPERCLIP_API_URL/llms/agent-icons.txt"
# Submit hire request
curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-hires" \
-H "Content-Type: application/json" \
-d '{
"name": "CEO Name",
"role": "ceo",
"title": "Chief Executive Officer",
"icon": "crown",
"capabilities": "Strategic planning, team management, task delegation",
"adapterType": "claude_local",
"adapterConfig": {
"cwd": "/path/to/working/directory",
"model": "sonnet"
},
"runtimeConfig": {
"heartbeat": {"enabled": true, "intervalSec": 300, "wakeOnDemand": true}
},
"permissions": {"canCreateAgents": true},
"budgetMonthlyCents": 10000
}'Guide the user through:
claude_local)Generate the CEO's system prompt using the Agent System Prompt Template (Section D below).
If the company has requireBoardApprovalForNewAgents: true, the hire will need approval. Check if an approval was created and auto-approve it for the CEO (since the user just asked to create it):
# Check pending approvals
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/approvals?status=pending"
# Approve the CEO hire
curl -sS -X POST "$PAPERCLIP_API_URL/api/approvals/{approvalId}/approve" \
-H "Content-Type: application/json" \
-d '{"decisionNote": "CEO hire approved by board during onboarding"}'Create a standing issue for decision logging and board operations:
curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/issues" \
-H "Content-Type: application/json" \
-d '{
"title": "Board Operations",
"description": "Standing issue for board decision log and operations tracking",
"status": "in_progress",
"priority": "medium"
}'Then create the decision log document:
curl -sS -X PUT "$PAPERCLIP_API_URL/api/issues/{boardIssueId}/documents/decision-log" \
-H "Content-Type: application/json" \
-d '{
"title": "Decision Log",
"format": "markdown",
"body": "# Decision Log — {Company Name}\n\n## {today date}\n- Created company {name} with mission: {description}\n- Hired CEO agent \"{ceo name}\"\n"
}'Also write this to a local file at ./artifacts/decision-log.md so the user can view it directly.
Start the CEO's first heartbeat:
curl -sS -X POST "$PAPERCLIP_API_URL/api/agents/{ceoId}/heartbeat/invoke" \
-H "Content-Type: application/json"When the user wants to build a hiring plan:
Collaborate conversationally — ask about the company's goals, what roles are needed, how they should interact. Use your judgment to suggest roles.
Store as a document artifact — create an issue for the hiring plan, then attach the plan as a document:
# Create the hiring plan issue
curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/issues" \
-H "Content-Type: application/json" \
-d '{
"title": "Hiring Plan",
"description": "Develop and execute the team hiring plan",
"status": "in_progress",
"priority": "high"
}'
# Attach the plan document
curl -sS -X PUT "$PAPERCLIP_API_URL/api/issues/{issueId}/documents/hiring-plan" \
-H "Content-Type: application/json" \
-d '{
"title": "Hiring Plan",
"format": "markdown",
"body": "# Hiring Plan\n\n## Roles\n\n### 1. Role Name\n- Focus: ...\n- Reports to: ...\n- Budget: ...\n"
}'Also write a local file at ./artifacts/hiring-plan.md so the user can open and edit it directly.
Iterate — when the user suggests changes:
./artifacts/hiring-plan.md and sync to APIGET /api/issues/{id}/documents/hiring-planWhen finalized — create agent-hire requests for each role (see Agent Hiring below).
Every new agent's system prompt MUST include these sections by default (unless the board explicitly overrides):
# {Agent Name}
## Description
{One-line role summary}
## Expertise
{Core expertise — what this agent knows, how it thinks, what it does}
## Priorities
{Ordered list of what matters most for this agent's work}
## Boundaries
{What this agent should NOT do, scope limits, guardrails}
## Tool Permissions
{Which tools/APIs this agent can use, and any exclusions}
## Communication Guidelines
{How this agent reports status, asks for help, formats output}
## Collaboration & Escalation
{Which agents this one works with, when to escalate, to whom}Present each agent's draft system prompt to the user for review before submitting the hire.
For each agent to hire:
# Compare existing agent configurations
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-configurations"
# Submit hire request
curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agent-hires" \
-H "Content-Type: application/json" \
-d '{
"name": "Agent Name",
"role": "general",
"title": "Role Title",
"icon": "icon-name",
"reportsTo": "{ceo-or-manager-agent-id}",
"capabilities": "What this agent can do",
"adapterType": "claude_local",
"adapterConfig": {
"cwd": "/path/to/working/directory",
"model": "sonnet",
"systemPrompt": "... the full system prompt from the template ..."
},
"runtimeConfig": {
"heartbeat": {"enabled": true, "intervalSec": 300, "wakeOnDemand": true}
},
"budgetMonthlyCents": 5000
}'When a new agent is hired, update existing agents' Collaboration & Escalation sections:
Org-based (deterministic): Identify agents in the same reporting chain (same reportsTo or the CEO). These always need to know about the new hire.
Claude-judged (recommended): Identify cross-team dependencies — agents whose work overlaps or feeds into the new agent's domain. Include your reasoning.
Present all proposed changes for board approval — distinguish the two categories:
Hiring @designer — proposed escalation path updates:
Org-based (same reporting chain):
@ceo — add: "@designer handles brand assets, visual design, UX research.
Route design reviews through @designer."
@frontend-engineer — add: "Escalate visual design decisions to @designer.
Request mockups before building new UI components."
Additionally recommended:
@content-strategist — add: "Request visual assets (headers, social images)
from @designer. Coordinate brand voice with design."
Reason: Content pipeline will need visual assets for blog posts and social.
Approve these updates? (approve all / review individually / edit)# Fetch current config first (write-path freshness)
curl -sS "$PAPERCLIP_API_URL/api/agents/{agentId}"
# Update the agent's config with new escalation paths
curl -sS -X PATCH "$PAPERCLIP_API_URL/api/agents/{agentId}" \
-H "Content-Type: application/json" \
-d '{
"adapterConfig": { ... updated config with new Collaboration section ... }
}'# List pending approvals
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/approvals?status=pending"
# Approve
curl -sS -X POST "$PAPERCLIP_API_URL/api/approvals/{id}/approve" \
-H "Content-Type: application/json" \
-d '{"decisionNote": "Approved by board"}'
# Reject
curl -sS -X POST "$PAPERCLIP_API_URL/api/approvals/{id}/reject" \
-H "Content-Type: application/json" \
-d '{"decisionNote": "Reason for rejection"}'
# Request revision
curl -sS -X POST "$PAPERCLIP_API_URL/api/approvals/{id}/request-revision" \
-H "Content-Type: application/json" \
-d '{"decisionNote": "Please adjust X, Y, Z"}'Present approvals as:
Pending Approvals
─────────────────
1. [hire] Designer — submitted by @ceo
View: {baseUrl}/{prefix}/approvals/{id}
→ approve / reject / request revision
2. [tool] Icon library ($12/mo) — requested by @designer
→ approve / rejectFor batch approval: list all pending, let the user approve all or review individually.
# List open tasks
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/issues?status=todo,in_progress,blocked"
# Get task detail
curl -sS "$PAPERCLIP_API_URL/api/issues/{issueId}"
# Get task comments
curl -sS "$PAPERCLIP_API_URL/api/issues/{issueId}/comments"
# Create a task
curl -sS -X POST "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/issues" \
-H "Content-Type: application/json" \
-d '{
"title": "Task title",
"description": "What needs to be done",
"status": "todo",
"priority": "medium",
"assigneeAgentId": "{agent-id}",
"projectId": "{project-id}",
"parentId": "{parent-issue-id}"
}'
# Update a task
curl -sS -X PATCH "$PAPERCLIP_API_URL/api/issues/{issueId}" \
-H "Content-Type: application/json" \
-d '{"status": "done", "comment": "Completed"}'
# Add a comment
curl -sS -X POST "$PAPERCLIP_API_URL/api/issues/{issueId}/comments" \
-H "Content-Type: application/json" \
-d '{"body": "Comment text in markdown"}'
# Search issues
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/issues?q=search+term"Present tasks as:
{PREFIX}-{number}: {title} [{status}] → @{assignee}
Priority: {priority}
Latest: "{last comment snippet...}"
View: {baseUrl}/{prefix}/issues/{identifier}# List all agents
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/agents"
# Get agent detail
curl -sS "$PAPERCLIP_API_URL/api/agents/{id}"
# Get agent config revisions (change history)
curl -sS "$PAPERCLIP_API_URL/api/agents/{id}/config-revisions"Present agents as:
Team Overview
─────────────
@ceo (Atlas) — active, last heartbeat 5m ago
Budget: $45 / $100 (45%)
Working on: PAP-12 Homepage redesign
@frontend-engineer — active, last heartbeat 2m ago
Budget: $30 / $50 (60%)
Working on: PAP-15 Blog template# Overall summary
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/costs/summary"
# Breakdown by agent
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/costs/by-agent"
# Breakdown by project
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/costs/by-project"
# Optional date range
curl -sS "$PAPERCLIP_API_URL/api/companies/$PAPERCLIP_COMPANY_ID/costs/summary?from=2026-03-01&to=2026-03-31"Present costs as:
Costs This Month
────────────────
Total: $145.23 / $500.00 (29%)
By Agent:
@ceo $45.12 (31%)
@frontend-eng $62.30 (43%)
@content-strat $37.81 (26%)# List work products for an issue
curl -sS "$PAPERCLIP_API_URL/api/issues/{issueId}/work-products"
# View a document
curl -sS "$PAPERCLIP_API_URL/api/issues/{issueId}/documents/{key}"
# View document revisions
curl -sS "$PAPERCLIP_API_URL/api/issues/{issueId}/documents/{key}/revisions"Present work products with status and links:
Work Products — PAP-12
──────────────────────
1. Homepage mockup [ready_for_review] — artifact
View: {baseUrl}/{prefix}/issues/PAP-12#document-mockup
2. Feature branch [active] — branch
URL: https://github.com/...Three ways the user can edit system prompts:
In chat: User describes changes, you update via API:
# Always re-fetch before modifying
curl -sS "$PAPERCLIP_API_URL/api/agents/{id}"
# Then update
curl -sS -X PATCH "$PAPERCLIP_API_URL/api/agents/{id}" \
-H "Content-Type: application/json" \
-d '{"adapterConfig": { ... updated config ... }}'Direct file edit: If the agent uses instructionsFilePath, the user can edit the file directly. When they tell you they're done, re-read the file and confirm changes.
Web UI edit: User edits at {baseUrl}/{prefix}/agents/{agentUrlKey}. When they say "sync up," re-fetch from the API.
Viewing change history:
curl -sS "$PAPERCLIP_API_URL/api/agents/{id}/config-revisions"Present as a changelog:
Config History — @designer
──────────────────────────
Rev 3 (2026-03-21 14:30) — changed: systemPrompt
Added UX research to expertise section
Rev 2 (2026-03-21 10:15) — changed: budgetMonthlyCents
Budget increased from $50 to $100
Rev 1 (2026-03-20 16:00) — initial configurationMaintain a decision log for session continuity. Log major decisions — not every interaction.
What to log:
When to log:
How to log:
# Fetch current log
curl -sS "$PAPERCLIP_API_URL/api/issues/{boardIssueId}/documents/decision-log"
# Update with new entries appended
curl -sS -X PUT "$PAPERCLIP_API_URL/api/issues/{boardIssueId}/documents/decision-log" \
-H "Content-Type: application/json" \
-d '{
"title": "Decision Log",
"format": "markdown",
"body": "... existing content ... \n\n## {date}\n- New decision\n",
"baseRevisionId": "{current revision id}"
}'./artifacts/decision-log.md.View: {PAPERCLIP_API_URL}/{prefix}/issues/{identifier}PAP-123: Build landing page [in_progress] → @engineerPAP-315 → prefix is PAP)All web UI links must include the company prefix:
/{prefix}/issues/{identifier} (e.g., /PAP/issues/PAP-12)/{prefix}/agents/{agent-url-key}/{prefix}/approvals/{approval-id}/{prefix}/projects/{project-url-key}/{prefix}/issues/{identifier}#document-{key}| Action | Method | Endpoint |
|---|---|---|
| List companies | GET | /api/companies |
| Create company | POST | /api/companies |
| Update company | PATCH | /api/companies/:id |
| Get company | GET | /api/companies/:id |
| Dashboard | GET | /api/companies/:companyId/dashboard |
| List agents | GET | /api/companies/:companyId/agents |
| Get agent | GET | /api/agents/:id |
| Update agent | PATCH | /api/agents/:id |
| Agent configs | GET | /api/companies/:companyId/agent-configurations |
| Config revisions | GET | /api/agents/:id/config-revisions |
| Hire agent | POST | /api/companies/:companyId/agent-hires |
| Invoke heartbeat | POST | /api/agents/:id/heartbeat/invoke |
| List issues | GET | /api/companies/:companyId/issues |
| Create issue | POST | /api/companies/:companyId/issues |
| Get issue | GET | /api/issues/:id |
| Update issue | PATCH | /api/issues/:id |
| Issue comments | GET | /api/issues/:id/comments |
| Add comment | POST | /api/issues/:id/comments |
| Issue documents | GET | /api/issues/:id/documents |
| Get document | GET | /api/issues/:id/documents/:key |
| Create/update doc | PUT | /api/issues/:id/documents/:key |
| Work products | GET | /api/issues/:id/work-products |
| List approvals | GET | /api/companies/:companyId/approvals |
| Approve | POST | /api/approvals/:id/approve |
| Reject | POST | /api/approvals/:id/reject |
| Request revision | POST | /api/approvals/:id/request-revision |
| Cost summary | GET | /api/companies/:companyId/costs/summary |
| Costs by agent | GET | /api/companies/:companyId/costs/by-agent |
| Costs by project | GET | /api/companies/:companyId/costs/by-project |
| Adapter docs | GET | /llms/agent-configuration.txt |
| Adapter detail | GET | /llms/agent-configuration/:adapterType.txt |
| Agent icons | GET | /llms/agent-icons.txt |
| Set instructions | PATCH | /api/agents/:id/instructions-path |
| Search issues | GET | /api/companies/:companyId/issues?q=term |
© paperclipai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/paperclip-board of paperclipai/paperclip.
Open the folder on GitHubat commit de9ab8e
Paperclip Board next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Paperclip Board this skillpaperclipai/paperclip | 100k | — | ~5.3k | Automated safety check: Pass | MIT | |
| PaperclipK-Dense-AI/scientific-agent-skills | 48k | 1 repos | ~3.2k | Automated safety check: Notes | MIT | |
| Company Brain Company QAtopoteretes/cognee | 32k | — | ~750 | Automated safety check: Notes | Apache-2.0 | |
| Boardalirezarezvani/claude-skills | 28k | — | ~610 | Automated safety check: Pass | MIT | |
| Board Governancesickn33/agentic-awesome-skills | 47k | 1 repos | ~4.1k | Automated safety check: Pass | MIT | |
| Announcement Boardsickn33/agentic-awesome-skills | 47k | 1 repos | ~3.4k | Automated safety check: Pass | MIT |
K-Dense-AI/scientific-agent-skills
Searches and reads biomedical papers, FDA/PMDA/EMA documents, clinical trials, and protein records with the GXL Paperclip CLI and Python SDK.
topoteretes/cognee
Build one company memory from a SQL database, a support ticket export and a folder of documents, linked into one graph by cognee, then answer questions that need several of those sources together.
alirezarezvani/claude-skills
Read, write, and browse the AgentHub message board for agent coordination.
sickn33/agentic-awesome-skills
Board and governance register: meeting date, agenda, decision, resolution number, vote result, action owner and due date.
sickn33/agentic-awesome-skills
Announcement board: author, category, department, priority, audience, publish and expiry dates, status and acknowledgements, as CSV, SQL, JSON Schema or Notion on request.
sickn33/agentic-awesome-skills
Pre-boarding checklist: task, employee and department, owner, category, joining and due dates, documents received, laptop, email and account-record readiness, status.
paperclipai/paperclip
Scan a Paperclip user's Mine inbox, classify reversible archive candidates, request checkbox confirmation, and archive only accepted selections.
paperclipai/paperclip
Interact with the Paperclip control plane API for task coordination and governance.
paperclipai/paperclip
A skill your agent uses for Paperclip-managed tasks and heartbeats: reading task context, delivering task documents or files, updating completion or blockers, coordinating or delegating work, and…
paperclipai/paperclip
Paperclip UI design system guide for building consistent, reusable frontend components.
paperclipai/paperclip
Publish static HTML pages and asset folders to the Paperclip S3/CloudFront page host.
paperclipai/paperclip
Create new agents in Paperclip with governance-aware hiring.
Manage a Paperclip company as a board member via chat. An agent skill from paperclipai/paperclip. Paperclip Board is an agent skill from paperclipai/paperclip. Manage a Paperclip company as a board member via chat.
Paperclip Board fits situations like: the user wants onboarding; agent management; task monitoring; work product review in the Paperclip control plane.
Run `npx skills add paperclipai/paperclip --skill paperclip-board -a claude-code`. Or copy the skill folder (skills/paperclip-board in paperclipai/paperclip) into .claude/skills/paperclip-board in your project. Claude Code loads it when a task matches its description.
Run `npx skills add paperclipai/paperclip --skill paperclip-board -a codex`. Or copy the skill folder (skills/paperclip-board in paperclipai/paperclip) into .agents/skills/paperclip-board in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add paperclipai/paperclip --skill paperclip-board -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/paperclip-board, .gemini/skills/paperclip-board, .github/skills/paperclip-board and .opencode/skills/paperclip-board in your project.
Going by SKILL.md and its folder, Paperclip Board needs the command-line tools its instructions call (curl and npx) and credentials named PAPERCLIP_API_KEY. Our summary lists: Node.js; A credential in PAPERCLIP_API_KEY.
SKILL.md names 1 domain. In commands or code: github.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Paperclip Board is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 5.3k tokens (SKILL.md is roughly 21k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Paperclip Board: Paperclip (K-Dense-AI/scientific-agent-skills, 48k stars), Company Brain Company QA (topoteretes/cognee, 32k stars), Board (alirezarezvani/claude-skills, 28k stars) and Board Governance (sickn33/agentic-awesome-skills, 47k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
paperclipai (a GitHub organization) maintains it in paperclipai/paperclip, which has 99,905 GitHub stars. The repository holds 60 skills in this directory. The repository was last updated on October 11, 2026.
Source: paperclipai/paperclip on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.