Loading...
Loading...
Found 13,352 Skills
Use when starting any conversation - establishes how to find and use skills, requiring Skill tool invocation before ANY response including clarifying questions
Create New Skill - scaffolds a skill definition following Claude Code conventions and this repository's patterns. Use when adding a new skill.
The always-on protocol for the loam skill namespace. Use at session start and whenever a loam task appears. Routes goals and other loam work, explains the memory model (memory = umbrella; wiki, guidance, and checkpoints are substrates), and lists cross-cutting rules. This is a routing/meta skill — delegate to a specific loam skill rather than performing work itself.
Retired — /ultracook no longer exists as a standalone skill. Any /ultracook invocation resolves to /cook, which now owns the single implementation pathway (including the fan-out mechanics this skill used to run). Use /cook instead.
Use only when user explicitly invokes $loop.
Ask me questions within this workspace regarding the workflow requirements I want to build.
Grill the user's plans, decisions, or ideas layer by layer. Use this when the user wants to stress-test their thinking or uses any 'grill' trigger phrase.
AI Berkshire Skill: Earnings Report In-depth Analysis Team: Parallel Interpretation by Four Masters + Official Account Publishing. Source: skills/earnings-team.md.
Convene a structured LLM Council — five thinking-lens advisors (Red Team, First Principles, Expansionist, Outsider, Executor) plus anonymised peer review, forced debate on consensus, dual-chairman synthesis with dissent preservation, and optional Codex-powered Decision Science pass — to pressure-test high-stakes decisions. Adaptive modes (Quick/Standard/Deep) keep cost bounded; a persistent journal enables learning across runs. Mandatory triggers: /claude-council, "convene the council", "run this by the council", "I need the council", "council this", "pressure-test this", "stress-test this", "war room this", "debate this". Strong triggers: "I'm torn between X and Y", "this is a big decision", "help me think this through from multiple angles", "I need outside perspectives", "should I X or Y" (with real stakes — if binary with obvious answer, triage rejects per Step 1 rule 4). Do NOT invoke for factual questions, coding help, debugging, quick yes/no decisions, emotional support, or questions with one right answer — answer those directly. Optional suffixes: "with codex" enables Decision Science pass; "deep" forces Deep mode; "quick" forces Quick mode. Secondary invocation: /claude-council outcome <sha1> <note> records decision outcome. /claude-council meta runs journal meta-analysis.
When to use — build, extend, or debug a DeepSeek Harness (dsh) plugin — plugin naming/scope rules, the host/client entry split, cordis services, client slots/settings/locale, the apiproxy RPC, profiles and presets, self-contained bundle packaging/loading, the develop→load→reload loop, or proposing a change to dsh itself.
Review source files changed during a phase for bugs, security issues, and code quality problems
Analyze the user's manual rewrite or repeated correction of Codex-generated work and propose durable, carefully scoped lessons. Use when the user asks to improve future behavior from their corrections. Do not use for ordinary task requirements or one-off implementation feedback without a request for lasting guidance.