name: rtk
description: Use rust-token-killer (rtk) as the default shell-output optimization layer for noisy command-line workflows.
RTK Skill
Use rust-token-killer (rtk) as the default shell-output optimization layer for noisy command-line workflows.
Repository:
Purpose
RTK reduces token-heavy command output before it reaches the agent.
Use it by default for:
- git inspection
- file reads and code search
- tests
- linting
- typechecking
- builds
- dependency and package inspection
- logs and other high-volume command output
Default Policy
- If
rtkis installed, prefer it for relevant shell commands. - If the global hook is installed, let it transparently rewrite Bash commands.
- If the hook does not apply, call
rtkexplicitly. - If
rtkis unavailable, fall back to the normal command instead of blocking the task.
Recommended Setup
rtk init -g- restart the agent session after hook installation
Scope Rule
- RTK auto-rewrite applies to Bash tool calls.
- Built-in read/search/glob-style tools do not pass through the hook.
- When using shell access for those workflows, prefer explicit RTK commands.
Examples:
rtk read <file>rtk grep <pattern>rtk find <glob> <path>rtk ls
Common Command Mapping
- git:
rtk git status,rtk git diff,rtk git log - GitHub CLI:
rtk gh pr view,rtk gh issue list - file reads/search:
rtk read,rtk grep,rtk find,rtk ls - tests:
rtk vitest run,rtk test npm test,rtk playwright test - TypeScript:
rtk tsc - lint/format:
rtk lint,rtk prettier --check . - Next.js:
rtk next build - Prisma:
rtk prisma ... - network/log-heavy commands:
rtk curl,rtk docker ...,rtk kubectl ...
Debugging Rule
- Prefer the RTK-wrapped form whenever raw output would be noisy.
- If RTK output hides detail needed for debugging, inspect saved full output if available or rerun the narrowest raw command needed.
Validation Preference
When validating work, prefer RTK-wrapped versions of noisy commands when available:
rtk lintrtk tscrtk test npm testrtk next build