Agent skill · Content & Marketing

optimize-prompt-token-efficiency

Iteratively optimizes prompts for token efficiency by maximizing information density - reduces verbosity, removes redundancy, tightens phrasing while preserving semantic content. Use when asked to compress, shorten, reduce tokens, tighten, maximize density, increase information density, or make a prompt more concise.

majiayu000github.com/majiayu000GitHub ↗
claude-codeMIT
Install
npx skills add majiayu000/claude-skill-registry --skill optimize-prompt-token-efficiency --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 11 KB
Bundled scripts: none
Path: skills/ai-llm/optimize-prompt-token-efficiency/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Optimize Prompt Token Efficiency Iteratively optimize prompt token efficiency by maximizing information density through verification loops. Primary goal: reduce token consumption while preserving all semantic content for AI-consumed prompts (CLAUDE.md, skills, agent prompts, specs). ## Overview This skill transforms verbose prompts into token-efficient versions through: 1. **Verification First** - `prompt-token-efficiency-verifier` checks for inefficiencies before any changes 2. **Optimization** - Apply targeted compression based on verifier feedback 3. **Re-verification** - Verify compression is lossless, iterate if issues remain (max 5 iterations) 4. **Output** - Atomic replacement only after verification passes **Loop**: Read → Verify → (Exit if efficient) → Optimize based on feedback → Re-verify → (Iterate if issues) → Output **Key principle**: Don't try to optimize in one pass. The verifier drives all changes - if it finds no inefficiencies, the prompt is already token-efficient. ## Workflow ### Phase 0: Create Todo List (TodoWrite immediately) Create todos tracking workflow phases. List reflects areas of work, not fixed steps. **Starter todos**: ``` - [ ] Input validation -

What's inside
Steps it walks through
  1. Overview
  2. Workflow
  3. Phase 0: Create Todo List (TodoWrite immediately)
  4. Phase 1: Input Validation
  5. Phase 2: Initial Verification
  6. Phase 3: Optimization Loop (Verifier-Driven)
  7. Compression Techniques
  8. Phase 4: Output
  9. Key Principles
  10. Edge Cases
  11. Example Usage
  12. Example Output
Ships with 1 file
  • metadata.json
Commands it runs
Replace original atomically
mv {working_path} {original_path}
Optimize a verbose CLAUDE.md
Optimize a skill file
Optimize an agent prompt
More from claude-skill-registry
All skills →
About this skill
What does the optimize-prompt-token-efficiency skill do?

Iteratively optimizes prompts for token efficiency by maximizing information density - reduces verbosity, removes redundancy, tightens phrasing while preserving semantic content. Use when asked to compress, shorten, reduce tokens, tighten, maximize density, increase information density, or make a prompt more concise.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill optimize-prompt-token-efficiency --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going