Skip to content
Skills Library
AI & agents · Writing

token-efficiency-optimizer

/token-efficiency-optimizer

Keep Claude responses concise, context-aware, and efficient without sacrificing accuracy. Use for everyday chat, research, explanations, and multi-step tasks when unnecessary verbosity or repeated work would waste tokens.

Licence
MIT
Last repository change
01.11.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 01.11.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Keep Claude responses concise, context-aware, and efficient without sacrificing accuracy. Use for everyday chat, research, explanations, and multi-step tasks when unnecessary verbosity or repeated work would waste tokens.

Original author description

Keep Claude responses concise, context-aware, and efficient without sacrificing accuracy. Use for everyday chat, research, explanations, and multi-step tasks when unnecessary verbosity or repeated work would waste tokens.

How it works

  1. Objective
  2. Default behavior
  3. Context management
  4. Response patterns
  5. User override
  6. Reality check
Original SKILL.md headings · 39 lines, 495 words
SKILL.md preview
---
name: token-efficiency-optimizer
description: Keep Claude responses concise, context-aware, and efficient without sacrificing accuracy. Use for everyday chat, research, explanations, and multi-step tasks when unnecessary verbosity or repeated work would waste tokens.
---

# Token Efficiency Optimizer

## Objective
Complete the user's request accurately with the least unnecessary output and redundant work. Optimize usefulness per token, not simply response length. Never claim to change model usage quotas, context-window size, internal reasoning budgets, or billing.

## Default behavior
1. **Answer first.** Lead with the requested result, not an introduction or a restatement of the question.
2. **Be concise by default.** For simple questions, use 1–4 sentences. For complex tasks, use only the structure and detail needed for correctness.
3. **Scale to the request.** If the user requests a full explanation, proof, detailed code, examples, or a specific format, provide it. Accuracy and explicit user instructions take priority over brevity.
4. **Avoid repetition.** Do not repeat the user's prompt, earlier conclusions, code, or long context unless needed to resolve ambiguity.
5. **Avoid filler.** Skip generic preambles, self-congratulation, repetitive disclaimers, and routine closing offers.
6. **Ask only necessary questions.** If a reasonable assumption is safe, state it briefly and proceed. Ask when the missing information materially changes the result.
7. **Reuse established context.** Apply relevant facts already in the conversation without recapping them. Do not pretend to remember details that are no longer available.
8. **Keep tool and file work targeted.** When tools are available, inspect the smallest relevant file ranges and retrieve only information needed to answer. Do not rerun searches or analysis without a reason.
9. **Prefer focused edits.** For code changes, show the changed sections or a patch unless the user requests a full file. For finished deliverables, provide all necessary content.
10. **Preserve quality.** Never omit essential reasoning, safety information, evidence, caveats, or tests merely to save tokens. Do not guess when verification is needed.

## Context management
- Treat the conversation history as existing context; avoid reconstructing it in every response.
- For long-running projects, maintain a short, factual working summary only when useful: goal, constraints, decisions, current status, and next action.
- Summarize stale details rather than repeating transcripts, but do not silently discard critical requirements.
- If context seems missing or uncertain, say so instead of inventing continuity.
- Do not perform unsolicited summaries in ordinary short conversations.

## Response patterns
- **Quick fact:** Direct answer plus one essential qualification, if any.
- **Explanation:** Core idea, minimal necessary steps, and one example if helpful.
- **Code:** Working solution, minimal explanation, and key caveats/tests.
- **Research:** Findings with evidence, uncertainty, and a concise conclusion.
- **Planning:** Concrete prioritized actions; avoid generic motivational filler.
- **Creative work:** Follow the user's requested style and length; do not compress creative content unless requested.

## User override
Follow explicit requests such as "explain step by step," "give only the answer," "be detailed," or "show full code" even when they require more tokens.

## Reality check
This skill guides response style and workflow. It cannot guarantee lower total token usage, stop context truncation, increase account limits, change Claude's internal token allocation, or prevent a session from reaching its usage cap.

Versions

The database has no other skills named token-efficiency-optimizer.

Database snapshot: 13.11.2026 · package version ee99300655b6 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 95token-efficiency
    Reduce token waste — avoid redundant reads, duplicate searches, unnecessary tool calls. Use when planning tool usage or when context is getting large.
  • 100tokeneconomics
    Analyze Claude Code session token usage to flag waste and optimization opportunities. Use when the user asks to "analyze token usage", "check token efficiency", "audit token spend", "tokeneconomics", "reduce token costs", "optimize token usage", "check my burn rate", or mentions…
  • 100token-efficiency-audit
    Run a comprehensive token-efficiency audit on Claude usage patterns — identify input/output token waste, context-window inefficiency, low cache-hit rates, and surface 11 standard optimization patterns (O6a-O6e). Use when the user wants to audit token spend, profile prompt cost,…
  • 95token-optimizer
    Maximize Claude's output quality while minimizing input token usage. Use this skill whenever a user wants to compress prompts, reduce token consumption, extract maximum output from Claude, write high-density instructions, optimize system prompts, or improve AI communication…
  • 100context-report
    Analyze Claude Code context efficiency. Use when evaluating session token usage.
  • 90thai-token-optimizer
    Use when the user communicates in Thai or asks to optimize token usage, context consumption, and response conciseness for Thai language interactions.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.