Paperclip Operator Skills

Local operator skills for preparing and operating AFK work in Paperclip through the paperclipai CLI.

These skills help a human operator turn fuzzy intent into Paperclip-native goals, projects, parent issues, plans, child issues, triage decisions, and monitoring reports while keeping Paperclip as the source of truth.

Install

List available skills:

npx skills add bbengamin/skills --list

Install all Paperclip operator skills into the current project:

npx skills add bbengamin/skills --all

Install globally:

npx skills add bbengamin/skills --all -g

Install selected skills:

npx skills add bbengamin/skills --skill paperclip-setup paperclip-clarify paperclip-record-strategy

After installing in a fresh project, run paperclip-setup. It checks your paperclipai context and can scaffold the shared operator docs into the project after you approve:

AGENTS.md
CONTEXT.md
docs/paperclip-operator/

Skill Catalog

Paperclip Operator

• paperclip-setup — check local paperclipai context and shared operator docs.
• paperclip-clarify — run a non-mutating clarification session.
• paperclip-record-strategy — create or select the Paperclip planning chain: Goal, Project, Parent Issue, and plan document.
• paperclip-plan-work — decompose a strategy artifact or parent issue into one level of child issues.
• paperclip-triage — review issues for AFK readiness before delegation.
• paperclip-monitor — inspect active execution across agents, heartbeats, activity, approvals, costs, and blocked work.
• paperclip-admin — handle ad hoc Paperclip reads, minor approved mutations, existing-agent admin, and company skill-library maintenance.
• paperclip-create-agent — create or hire Paperclip agents through the governance-aware native workflow.

Creator Growth

• creator-clarify — run a non-mutating creator-growth clarification session.
• creator-record-strategy — record approved creator-growth strategy into goals, creator projects, parent issues, campaign issues, and plan documents.
• creator-plan-work — decompose creator strategy or campaign artifacts into one level of backlog creator work.
• creator-triage — review planned creator work for AFK readiness before delegation.

Growth Operator

• growth-clarify — run a non-mutating clarification session for shared acquisition strategy across inbound and outbound.
• growth-record-strategy — record approved growth strategy into goals, durable channel/motion projects, strategy parent issues, branch parent issues, and plan documents.
• inbound-plan-work — decompose a growth strategy or inbound branch into one level of backlog inbound/channel work.
• outbound-plan-work — decompose a growth strategy or outbound branch into one level of backlog outbound work.
• inbound-triage — review planned inbound/channel work for level-aware AFK readiness before delegation.
• outbound-triage — review planned outbound work for level-aware AFK readiness across asset prep, tool work, sending, and reply/booking support.
• growth-tooling-scout — evaluate acquisition tools before adoption, integration, extension, or custom build.

Workflow

clarify -> record strategy -> plan work -> triage -> monitor -> recursive planning

Growth strategy branches after the shared strategy is recorded:

growth-clarify -> growth-record-strategy -> inbound-plan-work / outbound-plan-work -> inbound-triage / outbound-triage

The suite is designed around Paperclip's native hierarchy:

Company -> Goal -> Project -> Issue -> Workspace -> Agent run

Shared References

• AGENTS.md — repo-level operating rules.
• CONTEXT.md — glossary.
• docs/paperclip-operator/control-plane.md — Paperclip entities and lifecycle.
• docs/paperclip-operator/workflow.md — skill workflow.
• docs/paperclip-operator/afk-readiness.md — readiness rules for AFK issues.
• docs/paperclip-operator/cli-contract.md — paperclipai usage contract.
• docs/paperclip-operator/integration-matrix.md — MCP/CLI/REST operation matrix.
• docs/paperclip-operator/paperclip-docs-index.md — upstream Paperclip docs index.
• docs/growth-operator/control-plane.md — acquisition goals, durable channel/motion projects, and branch strategy model.
• docs/growth-operator/workflow.md — Growth skill workflow.
• docs/growth-operator/afk-readiness.md — shared readiness rules for inbound and outbound planning.
• docs/growth-operator/tooling-scout.md — growth tooling evaluation and build-vs-buy rubric.

These docs are bundled inside paperclip-setup as templates so they can be copied into fresh projects.

Principles

• Paperclip is the source of truth.
• Operator skills inspect before mutating.
• Mutations require operator approval.
• backlog means not ready or parked.
• todo means ready and actionable.
• Plan one child-issue level at a time.
• Use blockedByIssueIds for real dependencies.
• Use goals and sub-goals for durable acquisition direction.
• Use one project per durable inbound channel or outbound motion.
• Use parent issues and plan documents for strategy periods, campaigns, experiments, and branch planning.
• Keep outbound triage level-aware: asset preparation, tool work, sending, and reply/booking support have different approval and stop-condition requirements.
• Scout acquisition tools before hard-coding vendor assumptions into planning or triage skills.