Agent skill

instruction-optimizer

Use when instruction files (skills, prompts, CLAUDE.md) are too long or need token reduction while preserving capability. Triggers: "optimize instructions", "reduce tokens", "compress skill", "make this shorter", "too verbose".

Stars 163
Forks 31

Install this agent skill to your Project

npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/other/instruction-optimizer

SKILL.md

Instruction Optimizer

Invariant Principles

  1. Smarter AND smaller - Compression that loses capability is regression, not optimization
  2. Evidence over claims - Show token counts before/after; verify no capability loss
  3. Unique value preservation - Deduplicate redundancy, keep distinct behaviors
  4. Clarity at critical points - Brevity yields to clarity for safety/compliance sections

Reasoning Schema

Inputs

Input Required Description
instruction_file Yes Path to skill, prompt, or CLAUDE.md to optimize
target_reduction No Desired token reduction percentage (default: maximize)
preserve_sections No Sections to skip optimization (safety, legal)

Outputs

Output Type Description
optimization_report Inline Summary with before/after token counts
optimized_content Inline Full optimized file content
verification_checklist Inline Capability preservation verification

Declarative Principles

Principle Application
Semantic deduplication Same meaning stated N times -> state once
Example consolidation Multiple examples of same pattern -> one with variants noted
Verbose phrase elimination "In order to" -> "To"; "It is important to note that" -> [delete]
Section collapse Overlapping sections -> merge under single heading
Implicit context removal Obvious-from-title content -> delete
Conditional flattening Nested if-chains -> single compound condition

Compression Patterns

"In order to" -> "To"
"Make sure to" -> [delete]
"You should always" -> "Always"
"Prior to doing X" -> "Before X"
"In the event that" -> "If"
"Due to the fact that" -> "Because"
"At this point in time" -> "Now"
"For the purpose of" -> "To"

Process

  1. Read file completely
  2. Estimate tokens (words * 1.3)
  3. Identify safety-critical sections (skip these)
  4. Apply compression patterns
  5. Draft optimized version
  6. Verify capability preservation
  7. Calculate savings, present diff

Output Format

markdown
## Optimization Report: [filename]

### Summary
- Before: ~X tokens | After: ~Y tokens | Savings: Z (N%)

### Changes
1. [Technique]: [Description] (-N tokens)

### Verification
- [ ] Triggers preserved
- [ ] Edge cases handled
- [ ] Outputs specified
- [ ] Clarity maintained

### Optimized Content
[full content]

Skip Optimization When

  • Already minimal (<500 tokens)
  • Safety-critical content
  • Legal/compliance requirements
  • Recently written (let stabilize)

Self-Check

Before completing:

  • Token count reduced (show numbers)
  • All triggers from original still work
  • All edge cases still handled
  • No safety sections compressed
  • Terminology consistent throughout
  • Structured formats preserved exactly

If ANY unchecked: STOP and fix before presenting result.

Expand your agent's capabilities with these related and highly-rated skills.

Didn't find tool you were looking for?

Be as detailed as possible for better results