Loading...
Loading...
Found 4,853 Skills
Search and research enhancement skills. Use when performing web searches, looking up library documentation, or conducting research that requires multiple sources.
MANDATORY before starting any task. Enforces the GPA execution loop that prevents tool call sprawl. G: GATHER phase combines discover queries + memory reads + file reads into one phase. P: Plan in text with zero tool calls. A: APPLY all writes/edits/verification in one phase. One call per tool type per phase — batch all same-type operations together. Covers dependency analysis, batch opportunities, scope estimation, and loop-back triggers.
Use when substantive documents (reviews, analyses, synthesis documents) need adversarial review to strengthen arguments, identify weak points, and challenge assumptions before editorial polish (mandatory for Writer → Devil's Advocate pairing protocol)
Use when research direction needs assessment, critical knowledge gaps must be identified, or priorities must be recommended based on impact, dependencies, and effort (especially at project milestones or when scope questions arise)
Take screenshots to see what's on screen. Triggers on 'screenshot', 'grab a screenshot', 'have a look', 'can you see', 'what does it look like', 'check the screen', 'did that work', 'verify it worked', 'what happened'. AFTER uncertain CLI operations (backgrounded processes, nohup, visual changes), consider capturing to verify state. Captures windows or full screen to files. (user)
Stops execution and fixes root cause when commands, builds, scripts, or tools fail unexpectedly. Triggers on workaround language: 'directly', 'instead', 'alternatively', 'skip', 'fall back', 'work around', 'isn't working', 'broken', 'manually'. Activates on any unexpected non-zero exit code or process failure.
Create effective skills for OpenCode agents. Load FIRST before writing any SKILL.md. Provides required format, naming conventions, progressive disclosure patterns, and validation. Use when building, reviewing, or debugging skills.
Work with GitHub in this repo: PR creation, CI checks, and gh CLI operations.
Apply systematic code refactoring with small steps, clear boundaries, and proven techniques. Use when improving existing code, reducing technical debt, cleaning up legacy code, or when user mentions refactoring, code cleanup, or code improvement.
Use when creating or developing, before writing code or implementation plans - refines rough ideas into fully-formed designs through collaborative questioning, alternative exploration, and incremental validation. Don't use during clear 'mechanical' processes
Manage Jira issues from the command line. Use when working with Jira issues, creating tasks, updating status, assigning work, or searching for issues.
Use when seeking analogous solutions from other domains, when stuck on a problem and need fresh perspectives, or when evaluating whether approaches from field X might apply to field Y. Requires structured problem statement.