rtk
RTK (Rust Token Killer) - Token-Optimized Commands
Golden Rule
Always prefix commands with rtk. If RTK has a dedicated filter, it uses it. If not, it passes through unchanged. This means RTK is always safe to use. RTK is also cross-platform, so it works in Windows and with cmd/pwsh.
Important: Even in command chains with &&, use rtk:
# ❌ Wrong
git add . && git commit -m "msg" && git push
# ✅ Correct
rtk git add . && rtk git commit -m "msg" && rtk git push
Examples
rtk git status
rtk cargo test
rtk npm run build
rtk pytest -q
More from edm115/skills
pyrofork-docs
Use when working with Pyrofork (Pyrogram fork) in any Python project - setup/auth, client lifecycle, handlers/filters, async vs sync usage, plugins, raw MTProto API, formatting, storage/proxy/scheduling, Telegram-specific behavior, and troubleshooting common RPC/session/network errors.
14pyrofork-api
Use when implementing, debugging, or reviewing Pyrofork API usage and internals from docs/source/api, including Client, handlers, decorators, filters, enums, and RPC error catalogs. Triggers on requests for exact signatures, parameters, types, enum values, filter behavior, or handler/decorator wiring.
4pyrofork-best-practices
Use when building Telegram automations with Pyrofork and needing practical patterns for handlers, filters, plugins, raw API usage, and reliability.
4pyrofork-api-full-reference
Offline API backup skill for Pyrofork, extracted from source docstrings across pyrogram modules. Warning - the content is massive and should be queried with tools like `rg`/`grep` for specific references rather than read sequentially. Only load sections relevant to your needs.
3