Loading...
Loading...
Found 13,475 Skills
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.
Planner+Architect+Critic→consensus impl plan (≤3 rounds)
Self-evolving skills. Record user feedback, update methodologies and rules. Trigger words: update rules, record feedback, improve skill
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.
[user] 명시적인 작업 원천을 저장소 근거와 자연스러운 대화로 구체화해, 새 세션이나 더 낮은 수준 실행자가 원 대화 없이 사용할 수 있는 `.tigerkit/seed.md`를 준비합니다.
[user/auto] 하나의 pull request의 review feedback 또는 지원 가능한 GitHub Actions 실패를 fresh state로 읽고, 자연스러운 해결 계획을 합의한 뒤 필요 시 `seed.md`를 사용해 수정·검증·제한된 publication까지 처리합니다.
[user/auto] 사용자가 직접 해야 하는 `provisioning`, `credential`·`secret`, `login`/MFA/OTP/CAPTCHA/`passkey`, `dashboard`, `permission`, `device` `pairing`, `migration`/`cutover` 절차를 근거 기반의 자연스러운 대화로 안전하게 안내한다.