Individual skill

skill-pack-curator

Designs the membership and structure of a skill pack - persona, member selection, install sequence, cross-links, and what to add or cut. Use when someone asks "which skills should go in this skill pack", "design the membership of a new skill pack", "decide which skills to add or cut from a pack", or is turning a vertical (an industry or role) into a coherent bundle. Do NOT use to grade or rewrite a finished pack to a quality bar (use skill-auditor) - this designs composition.

skills/skill-pack-curator/SKILL.md

Read pinned source

Source commit 97a13607d669157a4a16d5ba79b77f208319f7b9

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
Yes
Observed behavior
Not checked yet
Last checked
Nov 6, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
24
Repository last updated
Oct 13, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Skill Pack Curator

A pack is not a dump of related skills. It is a curated operating system for one persona or one workflow, where every member earns its place, the members route to each other, and the whole covers the job end to end. The costly mistake this prevents: shipping a "collection" - ten adjacent skills with no sequence, no cross-links, and no reason to buy the bundle over any one member.

## Inputs to collect

1. The persona or workflow, in one sentence: "This pack is for [persona] who need to [job]."
2. The existing catalog - which candidate members already exist versus need creating.
3. The methodology, if any, the pack encodes (a named framework, a book, a practitioner playbook).

## Persona packs vs workflow packs

A persona pack serves one role across many task types ("Engineering Manager Toolkit"). A workflow pack covers one end-to-end workflow ("Database Migration Workflow"). Choose one mode and hold it; mixing both makes membership decisions arbitrary. Default: vertical/industry packs are persona packs; process packs are workflow packs.
Back to top