skillset-dev
Route work on the Skillset compiler repository through its tenets, accepted ADRs, and focused contributor skills. Use whenever changing or reviewing Skillset source, compiler behavior, schemas, tests, fixtures, generated output, or contributor workflows.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- skillset-dev
- metadata
- { "version": "0.1.0", "skillset.schema": "1" }
- description
- Route work on the Skillset compiler repository through its tenets, accepted ADRs, and focused contributor skills. Use whenever changing or reviewing Skillset source, compiler behavior, schemas, tests, fixtures, generated output, or contributor workflows.
03 SKILL.md 正文
Skillset Development
Start With Doctrine
- Read
AGENTS.mdanddocs/project/tenets.mdbefore changing a contract or generated-output promise. - Find the governing accepted decisions in
docs/adrs/README.mdanddocs/adrs/decision-map.json, then read the relevant ADRs rather than relying on their titles. - If implementation and doctrine disagree, change the implementation or make an explicit decision. Do not reconcile the conflict only in tactical documentation.
Route The Work
Use the narrowest specialist that owns the change:
- Compiler behavior, rendering, commands, or package placement: use
skillset-dev-compiler. - Config, frontmatter, source vocabulary, or shared validation: use
skillset-dev-schema. - Tests, fixtures, conformance, or verification strategy: use
skillset-dev-testing.
Use more than one specialist only when the change crosses their ownership boundaries. Keep one semantic owner and let the other specialist supply verification or integration guidance.
For ADR lifecycle work, use skillset-adrs, then follow docs/adrs/README.md and the repository ADR helper. For provider evidence, read the official provider material before changing a support claim. Dedicated provider, documentation, and release specialists are separate follow-up work; do not invent them inside another skill.
Preserve The Boundary
- Contributor material may read, invoke, test, and extend the public Skillset product.
- Public
skillset*artifacts must never route to or depend onskillset-dev*, repository internals, fixtures, or release machinery. bun run public-closure:guardenforces that boundary only over generatedplugins/skillset/**output. Contributor and self-hosted.agents/,.claude/,.cursor/, and.skillset/trees are intentionally outside its scan root.- Edit
.skillset/andskillset.yamlas canonical self-hosted source. Rebuild generated.agents/,.claude/,.cursor/, andplugins/output; never hand-edit it as source truth. - Build does not authorize installation, activation, trust, publication, or user-level provider configuration changes.
Record The Change
CI checks two independent release records, so record both kinds of change before pushing:
- Change entry for any edit to a
.skillset/source unit (a skill, a plugin, orRULES.md). Runbun ./apps/skillset/src/cli.ts check --ci --root .; it names each uncovered scope and prints the exactskillset change add --scope <unit> --bump <bump> --reason "<reason>"command, orskillset change refresh @<id> --yeswhen a pending entry for that scope already exists with stale evidence. - Changeset (
.changeset/*.md) for published-package behavior or payload.bun run changeset:checksays whether the branch needs one.
A change that touches both needs both. Neither record stands in for the other.
Finish The Loop
Implement the smallest complete change, verify it through the owning specialist, rebuild self-hosted output when source changes, record the change, inspect the generated diff, and run the repository aggregate gate before handoff.
04 同仓库更多 Skills
use-skillset
Use the skillset compiler in a repo with skillset.yaml or a .skillset/ directory. Covers creating a workspace, adding skills, rules, agents, hooks, and plugins, building and checking Claude, Codex, and Cursor output, repairing stale or hand-edited generated files, recording changes, cutting releases, importing existing skills, and marketplaces. Use when asked to add a rule, record a change, cut a release, or fix generated output.
broken
42
reference
Keep project references organized for review.
portable-proof
Proves that generated Agent Skills are accepted by pinned external consumers.
plugin-proof
Proves immediate-child skill fidelity inside an Agent Plugins package.
sink
Kitchen-sink skill exercising shared resources and custom resource mappings.