Optimizing

This is the skill you invoke when your bundle is working but messy, or when a skill keeps misfiring. It runs the audit suite, then systematically tightens descriptions for better triggering, cuts token bloat, and fixes structural issues like content in the wrong layer or workflows that should be separate skills. The execution flow is rigid (diagnose, decide, delegate to authoring, verify), but target selection adapts to what the audits surface. Notable feature: includes an A/B eval protocol for description changes so you can measure whether your "improvement" actually regresses trigger accuracy. Most useful after initial development when you're polishing for production or responding to user feedback that a skill isn't firing when it should.

GitHub stars: 297
last updated: Apr 27, 2026

View on GitHub

Install

$ npx -y skills add odradekai/bundles-forge --skill optimizing --agent claude-code

Installs into .claude/skills of the current project.

Files

Optimizing Bundle-Plugins

Overview

Orchestrate targeted improvement of a bundle-plugin project or a single skill. Unlike a full audit, optimization focuses on goals: better triggering, lower token cost, tighter workflow chains, and feedback-driven skill refinement. This skill diagnoses issues, decides on improvements, and delegates content changes to bundles-forge:authoring.

Core principle: Optimize for the agent's experience. Diagnose → decide → delegate → verify.

Skill type: Hybrid — follow the execution flow rigidly (diagnose → decide → delegate → verify), but select targets and adapt execution strategies flexibly based on audit findings and user goals.

Announce at start: "I'm using the optimizing skill to improve [this project / this skill]."