agentleFS
Microsoft AzureKnown publisherAzure/azure-sdk-tools/.github/skills/markdown-token-optimizer/SKILL.md

markdown-token-optimizer

Skill135 starsChanged 2 months agoMITView on GitHub

Analyze markdown files for token efficiency and reduce context-window bloat. **UTILITY SKILL**. DO NOT USE FOR: code optimization, general file editing, non-markdown files. TRIGGERS: optimize markdown, reduce tokens, token count, token bloat, too many tokens, make concise, shrink file, file too large, optimize for AI, token efficiency, verbose markdown, reduce file size.

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    USE FOR: analyze markdown files for token efficiency and reduce context-window bloat WHEN: "optimize markdown", "reduce tokens", "token …

    line 17
  2. Distinctive:

    WHEN: "optimize markdown", "reduce tokens", "token count", "token bloat", "too many tokens", "make concise", "shrink file", "file too …

    line 18
  3. Distinctive:

    DO NOT USE FOR: code optimization, general file editing, non-markdown files

    line 19

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Markdown Token Optimizer

This skill analyzes markdown files for token efficiency and reduces context-window bloat by identifying verbose patterns, duplicated content, and oversized sections, then suggesting concise revisions that preserve meaning while making documentation easier for AI systems to consume.

Triggers

USE FOR: analyze markdown files for token efficiency and reduce context-window bloat WHEN: "optimize markdown", "reduce tokens", "token count", "token bloat", "too many tokens", "make concise", "shrink file", "file too large", "optimize for AI", "token efficiency", "verbose markdown", "reduce file size" DO NOT USE FOR: code optimization, general file editing, non-markdown files

Steps

  1. Count - Calculate tokens (~4 chars = 1 token), report totals
  2. Scan - Find patterns: emojis, verbosity, duplication, large blocks
  3. Suggest - Table with location, issue, fix, savings estimate
  4. Summary - Current/potential/savings with top recommendations

See ANTI-PATTERNS.md for detection patterns and OPTIMIZATION-PATTERNS.md for techniques.

Rules

  • Suggest only (no auto-modification)
  • Preserve clarity in all optimizations
  • SKILL.md target: <500 tokens, references: <1000 tokens

Examples

  • "Optimize this SKILL.md for tokens"
  • "Count tokens in references/SCORING.md"

Troubleshooting

High token count? Check for emojis, repeated headings, or verbose tables.

MCP Tools

ToolPurpose
NoneCLI-only; uses local file tools

CLI fallback: Primary mode is CLI-based. No MCP servers required.

References

  • OPTIMIZATION-PATTERNS.md - Optimization techniques
  • ANTI-PATTERNS.md - Token-wasting patterns

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.