Skip to content

skilldrop·docs·How-to

Use the Core pack

Install the Core pack, run its first task, and follow a typical session step by step.

The cross-role toolkit every pack builds on: structured intake, document critique, the review council, output hygiene, and the decision graph behind a codebase, plus the ship-a-draft wrapper. Installed automatically with every role pack.

Reach for it when: You have rough notes, a transcript or a ticket and want a finished document, not a first draft.

1. Install it

npx skilldrop-cli install --pack core                 # Claude Code, your user folder
npx skilldrop-cli install --pack core --project       # Claude Code, this repo
npx skilldrop-cli install --pack core --ide cursor    # or kiro, codex, antigravity, copilot
npx skilldrop-cli install --pack core --local         # this repo, hidden from git

In Claude Code you can also add the marketplace once (/plugin marketplace add sananthanarayan/skilldrop) and run /plugin install core@skilldrop.

2. Run the first task: turn rough notes into a structured brief, then get a verdict on the draft

Paste this into your agent:

Here are my notes from today's planning call: <paste them>. Turn them into a brief, then critique the draft you write from it.

How to tell it worked: brief-intake returns a structured brief with gaps tagged, and doc-critique ends with a verdict: SHIP IT, SHIP WITH CHANGES, MAJOR REWRITE or WRONG ARTIFACT.

If nothing happens: If neither skill activates, check that brief-intake/SKILL.md and doc-critique/SKILL.md exist in your skills folder (~/.claude/skills/ by default). In Claude Code, start a new session after installing.

3. A typical session

Bring:

A session takes about 20–45 minutes.

  1. brief-intake: Paste the raw material and name the document you want it to become. You get: A structured brief with every field tagged explicit, implied, inferred or missing, plus a list of what the next step will refuse to start without. You decide: Answer or explicitly accept each missing field before drafting; the brief never fills them in for you.
  2. doc-critique: Hand over the draft you wrote from the brief, by hand or with any generator skill. You get: A critique that opens with a verdict and lists findings as blocker, major, minor or nit, each pointing to the section and suggesting a fix. You decide: Gate G5: SHIP IT or SHIP WITH CHANGES moves on; MAJOR REWRITE sends you back to the brief; WRONG ARTIFACT means you need a different kind of document.
  3. output-hygiene: Run it on the settled draft and say where it is going (markdown, commit message, plain text). You get: The draft with invisible Unicode, provenance trailers and chat closers stripped, prose tells quoted with rewrites, and a 'Not touched' list.

You end with: A reviewed, cleaned document with its verdict, the changes it carried, and a note of what the scrub did not touch.

4. Run it as a loop

A loop runs the skills in order and stops at each gate for a verdict. Install and start one:

npx skilldrop-cli install --loop --pack core

Next

Edit this page on GitHub · View source