create-paperclip-bundled-skill

Topics in the source

• Create a Paperclip Bundled Skill
• When to use
• When not to use
• Step 0 — Capture the source material
• Step 1 — FIND: search for an existing skill
• Step 2 — Choose kind, category, and slug
• Step 2A — External reference path (catalog-ref.json)
• Step 2B — Author a local catalog skill

Take source material — a tweet, a task description, a blog post, "make a skill that does X" — and land it as a skill in the Paperclip skills catalog (packages/skills-catalog/), delivered as a reviewed PR. The catalog is the shelf every Paperclip company browses and installs from, so the bar is: correct metadata, useful instructions, worked examples, and a clean validation run. The core rule is FIND before MAKE: if a good skill already exists (in the catalog, in this repo, or published on GitHub), reference or adapt it instead of writing a duplicate from scratch. A human sends a tweet/link/idea and asks for it to become a Paperclip skill. A task asks to bundle an existing repo skill into the catalog. A task asks to add an external published skill to the catalog. The skill is company-private (belongs in that company's library via the Skills UI/API, not the shipped catalog). You only need a repo-internal agent skill for working on Paperclip itself — that goes in .agents/skills/ or skills/, with no catalog machinery. Understand exactly what the skill should teach before writing anything. Tweets / X links. Use the xc CLI (X API client). Paperclip engineering agent environments ship it p

This is an excerpt. Refer to the complete source and its current requirements.