Repository navigation
v3.4.0 — token-economy & skill-composition guidance
Covers three releases (v3.3.0, v3.3.1, v3.4.0) shipped between v3.2.1 and this tag. No breaking changes to scripts.* imports or CLI invocations.
What changed and why
Token-economy guidance (v3.4.0) — added references/token-economy.md to answer a recurring question: how do you structure a skill so it doesn't burn the model's context budget? The reference covers the three progressive-disclosure levers (metadata is always-on; SKILL.md is a <500-line index; references/ and scripts/ cost nothing until loaded), one-skill-vs-many composition, and a recommended development track (scoping-changes → implementing-features → validating-code → reviewing-changes). Wired into SKILL.md and skill.yaml so the orphan checker can't silently drop it. (#51)
Development-practices guidance (v3.3.0) — added references/development-practices.md for skills that write code, fix bugs, or author PRs. Converted patterns from 84 real fix: commits into reusable guidance so agents don't rediscover the same failure modes. (#48)
Dogfood fix: bsc.py check failed on its own skill (v3.3.1) — checks() called validate_skill() without claude_code=True, so python bsc.py check skills/skill-creator always reported the legitimate model: key as an error. Fixed; --strict flag added for upload/API compat validation. Runs/ directory also added to .gitignore to prevent accidental staging of report artifacts. (#50)
Generated-test discovery and dependency path containment — tests generated into tests/generated/ were not discovered by pytest; fixed the collection path. Dependency paths can no longer escape the skill directory via relative traversal. (#44, #49)