CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./examples/skills/rtk-optimizer/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

63%Weight 40%Scale 1-5

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

The body is well-organized with concrete command mappings, an install check, and sensible edge cases, but it is held back by redundant sections (metrics and use/skip guidance each appear twice), padded conversational templates, and references pointing to non-existent files.

Suggestions

Merge the 'Metrics (verified)' section into the Supported commands tables and fold 'Recommendation' into 'Edge cases' so percentages and use/skip guidance appear only once.

Remove or actually bundle the referenced paths 'docs/resource-evaluations/rtk-evaluation.md' and 'examples/claude-md/rtk-optimized.md' — they do not exist in the skill bundle.

Replace the 'Usage pattern' conversational markdown template with one or two concrete executable examples showing the actual rtk invocation and condensed output.

DimensionReasoningScore

Conciseness

The command tables are dense and useful, but reduction percentages are stated twice ('92.3% reduction' in Supported commands and again in 'Metrics (verified)'), use/skip guidance is duplicated across 'Edge cases' and 'Recommendation', and 'Limitations' carries time-sensitive stats ('446 stars on GitHub... 30 releases in 23 days') outside any deprecated section.

3 / 5

Actionability

Concrete copy-paste commands throughout: mappings like 'git log → rtk git log', install verification ('rtk --version'), fallback installs ('brew install rtk-ai/tap/rtk', 'cargo install rtk'), and 'rtk gain'. Minor gap: the 'Usage pattern' section is a conversational template ('1. Acknowledge request') rather than executable invocation examples.

4 / 5

Workflow Clarity

'How it works' gives a clear 4-step sequence (Detect → Suggest → Execute when user confirms → Track) with an explicit install-validation checkpoint and fallback commands, plus edge-case handling. Missing error-recovery if the RTK output is wrong or the command fails, so it sits at anchor 4 rather than 5.

4 / 5

Progressive Disclosure

Sections are clearly headed, but the References section points to 'docs/resource-evaluations/rtk-evaluation.md' and 'examples/claude-md/rtk-optimized.md', which do not exist in the bundle, and detailed metrics plus the CLAUDE.md configuration template are inlined in a 135-line file instead of being split out.

3 / 5

Total

14

/

20

Passed

Description

78%Weight 40%Scale 1-5

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 is strong: third-person voice, a clear what-and-when structure with concrete trigger commands, and a distinct token-reduction niche. Its only weakness is that it names a single capability and omits several natural trigger terms for commands the skill supports.

DimensionReasoningScore

Specificity

'Wrap high-verbosity shell commands with RTK to reduce token consumption' names the domain and one concrete action, but does not list several distinct capabilities; the command names are triggers rather than actions, so it matches anchor 3 rather than 4.

3 / 5

Completeness

It explicitly answers both what ('Wrap high-verbosity shell commands with RTK to reduce token consumption') and when ('Use when running git log, git diff, cargo test, pytest, or other verbose CLI output that wastes context window tokens') with concrete trigger phrases, matching the anchor 5 example.

5 / 5

Trigger Term Quality

'git log, git diff, cargo test, pytest' are natural phrases users would say, with 'other verbose CLI output' as a catch-all; however, natural terms for other supported commands (find, grep, vitest, pnpm, go test, gh) are missing, which is more than the comprehensive coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The RTK-wrapping niche is distinct with specific trigger commands, but trigger terms like 'git log' and 'git diff' overlap with git-related skills and 'verbose CLI output' is broad enough to fire on general shell work, giving minor overlap risk rather than minimal.

4 / 5

Total

16

/

20

Passed

Validation

93%

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

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

FlorianBruniaux/claude-code-ultimate-guide

Path

examples/skills/rtk-optimizer/SKILL.md

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.