Install any skill in seconds. Free to start, no credit card required.
Get Started Free →odradekai/optimizing
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
Passed 15 of 20 test cases with the skill, and 8 of 20 without it.
and 8 more in the full report
9 fixed8 passed either way4 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 9 test cases the skill fixed. Same model, same prompt, with and without the skill.
We need to check workflow chain integrity across all skills in `./my-plugin` before applying Target 3 fixes. What CLI tool command should be executed?
| Checked | Without skill | With skill |
|---|---|---|
| The response specifies executing bundles-forge audit-workflow. | Missed | Passed |
The instructions your model reads when the skill loads.
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]."
The target can be a local path, a GitHub URL, or a zip file. Normalize the input to a local directory before scope detection.
Edge cases & naming conventions:
bundles-forge:auditing—references/input-normalization.md
This is a mandatory step — do not skip it or improvise paths. Resolve the target to a local directory before proceeding to Scope Detection.
$CLAUDE_PROJECT_DIR or $CURSOR_PROJECT_DIR (plugin mode), falling back to the current working directory.<owner> and <repo> from the URL. Shallow-clone to <workspace>/.bundles-forge/repos/<owner>__<repo>/ using --depth 1 --no-checkout, then run git checkout. If the directory already exists, append a __<YYYYMMDD> timestamp to avoid collisions. Do not clone to /tmp/, ~/, or any path outside .bundles-forge/repos/.<workspace>/.bundles-forge/repos/<archive-name>/.See the canonical source for the full naming convention (version/timestamp suffixes), GitHub subdirectory URLs, and security rules.
Prerequisites: Target resolved to a local path (via Input Normalization above).
After normalization, determine the scope from the resolved local path:
| Target | How to Detect | Mode |
|---|
test cases passed, vs 8 / 20 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.