Skill Packs
Curated groups of skills, tools, hooks, prompt surfaces, and scaffold assets
A pack turns repository evidence into a curated operating bundle.
The repo receives the right context without forcing every operator to assemble an AI setup by hand.
Pack Resolution
punks scaffold setup detects repo facts, maps those facts to packs, asks for confirmation, then writes the scaffold output. The CLI selects packs, not raw skills.
For this domain model, the important repo facts are simple: dependencies and file extensions. Dependencies show which frameworks, libraries, and toolchains are present. File extensions show which languages and source surfaces exist.
The CLI mechanics belong in the CLI domain. The Harness concept is that pack selection follows repo evidence.
Pack Types
The high-level model has two pack types:
| Pack Type | Selected By | Adds |
|---|---|---|
| Agnostic | Every harnessed repository. | Requirements, planning, review, docs, debug, quality, research, subagent workflow, and delivery workflow context. |
| Language | File extensions and language toolchain evidence. | Language-specific skills, prompts, examples, and validation expectations. |
Specific surfaces get their own pack pages only when they need durable conceptual guidance. Resolver details belong in the CLI domain.
The mandatory agnostic pack groups include debug, docs, planning, quality, research, requirements, and subagents. They carry phase wrappers such as delivery-phase, review-phase, debugging-phase, docs-ingest-phase, and requirements-phase; research also carries prototype for throwaway logic/UI prototypes, review for Standards versus Spec review framing, and autoreview as the structured review runtime. The docs pack also distributes writing-fragments, writing-beats, and writing-shape so substantial public-facing docs work can preserve durable private writer artifacts before final page output. Phase wrappers stay global orchestration entrypoints rather than scoped primary skills.
Pack Output
A selected pack can contribute several kinds of scaffold output:
| Output | Purpose |
|---|---|
| Skills | Install the execution contracts the repo should have available under .agents/skills. |
| Prompt guidance | Shape generated root and scoped prompt surfaces without turning packs into local product truth. |
| Subagent templates | Create scoped worker contracts that match the repo surfaces detected by the pack. |
| Hooks and tools | Attach required guardrails and tool expectations. Validation Gates, External Tool Contract, and Hooks explain those mechanics. |
| Source examples | Point agents toward useful upstream or package source when the surface benefits from comparison. |
Packs distribute operating context. Product requirements, business logic, and repo-specific source truth remain in the repository that owns them.
For a practical lookup of available skills and source SKILL.md files, use Skill Reference. This page stays focused on the pack model; the reference page lists individual skills.
For individual skills that deserve more operator judgment than a reference row can carry, use Atomic Skills.