Loading...
Loading...
Found 6,632 Skills
One-shot question answering using the research process. Answers inline without generating documents, then offers handoff to brainstorm or research.
Design and evaluate compression strategies for long-running sessions
Research codebase comprehensively using parallel sub-agents to answer user questions. Use when the user asks to "research the codebase", "understand how X works", or "investigate Y".
View investment accounts, check portfolio performance, monitor 401k, and research funds on Fidelity
Remote-control tmux sessions for interactive CLIs by sending keystrokes and scraping pane output.
People research using Exa search. Finds LinkedIn profiles, professional backgrounds, experts, team members, and public bios across the web. Use when searching for people, finding experts, or looking up professional profiles.
This skill should be used when the user asks to refactor specific files or directories, simplify recently changed code, clean up dead code in a limited scope, or invokes `/refactor` with paths or semantic queries.
Based on the Recursive Language Models (RLM) research by Zhang, Kraska, and Khattab (2025), this skill provides strategies for handling tasks that exceed comfortable context limits through programmatic decomposition and recursive self-invocation. Triggers on phrases like "analyze all files", "process this large document", "aggregate information from", "search across the codebase", or tasks involving 10+ files or 50k+ tokens.
Agent skill for performance-optimizer - invoke with $agent-performance-optimizer
Before starting any significant task, force explicit evaluation of available skills. For each potentially relevant skill, state YES/NO with reasoning. Only proceed to implementation after skills have been consciously evaluated and activated. Prevents the ~50% "coin flip" activation rate that occurs when skills are passively available but not deliberately considered.
Conduct context-driven code reviews focusing on quality, testability, and maintainability. Use when reviewing code, providing feedback, or establishing review practices.
Synthesizes research findings into design decisions via codebase investigation. Use when (1) translating research into implementation approaches, (2) selecting between design alternatives, (3) executing after /research or deep-research, or (4) preparing input for /plan phase.