Loading...
Loading...
Found 91 Skills
Automatically detects story settings (genres, time periods, themes) based on keywords and activates corresponding knowledge bases - works silently in the background to provide relevant writing guidance without user intervention
Use when context window is filling up too fast or input token cost is too high. Audits overhead sources.
Token/quota throttling rules for multi-agent orchestration. Before any Agent tool call or Workflow dispatch—regardless of whether the user mentioned saving tokens, even a single subagent counts—read this skill first before acting. Also triggered when the user says "save tokens", "quota", "don't burn my limit". Trigger words: workflow, multi-agent, fan-out, subagent, dispatch, orchestration, save tokens, quota, token optimizer. English triggers: "save tokens", "quota", "don't burn my limit", "token optimizer".
Install, initialize, verify, and troubleshoot RTK (Rust Token Killer) for AI coding agents. Use when you need to reduce shell-command token output, confirm that the correct `rtk` binary is installed, choose between Homebrew, install.sh, or Cargo installation, wire `rtk init` for Claude Code, Codex, Gemini CLI, Cursor, Copilot, Windsurf, Cline, or OpenCode, or use compact wrappers such as `rtk git status`, `rtk read`, `rtk grep`, `rtk test`, `rtk lint`, and `rtk gain`. Triggers on: rtk, rust token killer, token saver cli, rtk init, rtk gain, codex rtk, gemini rtk, opencode rtk, claude hook token reduction.
Classify problems and route to optimal thinking MCP (11 available). Monitor confidence, re-route on stall. Use for complex reasoning. NOT for simple questions (answer directly) or code review (review).
Track session costs, set budget alerts, and optimize token spend. Use to check costs mid-session or set spending limits.
Browser automation workflows with Playwright MCP integration
Token-optimized CLI proxy: wrap noisy commands (test runs, builds, git, grep, gh, logs, directory walks) so a filtered summary reaches context instead of a raw dump. Use before running any command whose output is large or repetitive, and to decide when filtering would hide the line you actually need.
Show context usage heatmap for current session
Reduce avoidable Codex token and context usage in long-running or repository-scale work by minimizing repeated reads, inefficient polling, context drift, and unnecessary high-capability model use. Apply when users ask to save Codex quota, streamline a long task, or make an agent workflow more context-efficient; do not apply to ordinary short tasks that need no optimization.
Apply when context is filling up: large outputs, long files, repeated reads, fan-out planning. Route bulk to subagents; keep summaries in the main thread, not raw payloads.
Orchestrate bounded Codex, Claude Code, Agy, Kimi, or custom CLI workers to finish work with the least lead context and provider usage, following playbooks such as plan big, execute small. Use when the user asks to orchestrate, delegate, compare agents, conserve agent tokens or quota, recover a worker, report what an orchestration did and cost, or work without MCP or Python, when the user types /alethe or a short command such as "alethe report" or "alethe stop", and when they want it on from now on, at any point of a task and alongside other skills. Also use it proactively, without being asked, when a request is large enough to split into bounded independent units, such as a multi-file refactor, a migration, an audit or research across many files. Do not use for a small mechanical task unless explicitly requested.