rtk-optimizer

Wrap high-verbosity shell commands with RTK to reduce token consumption. Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens.

Quality

71%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

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

Quality

Content

42%

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

The skill provides a useful reference for RTK command mappings with concrete reduction percentages, but suffers from verbosity (duplicated information between supported commands and metrics sections), missing error handling workflows, and references to non-existent bundle files. The content tries to serve as both a behavioral prompt and a reference guide, which dilutes its effectiveness at either purpose.

Suggestions

Remove the 'Activation Examples' section and 'Recommendation' section — Claude can infer when to use RTK from the command mappings alone, and the recommendation restates existing content.

Consolidate the 'Supported Commands' and 'Metrics' sections into a single table to eliminate duplication of reduction percentages.

Add error handling guidance: what to do when RTK fails, how to fall back to raw commands, and how to handle version incompatibilities.

Either provide the referenced bundle files (docs/resource-evaluations/rtk-evaluation.md, examples/claude-md/rtk-optimized.md) or remove the references to avoid broken navigation.

Dimension	Reasoning	Score
Conciseness	The skill includes some unnecessary content like the 'Activation Examples' section (Claude doesn't need to be shown how to detect user intent), the 'Limitations' section mixing GitHub stars with actual limitations, and the 'Recommendation' section which largely restates what's already covered. The metrics section partially duplicates the supported commands section. However, the core command mappings are efficiently presented.	2 / 3
Actionability	The command mappings are concrete and useful (e.g., `git log` → `rtk git log`), and installation commands are copy-paste ready. However, the 'Usage Pattern' section uses a markdown template rather than executable code, and the skill conflates being a reference for Claude with being a behavioral prompt ('Acknowledge request', 'Suggest RTK optimization'). The actual RTK usage is straightforward but the skill doesn't provide complete executable examples of RTK output parsing or error handling.	2 / 3
Workflow Clarity	The usage pattern provides a basic sequence (detect → suggest → execute → track), but there's no validation or error handling workflow. What happens if RTK fails or produces unexpected output? The installation check is good, but there's no feedback loop for when RTK isn't installed or when the command fails. For a tool that wraps other commands, error recovery guidance is important.	2 / 3
Progressive Disclosure	No bundle files are provided, yet the skill references `docs/resource-evaluations/rtk-evaluation.md` and `examples/claude-md/rtk-optimized.md` which don't exist. The content is a monolithic document that could benefit from splitting the detailed metrics and command reference into separate files. All content is inline with no actual supporting files.	1 / 3
	Total	7 / 12 Passed

Description

100%

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

This is a strong skill description that concisely communicates both the purpose and trigger conditions. It uses third person voice, lists concrete command examples as trigger terms, and has an explicit 'Use when' clause. The description is well-targeted and distinctive, making it easy for Claude to select appropriately from a large skill set.

Dimension	Reasoning	Score
Specificity	The description names a concrete action ('Wrap high-verbosity shell commands with RTK') and lists specific examples of commands (git log, git diff, cargo test, pytest). It clearly describes what the skill does.	3 / 3
Completeness	Clearly answers both 'what' (wrap high-verbosity shell commands with RTK to reduce token consumption) and 'when' (explicit 'Use when' clause listing specific triggers like git log, git diff, cargo test, pytest, or other verbose CLI output).	3 / 3
Trigger Term Quality	Includes natural keywords users would encounter: 'git log', 'git diff', 'cargo test', 'pytest', 'verbose CLI output', 'context window tokens', 'shell commands'. These are terms a user or Claude would naturally associate with this need.	3 / 3
Distinctiveness Conflict Risk	This skill occupies a very clear niche — wrapping verbose CLI output with RTK for token reduction. It's unlikely to conflict with other skills since it targets a specific optimization technique for shell command output.	3 / 3
	Total	12 / 12 Passed

Validation

90%

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 — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: FlorianBruniaux/claude-code-ultimate-guide
Commit: bbaa00d

Reviewed: 3 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.