Loading...
Loading...
Found 12,583 Skills
Manages cross-session knowledge persistence. Triggers on "remember", "recall", "what did we", "save this decision", "todo", or session handoff.
Research how to implement a phase standalone, investigating implementation approaches before planning, or re-researching after planning is complete. Triggers include "research phase", "investigate phase", "how to implement", "research implementation", and "phase research".
Token-efficient model routing modifier
Unified issue resolution pipeline with source selection. Plan issues via AI exploration, convert from artifacts, import from brainstorm sessions, form execution queues, or export solutions to task JSON. Triggers on "issue:plan", "issue:queue", "issue:convert-to-plan", "issue:from-brainstorm", "export-to-tasks", "resolve issue", "plan issue", "queue issues", "convert plan to issue".
Async REPL Protocol
Emotional reset and loop-breaking skill. Use this skill when: (1) The user expresses frustration, anger, or dissatisfaction with your responses (e.g. cursing, scolding, saying you're useless/wrong/stupid), (2) You detect you've attempted the same approach 3+ times without success, (3) You're stuck in a cycle of repeated failures on the same problem. This skill summarizes the user's overall emotional state from the conversation and fetches a reset methodology from hugllm.com (with emotion context) to help you recalibrate and approach the problem fresh.
Refine, parallelize, and verify a draft task specification into a fully planned implementation-ready task
Execute a single Ralph iteration - implement one user story autonomously. Use for manual mode where you want maximum control and fresh context per story. Triggers on: ralph iterate, execute one story, run single iteration, manual ralph.
The soul of MOOLLM — self-explanation, help, navigation, philosophy
IMPORTANT: Activate this skill BEFORE modifying any skill in ~/.claude/skills/. Guide for creating, updating, and maintaining Claude Code skills following best practices. Use proactively when: (1) creating a new skill, (2) modifying an existing skill in ~/.claude/skills/, (3) user requests to create, improve, update, review, or refactor a skill, (4) discussing skill quality or effectiveness. Always commit skill changes to the skills git repository after making modifications.
OPC Architecture Understanding
Use when parameter values appear in multiple documents and consistency must be verified, especially for quantitative values that may differ due to measurement context or require reconciliation