# Manage Paperclip Company

Manages a Paperclip company by chat: onboarding, agents, approvals and cost oversight.

- Repository: https://github.com/paperclipai/paperclip (109885 stars)
- Category: Business
- License: MIT
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add paperclipai/paperclip --skill paperclip-board -g -a claude-code -y`
Codex: `npx skills add paperclipai/paperclip --skill paperclip-board -g -a codex -y`
Cursor: `npx skills add paperclipai/paperclip --skill paperclip-board -g -a cursor -y`
Gemini CLI: `npx skills add paperclipai/paperclip --skill paperclip-board -g -a gemini-cli -y`

## Description

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.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# Paperclip Board Skill

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.

## Authentication & Environment

**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:**
- Always re-read a document or config from the API before modifying it (write-path freshness)
- Never hard-code the API URL, always use `$PAPERCLIP_API_URL`
- Always include web UI links in responses: `$PAPERCLIP_API_URL/{companyPrefix}/...`
- Present results conversationally, summarize, don't dump JSON

## Session Startup

Every time you begin a new conversation with the user:

The rest: https://github.com/paperclipai/paperclip/blob/HEAD/skills/paperclip-board/SKILL.md