Stats
Actions
Tags
From core
Optimize documentation for conciseness and clarity. Strengthens vague instructions with explicit criteria, removes redundancy while preserving meaning, and tightens prose. Use when the user says 'optimize this doc', 'tighten this', 'make this more concise', 'clean up this documentation', 'this doc is too long', 'remove redundancy', or asks to improve a markdown/documentation file.
How this skill is triggered — by the user, by Claude, or both
Slash command
/core:optimize-docThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Make documentation more concise and clearer. Strengthen vague instructions, remove redundancy, preserve meaning.
Make documentation more concise and clearer. Strengthen vague instructions, remove redundancy, preserve meaning.
Priority order: Correctness > Efficiency > Conciseness. Never sacrifice meaning for brevity.
Idempotent: First pass strengthens and trims. Second pass tightens further. Subsequent passes produce no changes.
If the user specified a file, use it. Otherwise ask which file or directory to optimize.
Read the full document before making any changes.
For every instruction section, apply the Execution Test:
Can Claude execute this correctly without the content in question?
├─ NO → KEEP (execution-critical)
└─ YES
├─ Does it explain WHY (rationale/educational)? → REMOVE
├─ Does it show WHAT "correct" looks like? → KEEP
├─ Does it extract a reusable decision rule? → KEEP
└─ Is it redundant with another section? → REMOVE
Cover the examples and read only the instruction text:
If vague: Strengthen the instruction first — replace subjective terms with explicit criteria, convert narrative to steps, add thresholds. Keep all examples until the instruction can stand alone.
If clear: Evaluate whether examples are still needed (see keep/remove guidance below).
Strengthen vague instructions and remove redundancy in a single pass where possible. For complex documents, use multiple passes.
Output a summary of changes:
## Optimization Summary
**Changes:**
1. [Section] (Lines X-Y): [what changed and why]
**Metrics:** N lines removed | M sections strengthened
**Status:** Fully optimized | Run again for further tightening
→ Shows that "delete" means remove lines, not change checkbox)Never replace with references:
OK to replace with references:
Before consolidating duplicates, verify:
Never sacrifice for conciseness:
npx claudepluginhub trickycdm/tricky-cc-plugins --plugin coreGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.