Hullo @FlorianBruniaux 👋 I ran your skills through `tessl skill review` at work and found some targeted improvements. Here's the full before/after: | Skill | Before | After | Change | |-------|--------|-------|--------| | talk-pipeline/orchestrator | 0% | 93% | +93% | | talk-pipeline/stage-3-concepts | 0% | 93% | +93% | | talk-pipeline/stage-4-position | 0% | 93% | +93% | | talk-pipeline/stage-1-extract | 0% | 85% | +85% | | talk-pipeline/stage-2-research | 0% | 85% | +85% | | talk-pipeline/stage-5-script | 0% | 85% | +85% | | talk-pipeline/stage-6-revision | 0% | 79% | +79% | | ccboard | 32% | 100% | +68% | | audit-agents-skills | 34% | 95% | +61% | | rtk-optimizer | 41% | 100% | +59% | | skill-creator | 52% | 89% | +37% | | voice-refine | 59% | 93% | +34% | | design-patterns | 59% | 85% | +26% | | cyber-defense-team | 76% | 100% | +24% | | landing-page-generator | 70% | 93% | +23% | | issue-triage | 73% | 89% | +16% | | pr-triage | 73% | 89% | +16% | | release-notes-generator | 78% | 85% | +7% | | guide-recap | 93% | 100% | +7% | **Average: 11% → 91% (+80%)** <details> <summary>Changes summary</summary> ### All 7 talk-pipeline skills (0% → 79-93%) - **Fixed `allowed-tools` frontmatter**: Changed from YAML list syntax (which fails validation) to comma-separated string format - **Improved descriptions**: Added specific actions and "Use when..." clauses to all pipeline stage descriptions ### ccboard (32% → 100%) - Rewrote description with concrete actions and "Use when..." clause - Removed ~80% bloat: architecture, credits, license, contributing, performance, limitations, roadmap sections - Kept commands table, navigation shortcuts, 3 usage examples, and troubleshooting - Added validation section ### audit-agents-skills (34% → 95%) - Rewrote description with concrete trigger terms and "Use when..." clause - Removed Industry Context section, verbose Purpose section, detection patterns, full JSON output example - Added validation checkpoints between workflow phases - Condensed scoring criteria tables ### rtk-optimizer (41% → 100%) - Rewrote description with natural user terms instead of jargon - Consolidated redundant metrics into single unified table - Removed redundant Configuration and Limitations sections - Added error handling and prerequisites sections ### skill-creator (52% → 89%) - Rewrote description with concrete actions and "Use when..." clause - Removed verbose explanatory sections Claude already understands - Restructured into clear 4-step workflow (Create → Template → Validate → Package) - Added explicit validation step ### voice-refine (59% → 93%) - Added "Use when..." clause with natural terms (voice memo, dictation, speech-to-text) - Removed Integration with Voice Tools section (Wispr Flow hotkeys irrelevant to Claude) - Condensed What Gets Removed/Preserved into concise Filtering Rules section ### design-patterns (59% → 85%) - Added "Use when..." clause with trigger terms (refactoring, singleton, factory, observer) - Reduced invocation examples from 9 to 4 - Removed redundant Suggestion Mode output example (~80 lines) ### cyber-defense-team (76% → 100%) - Added "Use when..." clause with natural security terms - Replaced prose descriptions with concrete Agent tool call syntax ### landing-page-generator (70% → 93%) - Added natural trigger terms (homepage, project website, marketing page) - Added Step 5: Validation Checkpoint - Removed redundant Related Use Cases section ### issue-triage (73% → 89%) - Converted `>` block scalar description to quoted string with "Use when..." clause - Condensed Jaccard algorithm pseudocode into concise paragraphs - Converted edge cases from 10-row table to 8 bullet points ### pr-triage (73% → 89%) - Converted `>` block scalar description to quoted string with "Use when..." clause - Removed unnecessary inline bash comments - Consolidated rate limiting notes ### release-notes-generator (78% → 85%) - Added natural trigger terms (release, changelog, version notes, ship) - Merged "When to Use" and "What This Skill Does" into single Workflow section ### guide-recap (93% → 100%) - Added trigger terms (release notes, announcements, social media posts) - Wrapped description in quotes </details> Honest disclosure — I work at @tesslio where we build tooling around skills like these. Not a pitch - just saw room for improvement and wanted to contribute. Want to self-improve your skills? Just point your agent (Claude Code, Codex, etc.) at [this Tessl guide](https://docs.tessl.io/evaluate/optimize-a-skill-using-best-practices) and ask it to optimize your skill. Ping me - [@popey](https://github.com/popey) - if you hit any snags. Thanks in advance 🙏
92 lines
3 KiB
Markdown
92 lines
3 KiB
Markdown
---
|
|
name: rtk-optimizer
|
|
description: "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."
|
|
version: 1.0.0
|
|
tags: [optimization, tokens, efficiency, git]
|
|
---
|
|
|
|
# RTK Optimizer Skill
|
|
|
|
Automatically suggest and apply RTK (Rust Token Killer) wrappers for verbose commands, reducing token usage by ~73% on average.
|
|
|
|
## How It Works
|
|
|
|
1. **Detect high-verbosity commands** in user requests
|
|
2. **Suggest RTK wrapper** with expected savings
|
|
3. **Execute with RTK** when user confirms
|
|
4. **Track savings** over session via `rtk gain`
|
|
|
|
## Prerequisites
|
|
|
|
```bash
|
|
rtk --version # Requires rtk 0.16.0+
|
|
|
|
# Install if needed:
|
|
brew install rtk-ai/tap/rtk # macOS/Linux
|
|
cargo install rtk # All platforms
|
|
```
|
|
|
|
## Supported Commands
|
|
|
|
| Command | RTK Equivalent | Reduction |
|
|
|---------|---------------|-----------|
|
|
| `git log` | `rtk git log` | 92% (13,994 -> 1,076 chars) |
|
|
| `git status` | `rtk git status` | 76% |
|
|
| `git diff` | `rtk git diff` | 56% (15,815 -> 6,982 chars) |
|
|
| `find` | `rtk find` | 76% |
|
|
| `cat <large-file>` | `rtk read <file>` | 63% (163K -> 61K chars) |
|
|
| `pnpm list` | `rtk pnpm list` | 82% |
|
|
| `vitest run` / `pnpm test` | `rtk vitest run` | 90% |
|
|
| `cargo test` | `rtk cargo test` | 90% |
|
|
| `cargo build` | `rtk cargo build` | 80% |
|
|
| `cargo clippy` | `rtk cargo clippy` | 80% |
|
|
| `pytest` | `rtk python pytest` | 90% |
|
|
| `go test` | `rtk go test` | 90% |
|
|
| `gh pr view` | `rtk gh pr view` | 87% |
|
|
| `gh pr checks` | `rtk gh pr checks` | 79% |
|
|
| `ls` | `rtk ls` | condensed |
|
|
| `grep` | `rtk grep` | filtered |
|
|
|
|
## Usage Pattern
|
|
|
|
```markdown
|
|
# When user requests a verbose command:
|
|
|
|
1. Acknowledge the request
|
|
2. Suggest RTK: "I'll use `rtk git log` to reduce token usage by ~92%"
|
|
3. Execute the RTK-wrapped command
|
|
4. Report savings: "Saved ~13K tokens (baseline: 14K, RTK: 1K)"
|
|
```
|
|
|
|
## Activation Examples
|
|
|
|
**User**: "Show me the git history"
|
|
**Action**: Detect `git log` -> execute `rtk git log` -> report 92% savings
|
|
|
|
**User**: "Run the test suite"
|
|
**Action**: Detect `cargo test` / `pytest` -> execute `rtk cargo test` -> report 90% savings
|
|
|
|
## When to Skip RTK
|
|
|
|
- **Small outputs** (<100 chars): Overhead not worth it
|
|
- **Claude built-in tools**: Grep/Read tools are already optimized
|
|
- **Interactive commands**: RTK is for batch/non-interactive output only
|
|
- **Multiple piped commands**: Wrap the outermost command, not each step
|
|
|
|
## Error Handling
|
|
|
|
- If `rtk` is not found, fall back to the raw command and suggest installation
|
|
- If RTK output is empty or malformed, re-run without RTK and report the issue
|
|
- If RTK version is outdated, warn about potential breaking changes (rapid release cadence)
|
|
|
|
## Session Tracking
|
|
|
|
```bash
|
|
rtk gain # Shows cumulative token savings for the session (SQLite-backed)
|
|
```
|
|
|
|
## References
|
|
|
|
- RTK GitHub: https://github.com/rtk-ai/rtk
|
|
- Evaluation: `docs/resource-evaluations/rtk-evaluation.md`
|
|
- CLAUDE.md template: `examples/claude-md/rtk-optimized.md`
|