// Use when starting any conversation involving bundle-plugins — blueprinting, scaffolding, authoring, auditing, testing, optimizing, or releasing. Also use when feeling unsure which bundles-forge skill applies
Use when reviewing a bundle-plugin for structural issues, version drift, skill quality, workflow integration, or security risks — before releasing, after changes, or after adding skills. Auto-detects scope (full project vs skill vs workflow)
Use when writing, completing, improving, or adapting SKILL.md and agents/*.md in a bundle-plugin — integrating external skills, filling scaffolded stubs, or rewriting for better triggering and token efficiency
Use when generating project structure for new bundle-plugins, adding or removing platform support (Claude Code, Cursor, Codex, OpenCode, Gemini CLI, OpenClaw), updating platform manifests, or migrating hooks and configuration between platforms
Use when optimizing a bundle-plugin or single skill — improving descriptions, reducing tokens, fixing audit findings, restructuring workflows, adding skills to fill gaps, or iterating on user feedback
Use when planning new bundle-plugins, splitting complex skills, combining skills into bundles, or exploring a vague idea about packaging skills
Use when releasing a bundle-plugin, bumping versions, fixing version drift across manifests, setting up version sync infrastructure, updating CHANGELOG, publishing to marketplaces, or checking release readiness
| name | using-bundles-forge |
| description | Use when starting any conversation involving bundle-plugins — blueprinting, scaffolding, authoring, auditing, testing, optimizing, or releasing. Also use when feeling unsure which bundles-forge skill applies |
Before invoking any bundles-forge skill on a target directory, verify the target is a bundle-plugin project:
skills/ directory?package.json?If neither exists, inform the user: "This directory doesn't appear to be a bundle-plugin project. Bundles Forge skills are designed for bundle-plugins (repositories where skills are the primary content). Would you like to create a new bundle-plugin here, or did you mean to point to a different directory?"
Exception: bundles-forge:auditing and bundles-forge:optimizing can also operate on individual skill folders or files — they don't require a full bundle-plugin project.
In Claude Code: Use the Skill tool. When you invoke a skill, its content is loaded — follow it directly.
In Cursor: Use the Skill tool.
In Gemini CLI: Skills activate via the activate_skill tool. See references/gemini-tools.md for tool mapping.
In Codex: Skills are discovered from ~/.agents/skills/. See references/codex-tools.md for tool mapping.
In OpenClaw: Skills auto-load from the bundle's skills/ directory. See references/openclaw-tools.md for tool mapping.
Skills use Claude Code tool names as the default. Non-Claude-Code platforms: see the tool mapping references in this directory for equivalents.
Invoke relevant skills BEFORE any response or action when working with bundle-plugins. If there's even a small chance a skill applies, invoke it to check.
User message about bundle-plugins
→ Might any skill apply?
→ yes → Invoke Skill tool → Follow skill → Respond
→ no → Respond directly
These skills diagnose, decide, and delegate. They orchestrate other skills to accomplish multi-step goals.
| Skill | Role | When to Use |
|---|---|---|
bundles-forge:blueprinting | New-project orchestrator | Planning new bundle-plugins, splitting complex skills, or composing skills into bundles. Orchestrates the full creation pipeline: scaffolding → authoring → workflow design → auditing |
bundles-forge:optimizing | Improvement orchestrator | Engineering optimization, feedback iteration, descriptions, tokens, adding skills, restructuring workflows. Delegates content changes to authoring |
bundles-forge:releasing | Release pipeline orchestrator | Version management, release pipeline: audit, test, version bump, publish |
These skills do one thing well. They can be invoked directly by users or dispatched by orchestrators.
| Skill | Role | When to Use |
|---|---|---|
bundles-forge:scaffolding | Structure generator | Generating project structure, adding or removing platform support |
bundles-forge:authoring | Content writer | Writing or improving SKILL.md content and agent definitions (agents/*.md) |
bundles-forge:auditing | Diagnostic reporter | Reviewing a project for quality issues, security risks — outputs reports, does not orchestrate fixes |
bundles-forge:testing | Dynamic verifier | Testing a plugin locally — dev-marketplace setup, hook smoke tests, component discovery, cross-platform readiness |
| Skill | Purpose |
|---|---|
bundles-forge:using-bundles-forge | Bootstrap meta-skill — you're reading it now (auto-loaded by hooks) |
When multiple skills could apply, prefer orchestrators over executors:
bundles-forge:blueprinting (orchestrates scaffolding, authoring, auditing)bundles-forge:optimizing (orchestrates authoring, scaffolding, auditing)bundles-forge:releasing (orchestrates auditing, testing, optimizing)bundles-forge:authoring (when you just need to write/improve a SKILL.md)bundles-forge:scaffolding (when you just need to add/remove a platform)bundles-forge:auditing (when you just need a diagnostic report)bundles-forge:testing (when you just need to verify a plugin works locally)dev-workflows, data-tools)name frontmatter field<project>:<skill-name>using-<project>agents/<role>.mdThe skill itself declares which type it is.
routing-context — skill routing table, platform adaptation guidance, and instruction priority for the current session