Loading...
Loading...
Found 13,323 Skills
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.
Delegate a coding task to Oh My Pi (`omp`) as a background implementer, then review its diff and land it yourself. Use this whenever the user wants to delegate implementation work to Oh My Pi / omp - phrasings like "have omp implement X", "delegate this to oh my pi", "run it through omp", "use oh-my-pi to implement/fix/refactor" - or wants to run a queue of coding tasks through omp while staying the reviewer. DO NOT USE for tasks small enough to do inline, when the user wants the code written directly without delegating, or when they mean the original Pi CLI (`pi`) — that is pi-delegate.
Self-evolving skills. Record user feedback, update methodologies and rules. Trigger words: update rules, record feedback, improve skill
Canonical workflow for a task. Read and follow strictly end to end while working on the task.
Applies this repository's skill-authoring standard as a procedure. Use for any change to, or judgment about, a file under skills/** — a SKILL.md, a reference, a persona prompt, a bundled script's instructions: creating a skill, editing one, reviewing a skill change, or acting on review feedback (human or bot) about one. Not for src/, tests/, or scripts/ code.
Know a company completely. Opens by asking your goal and where your context lives (CRM? call recorder? team chat? email?), then routes to 4 modes - account deep-dive & plan (external + your internal history with them), org chart (who runs it), tech stack & wedge, competitive battlecard. Use for "tell me about <company>", "account plan for <company>", "org chart for <company>", "what's their tech stack", "battlecard for <competitor>", "how do we beat <X>", "research this account".