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.
63
75%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./examples/skills/rtk-optimizer/SKILL.mdQuality
Discovery
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 clearly communicates its purpose, provides specific trigger terms, and includes an explicit 'Use when' clause. It names concrete tools and commands, making it easy for Claude to select this skill when appropriate. The description is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists a concrete action ('Wrap high-verbosity shell commands with RTK to reduce token consumption') and names specific commands (git log, git diff, cargo test, pytest). Multiple concrete actions and tools are referenced. | 3 / 3 |
Completeness | Clearly answers 'what' (wrap high-verbosity shell commands with RTK to reduce token consumption) and 'when' (explicit 'Use when' clause listing specific commands and the general case of 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'. These are terms developers naturally use when dealing with verbose command output. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — focuses on a specific niche (RTK wrapping for token reduction of verbose CLI output). Unlikely to conflict with other skills since it targets a very particular optimization technique. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%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 table of RTK command mappings with verified metrics, which is its strongest asset. However, it suffers from including behavioral scripting (telling Claude how to suggest things to users) rather than focusing purely on actionable command substitutions, and it references bundle files that don't exist. The content could be significantly tightened by removing the activation examples, simplifying the usage pattern, and focusing on the command mapping table and edge cases.
Suggestions
Remove the 'Activation Examples' section — Claude doesn't need examples of how to detect user intent; focus on the command mapping reference table instead.
Replace the abstract 'Usage Pattern' markdown template with a concrete decision rule, e.g., 'Prefix any command from the Supported Commands list with `rtk` unless output is expected to be <100 chars.'
Add a validation step: after running an RTK-wrapped command, verify the output is non-empty and contains expected content before presenting results to the user.
Either provide the referenced bundle files (docs/resource-evaluations/rtk-evaluation.md, examples/claude-md/rtk-optimized.md) or remove the references to avoid dead links.
| 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 'Configuration' section showing how to add it to CLAUDE.md. However, the command mapping tables are efficient and the metrics are useful reference data. | 2 / 3 |
Actionability | The command mappings are concrete and the installation commands are copy-paste ready, but the core 'Usage Pattern' section is written as a markdown template describing behavior rather than providing executable guidance. The skill describes what to do abstractly ('Acknowledge request', 'Suggest RTK optimization') rather than giving concrete executable patterns. | 2 / 3 |
Workflow Clarity | The workflow steps (detect → suggest → execute → track) are listed but lack validation checkpoints. There's no guidance on what to do if RTK produces unexpected output, no error handling for failed commands, and the 'Usage Pattern' is more of a behavioral script than a validated workflow. The edge cases section partially compensates but doesn't include verification steps. | 2 / 3 |
Progressive Disclosure | References to external files (docs/resource-evaluations/rtk-evaluation.md, examples/claude-md/rtk-optimized.md) are mentioned but no bundle files exist to support them. The content is somewhat monolithic with metrics, configuration, and reference tables all inline when some could be split out. The structure has clear sections but the document is longer than it needs to be for a single-purpose skill. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
90%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 | |
- Commit
60a4372
- Reviewed
Table of Contents
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.