skillbunlisted

# /skillbun -- Skill Bundler The Agent Skills spec defines single skills. A skill that depends on another (skillize needs skill-creator's eval tooling) has no way to declare or distribute that dependency. skillbun closes this gap: resolve deps, rename to avoid collisions, validate, bundle, ship. ## Process ### 1. Identify targets Accept one or more skill paths or names (full flag set under Usage). For each target, verify SKILL.md exists and validate: frontmatter has `name` and `description`, name matches directory, kebab-case. ### 2. Resolve dependencies Scan each skill's SKILL.md and reference files for inter-skill references. Detection heuristics: **Explicit** (high confidence): - "read the skill-creator SKILL.md" or similar - References to paths containing another skill's name - "follow skill-creator's section on X" **Implicit** (medium confidence): - "use /other-skill" or "invoke /other-skill" - References to scripts/agents/assets in another skill's directory **System** (note in manifest, don't bundle): - `compatibility` field requirements (git, python, docker) Build a dependency graph. Check for cycles. Present for confirmation: ``` skillize └── skill-creator (eval pipeline, scripts, agents) 2 skills, 0 cycles Bundle? [Y/n] ``` ### 3. Rename for distribution Skills bundled from third-party sources should be renamed to avoid collision with independently installed copies. The rename must be consistent across three places: 1. **Directory name**: `skill-crea