context-optimizer

Optimize token usage and context management. Use when sessions feel slow, context is degraded, or you're running out of budget.

Quality

74%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/context-optimizer/SKILL.md

Quality

Discovery

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description has good structural completeness with an explicit 'Use when' clause covering multiple trigger scenarios, but it lacks specificity about what concrete actions the skill actually performs. The 'what' portion is too abstract—'optimize token usage and context management' reads more like a goal than a set of actionable capabilities. The trigger terms are reasonable but could be expanded with more natural user language.

Suggestions

Replace the vague 'optimize token usage and context management' with specific concrete actions, e.g., 'Summarize conversation history, compress prompts, prune unused context, and estimate token costs'.

Add more natural trigger term variations to the 'Use when' clause, such as 'token limit', 'context window full', 'too many tokens', 'cost reduction', or 'prompt too long'.

Dimension	Reasoning	Score
Specificity	The description uses vague language like 'optimize token usage and context management' without listing any concrete actions. What specific actions does this skill perform? There are no specifics like 'summarize conversation history', 'prune unused context', or 'compress prompts'.	1 / 3
Completeness	The description does answer both 'what' (optimize token usage and context management) and 'when' (sessions feel slow, context is degraded, running out of budget) with an explicit 'Use when' clause containing trigger conditions.	3 / 3
Trigger Term Quality	Includes some relevant terms like 'token usage', 'context', 'slow', 'budget' that users might mention, but misses common variations like 'too long', 'token limit', 'context window', 'running out of tokens', 'cost reduction', or 'prompt optimization'.	2 / 3
Distinctiveness Conflict Risk	'Context management' and 'optimization' are somewhat broad terms that could overlap with performance tuning, cost management, or prompt engineering skills. However, the combination of 'token usage' with 'context degraded' and 'budget' provides some distinctiveness.	2 / 3
	Total	8 / 12 Passed

Implementation

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, well-structured skill that efficiently communicates context management strategies. It excels at conciseness through effective use of tables and terse instructions, and provides highly actionable guidance with specific commands, thresholds, and configuration snippets. The only minor weakness is that all content is inline, though the skill's moderate length makes this acceptable.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient throughout. It uses tables for quick scanning, avoids explaining what context windows or tokens are, and assumes Claude already understands these concepts. Every section delivers actionable information without padding.	3 / 3
Actionability	Provides concrete commands (/compact, /context, /mcp, /resume), specific configuration JSON for auto-compaction, exact thresholds (70%, 90%), and specific examples of good vs bad prompts. The guidance is immediately executable.	3 / 3
Workflow Clarity	The Quick Diagnosis section provides a clear decision tree (check → threshold → action). The Context Budget Planning table sequences phases with explicit thresholds and remediation actions. The 'When Context Is Degraded' section provides an escalating fix sequence with clear steps.	3 / 3
Progressive Disclosure	The content is well-organized with clear sections and headers, but everything is inline in a single file. Some sections like CLAUDE.md Optimization or Subagent Delegation could benefit from linking to more detailed reference files. However, the skill is under ~80 lines and reasonably self-contained, so this is a minor issue.	2 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: rohitg00/pro-workflow
Commit: 1de1554

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.