Skill Bundler

Skill Bundler

Create or review Skill Bundles. A Skill Bundle does not provide domain capabilities itself; only the bundled Sub-Skills do the real work.

Core Rules

• Use skill_bundle_template.md as the authoritative template for the generated bundle SKILL.md.
• Keep the generated bundle SKILL.md short: runtime rule, dispatch map, and essential bundle-specific notes only.
• In the generated dispatch map, list every Sub-Skill as its own bullet; do not group multiple Sub-Skills into one dispatch entry.
• Do not copy Sub-Skill content into the generated bundle SKILL.md.
• Copy source skill folders whole, then rename only each copied SKILL.md to SUB_SKILL.md.
• Preserve copied files, assets, scripts, references, notices, and licenses unless the user explicitly asks for cleanup.
• For Git-backed source skills, record the source repository and resolved base commit in bundled-skills/manifest.json.

Workflow

1. Confirm the bundle name, folder slug, source skills, and bundle icon.
2. Inspect each source skill to understand its trigger, purpose, resources, and license/source notes.
3. Create the bundle folder with SKILL.md, agents/openai.yaml, and bundled-skills/.
4. Copy each source skill into bundled-skills/<subskill-slug>/.
5. Rename each copied top-level SKILL.md to SUB_SKILL.md; do not leave discoverable SKILL.md files below bundled-skills/.
6. Fill skill_bundle_template.md to write the generated bundle SKILL.md.
7. Add a compact bundled-skills/index.json for runtime routing when the dispatch map is not enough.
8. Add a bundled-skills/manifest.json only for review, audit, source, license, and update context. For every Git-backed source, include at least its repository URL and resolved base commit; include tag, branch, or source path when known.
9. Validate the bundle before handing it back.

Generated Bundle Shape

<bundle-slug>/
  SKILL.md
  agents/openai.yaml
  bundled-skills/
    index.json
    manifest.json
    <subskill-slug>/
      SUB_SKILL.md
      ...