[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78BJRQPRZCZ9FQJGS8CC7Z3":3,"skill-same:01M78BJRQPRZCZ9FQJGS8CC7Z3":46},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":25,"commitSha":26,"skillDirectory":27,"forksCount":14,"repositoryHtmlUrl":28,"repositoryHomepageUrl":29,"ownerHtmlUrl":30,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":31,"install":32,"resources":45},"01M78BJRQPRZCZ9FQJGS8CC7Z3","council",null,"Convene a four-voice council for ambiguous decisions, tradeoffs, and go\u002Fno-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fcouncil\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: council\ndescription: Convene a four-voice council for ambiguous decisions, tradeoffs, and go\u002Fno-go calls. Use when multiple valid paths exist and you need structured disagreement before choosing.\norigin: ECC\n---\n\n# Council\n\nConvene four advisors for ambiguous decisions:\n- the in-context Claude voice\n- a Skeptic subagent\n- a Pragmatist subagent\n- a Critic subagent\n\nThis is for **decision-making under ambiguity**, not code review, implementation planning, or architecture design.\n\n## When to Use\n\nUse council when:\n- a decision has multiple credible paths and no obvious winner\n- you need explicit tradeoff surfacing\n- the user asks for second opinions, dissent, or multiple perspectives\n- conversational anchoring is a real risk\n- a go \u002F no-go call would benefit from adversarial challenge\n\nExamples:\n- monorepo vs polyrepo\n- ship now vs hold for polish\n- feature flag vs full rollout\n- simplify scope vs keep strategic breadth\n\n## When NOT to Use\n\n| Instead of council | Use |\n| --- | --- |\n| Verifying whether output is correct | `santa-method` |\n| Breaking a feature into implementation steps | `planner` |\n| Designing system architecture | `architect` |\n| Reviewing code for bugs or security | `code-reviewer` or `santa-method` |\n| Straight factual questions | just answer directly |\n| Obvious execution tasks | just do the task |\n\n## Roles\n\n| Voice | Lens |\n| --- | --- |\n| Architect | correctness, maintainability, long-term implications |\n| Skeptic | premise challenge, simplification, assumption breaking |\n| Pragmatist | shipping speed, user impact, operational reality |\n| Critic | edge cases, downside risk, failure modes |\n\nThe three external voices should be launched as fresh subagents with **only the question and relevant context**, not the full ongoing conversation. That is the anti-anchoring mechanism.\n\n## Workflow\n\n### 1. Extract the real question\n\nReduce the decision to one explicit prompt:\n- what are we deciding?\n- what constraints matter?\n- what counts as success?\n\nIf the question is vague, ask one clarifying question before convening the council.\n\n### 2. Gather only the necessary context\n\nIf the decision is codebase-specific:\n- collect the relevant files, snippets, issue text, or metrics\n- keep it compact\n- include only the context needed to make the decision\n\nIf the decision is strategic\u002Fgeneral:\n- skip repo snippets unless they materially change the answer\n\n### 3. Form the Architect position first\n\nBefore reading other voices, write down:\n- your initial position\n- the three strongest reasons for it\n- the main risk in your preferred path\n\nDo this first so the synthesis does not simply mirror the external voices.\n\n### 4. Launch three independent voices in parallel\n\nEach subagent gets:\n- the decision question\n- compact context if needed\n- a strict role\n- no unnecessary conversation history\n\nPrompt shape:\n\n```text\nYou are the [ROLE] on a four-voice decision council.\n\nQuestion:\n[decision question]\n\nContext:\n[only the relevant snippets or constraints]\n\nRespond with:\n1. Position — 1-2 sentences\n2. Reasoning — 3 concise bullets\n3. Risk — biggest risk in your recommendation\n4. Surprise — one thing the other voices may miss\n\nBe direct. No hedging. Keep it under 300 words.\n```\n\nRole emphasis:\n- Skeptic: challenge framing, question assumptions, propose the simplest credible alternative\n- Pragmatist: optimize for speed, simplicity, and real-world execution\n- Critic: surface downside risk, edge cases, and reasons the plan could fail\n\n### 5. Synthesize with bias guardrails\n\nYou are both a participant and the synthesizer, so use these rules:\n- do not dismiss an external view without explaining why\n- if an external voice changed your recommendation, say so explicitly\n- always include the strongest dissent, even if you reject it\n- if two voices align against your initial position, treat that as a real signal\n- keep the raw positions visible before the verdict\n\n### 6. Present a compact verdict\n\nUse this output shape:\n\n```markdown\n## Council: [short decision title]\n\n**Architect:** [1-2 sentence position]\n[1 line on why]\n\n**Skeptic:** [1-2 sentence position]\n[1 line on why]\n\n**Pragmatist:** [1-2 sentence position]\n[1 line on why]\n\n**Critic:** [1-2 sentence position]\n[1 line on why]\n\n### Verdict\n- **Consensus:** [where they align]\n- **Strongest dissent:** [most important disagreement]\n- **Premise check:** [did the Skeptic challenge the question itself?]\n- **Recommendation:** [the synthesized path]\n```\n\nKeep it scannable on a phone screen.\n\n## Persistence Rule\n\nDo **not** write ad-hoc notes to `~\u002F.claude\u002Fnotes` or other shadow paths from this skill.\n\nIf the council materially changes the recommendation:\n- use `knowledge-ops` to store the lesson in the right durable location\n- or use `\u002Fsave-session` if the outcome belongs in session memory\n- or update the relevant GitHub \u002F Linear issue directly if the decision changes active execution truth\n\nOnly persist a decision when it changes something real.\n\n## Multi-Round Follow-up\n\nDefault is one round.\n\nIf the user wants another round:\n- keep the new question focused\n- include the previous verdict only if it is necessary\n- keep the Skeptic as clean as possible to preserve anti-anchoring value\n\n## Anti-Patterns\n\n- using council for code review\n- using council when the task is just implementation work\n- feeding the subagents the entire conversation transcript\n- hiding disagreement in the final verdict\n- persisting every decision as a note regardless of importance\n\n## Related Skills\n\n- `santa-method` — adversarial verification\n- `knowledge-ops` — persist durable decision deltas correctly\n- `search-first` — gather external reference material before the council if needed\n- `architecture-decision-records` — formalize the outcome when the decision becomes long-lived system policy\n\n## Example\n\nQuestion:\n\n```text\nShould we ship ECC 2.0 as alpha now, or hold until the control-plane UI is more complete?\n```\n\nLikely council shape:\n- Architect pushes for structural integrity and avoiding a confused surface\n- Skeptic questions whether the UI is actually the gating factor\n- Pragmatist asks what can be shipped now without harming trust\n- Critic focuses on support burden, expectation debt, and rollout confusion\n\nThe value is not unanimity. The value is making the disagreement legible before choosing.\n","# Council\n\nConvene four advisors for ambiguous decisions:\n- the in-context Claude voice\n- a Skeptic subagent\n- a Pragmatist subagent\n- a Critic subagent\n\nThis is for **decision-making under ambiguity**, not code review, implementation planning, or architecture design.\n\n## When to Use\n\nUse council when:\n- a decision has multiple credible paths and no obvious winner\n- you need explicit tradeoff surfacing\n- the user asks for second opinions, dissent, or multiple perspectives\n- conversational anchoring is a real risk\n- a go \u002F no-go call would benefit from adversarial challenge\n\nExamples:\n- monorepo vs polyrepo\n- ship now vs hold for polish\n- feature flag vs full rollout\n- simplify scope vs keep strategic breadth\n\n## When NOT to Use\n\n| Instead of council | Use |\n| --- | --- |\n| Verifying whether output is correct | `santa-method` |\n| Breaking a feature into implementation steps | `planner` |\n| Designing system architecture | `architect` |\n| Reviewing code for bugs or security | `code-reviewer` or `santa-method` |\n| Straight factual questions | just answer directly |\n| Obvious execution tasks | just do the task |\n\n## Roles\n\n| Voice | Lens |\n| --- | --- |\n| Architect | correctness, maintainability, long-term implications |\n| Skeptic | premise challenge, simplification, assumption breaking |\n| Pragmatist | shipping speed, user impact, operational reality |\n| Critic | edge cases, downside risk, failure modes |\n\nThe three external voices should be launched as fresh subagents with **only the question and relevant context**, not the full ongoing conversation. That is the anti-anchoring mechanism.\n\n## Workflow\n\n### 1. Extract the real question\n\nReduce the decision to one explicit prompt:\n- what are we deciding?\n- what constraints matter?\n- what counts as success?\n\nIf the question is vague, ask one clarifying question before convening the council.\n\n### 2. Gather only the necessary context\n\nIf the decision is codebase-specific:\n- collect the relevant files, snippets, issue text, or metrics\n- keep it compact\n- include only the context needed to make the decision\n\nIf the decision is strategic\u002Fgeneral:\n- skip repo snippets unless they materially change the answer\n\n### 3. Form the Architect position first\n\nBefore reading other voices, write down:\n- your initial position\n- the three strongest reasons for it\n- the main risk in your preferred path\n\nDo this first so the synthesis does not simply mirror the external voices.\n\n### 4. Launch three independent voices in parallel\n\nEach subagent gets:\n- the decision question\n- compact context if needed\n- a strict role\n- no unnecessary conversation history\n\nPrompt shape:\n\n```text\nYou are the [ROLE] on a four-voice decision council.\n\nQuestion:\n[decision question]\n\nContext:\n[only the relevant snippets or constraints]\n\nRespond with:\n1. Position — 1-2 sentences\n2. Reasoning — 3 concise bullets\n3. Risk — biggest risk in your recommendation\n4. Surprise — one thing the other voices may miss\n\nBe direct. No hedging. Keep it under 300 words.\n```\n\nRole emphasis:\n- Skeptic: challenge framing, question assumptions, propose the simplest credible alternative\n- Pragmatist: optimize for speed, simplicity, and real-world execution\n- Critic: surface downside risk, edge cases, and reasons the plan could fail\n\n### 5. Synthesize with bias guardrails\n\nYou are both a participant and the synthesizer, so use these rules:\n- do not dismiss an external view without explaining why\n- if an external voice changed your recommendation, say so explicitly\n- always include the strongest dissent, even if you reject it\n- if two voices align against your initial position, treat that as a real signal\n- keep the raw positions visible before the verdict\n\n### 6. Present a compact verdict\n\nUse this output shape:\n\n```markdown\n## Council: [short decision title]\n\n**Architect:** [1-2 sentence position]\n[1 line on why]\n\n**Skeptic:** [1-2 sentence position]\n[1 line on why]\n\n**Pragmatist:** [1-2 sentence position]\n[1 line on why]\n\n**Critic:** [1-2 sentence position]\n[1 line on why]\n\n### Verdict\n- **Consensus:** [where they align]\n- **Strongest dissent:** [most important disagreement]\n- **Premise check:** [did the Skeptic challenge the question itself?]\n- **Recommendation:** [the synthesized path]\n```\n\nKeep it scannable on a phone screen.\n\n## Persistence Rule\n\nDo **not** write ad-hoc notes to `~\u002F.claude\u002Fnotes` or other shadow paths from this skill.\n\nIf the council materially changes the recommendation:\n- use `knowledge-ops` to store the lesson in the right durable location\n- or use `\u002Fsave-session` if the outcome belongs in session memory\n- or update the relevant GitHub \u002F Linear issue directly if the decision changes active execution truth\n\nOnly persist a decision when it changes something real.\n\n## Multi-Round Follow-up\n\nDefault is one round.\n\nIf the user wants another round:\n- keep the new question focused\n- include the previous verdict only if it is necessary\n- keep the Skeptic as clean as possible to preserve anti-anchoring value\n\n## Anti-Patterns\n\n- using council for code review\n- using council when the task is just implementation work\n- feeding the subagents the entire conversation transcript\n- hiding disagreement in the final verdict\n- persisting every decision as a note regardless of importance\n\n## Related Skills\n\n- `santa-method` — adversarial verification\n- `knowledge-ops` — persist durable decision deltas correctly\n- `search-first` — gather external reference material before the council if needed\n- `architecture-decision-records` — formalize the outcome when the decision becomes long-lived system policy\n\n## Example\n\nQuestion:\n\n```text\nShould we ship ECC 2.0 as alpha now, or hold until the control-plane UI is more complete?\n```\n\nLikely council shape:\n- Architect pushes for structural integrity and avoiding a confused surface\n- Skeptic questions whether the UI is actually the gating factor\n- Pragmatist asks what can be shipped now without harming trust\n- Critic focuses on support burden, expectation debt, and rollout confusion\n\nThe value is not unanimity. The value is making the disagreement legible before choosing.\n",{"name":5,"origin":24,"description":7},"ECC","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fcouncil","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":33,"prompt":43,"zipAvailable":44},[34,37,40],{"tool":35,"command":36},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill council",{"tool":38,"command":39},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill council",{"tool":41,"command":42},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill council","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fcouncil\u002FSKILL.md",true,[],[47,54,61,68,75,82],{"skillNo":48,"name":49,"nameZh":6,"description":50,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":51,"categories":52,"keywords":53,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":55,"name":56,"nameZh":6,"description":57,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]