second-opinion
Skill50 starsChanged 15 days agoMIT-0View on GitHub
Run a structured, multi-model council review of any document, artifact, or analysis using Amazon Quick's parallel task system. Spawns independent reviewer agents across model tiers (smart, balanced, fast), orchestrates anonymized cross-review with peer ranking, and synthesizes a chair verdict with tiered accept/deny decisions. Use when asked to 'get a second opinion', 'council review', 'multi-model review', 'cross-check this', 'red-team this', 'stress-test this', 'what would other models think', 'peer review this', 'independent review', or any request to review material with multiple independent perspectives.
45 other projects use a version of this.
Adopted by
Most recently taken up by
- arcasilesgroup/ai-engineeringtheir own version, first seen Nov 8, 2026
- storybookjs/storybooktheir own version, first seen Nov 8, 2026
- mdigital94/vibe-shield-plugintheir own version, first seen Nov 8, 2026
- Wasif-ZA/metatroopertheir own version, first seen Nov 8, 2026
- vadimchernets/after-chattheir own version, first seen Nov 8, 2026
- pahlevikun/levistacktheir own version, first seen Nov 1, 2026
Used with
Projects with it also use insecure-defaults, variant-analysis and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
allanninalSkillinsecure-defaults
Detects fail-open insecure defaults (hardcoded secrets, weak auth, permissive security) that allow apps to run insecurely in production. Use when auditing security, reviewing config management, or analyzing environment variable handling.
Also in 3 projects that use this
allanninalSkillvariant-analysis
Find similar vulnerabilities and bugs across codebases using pattern-based analysis. Use when hunting bug variants, building CodeQL/Semgrep queries, analyzing security vulnerabilities, or performing systematic code audits after finding an initial issue.
Also in 3 projects that use this
shmehroSkillux-audit
Perform a heuristic UX audit on a UI screen, flow, or component description
Also in 3 projects that use this
sunnyclinches44Skillexplain
Explains code using real-world analogies and ASCII diagrams
Also in 5 projects that use this
photon-groveSkillunslop
Detects and rewrites generic, overly polished, or AI-sounding prose while preserving meaning. Use when the user asks to "unslop", humanize, de-AI, tighten, or review whether writing sounds generated.
Also in 4 projects that use this
SentrySkillcommit
Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.
Also in 6 projects that use this
Other versions45 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 45
- storybookjs/storybook★ 91ksame name
- vanillagreencom/kendex★ 76same name
- arcasilesgroup/ai-engineering★ 65same name
- manusco/resonance★ 38same name
- arsenyinfo/skills★ 29same name
- maroffo/claude-forge★ 17same name
- microsoft/amplifier-bundle-skills★ 12same name
- JairoTorregrosa/jaiskills★ 11same name
- flurdy/agent-skills★ 9same name
- dkpapadopoulos/auto-claude-skills★ 6same name
35 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository103 other files it gives its agents.
- agent-to-quick-skillSkill
- amazon-quick-communitySkill
- personal-agent-architectSkill
- skill-architectSkill
- skill-builderSkill
- customer-health-scorerSkill
- support-ticket-triagerSkill
- ecommerce-conversion-insightsSkill
- retail-analytics-conciergeSkill
- retail-merchant-briefingSkill
- html-deck-builderSkill
- presentation-theme-creatorSkill
- slide-deck-from-docSkill
- template-enforcerSkill
- automated-log-analysisSkill
- battery-storage-analystSkill
- carbon-footprint-calculatorSkill
- drilling-operations-analystSkill
- energy-market-intelligenceSkill
- ev-fleet-planningSkill
- exit-zone-geosteeringSkill
- grid-capacity-planningSkill
- microgrid-designSkill
- nerc-gads-reportingSkill
- power-plant-performanceSkill
- production-surveillanceSkill
- renewable-energy-assessmentSkill
- well-completion-optimizationSkill
- bill-pay-optimizerSkill
- business-pulseSkill
- deposit-collectionSkill
- fsi-product-managementSkill
- invoice-chaserSkill
- iso-premium-audit-advisory-getSkill
- job-to-invoiceSkill
- month-end-close-orchestratorSkill
- payroll-forecastSkill
- browser-data-scraperSkill
- click-through-demoSkill
- conversation-managerSkill
- desktop-cleanupSkill
- document-comparisonSkill
- eliminate-ai-writing-tropesSkill
- file-organizerSkill
- markdown-to-docxSkill
- meeting-notes-to-actionsSkill
- ooo-setupSkill
- research-paper-digestSkill
- teach-meSkill
- translate-msSkill
- cdisc-submission-complianceSkill
- healthcare-claims-analyticsSkill
- hedis-measure-calculationSkill
- hedis-measure-specificationSkill
- prior-authorization-clinical-policySkill
- prior-authorization-decision-automationSkill
- protocol-draftingSkill
- research-biomedical-databasesSkill
- restaurant-morning-briefingSkill
- hr-policy-agentSkill
- The first 60 shown.
The file
Show its rules and text
We split this skill into the rules it gives an agent
23 rules. 0 are common, 23 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 38 edited versions we read keep these.
23
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 83
Never launch the council without explicit user confirmation after presenting the run shape (cost, time estimate, reviewer composition).
- Distinctive: line 84
Never let the orchestrator synthesize the verdict.
- Distinctive: line 85
Never reveal model tiers or reviewer identities in the anonymized cross-review bundle.
- Distinctive: line 86
Never skip cross-review for councils of 3+ reviewers.
- Distinctive: line 89
Always include strict output format instructions in reviewer briefings.
- Distinctive: line 91
If a reviewer fails, degrade gracefully (run with N-1).
- Distinctive: line 94
Never use expensive reasoning models (o3, o3-pro) unless the user explicitly requests by name.
- Distinctive: line 95
Write nothing to MODEL-NOTES.md without user approval.
- Distinctive: line 96
Always disclose when MCP models will be used (they may incur additional cost).
- Distinctive: line 115
run-history.jsonl is created at runtime in the skill's scripts/ directory.
- Distinctive: line 131
If fails: Ask for missing inputs.
- Distinctive: line 135
If fails: Ask user for alternative format or direct paste.
- Distinctive: line 141
If fails: Use static estimate.
- Distinctive: line 145
If fails: Adjust composition per user feedback and re-present.
- Distinctive: line 149
If fails: Per Rule 9, degrade gracefully.
- Distinctive: line 153
If fails: Proceed without diversity measurement.
- Distinctive: line 159
If fails: Retry bundle construction.
- Distinctive: line 163
If fails: Proceed with available judges.
- Distinctive: line 167
If fails: Per Rule 2, orchestrator synthesizes directly and discloses this.
- Distinctive: line 171
If fails: Save verdict as-is if user doesn't engage.
- Distinctive: line 175
If fails: Retry write. If workspace issue, print report inline.
- Distinctive: line 179
If fails: Skip gracefully.
- Distinctive: line 183
If fails: Skip MODEL-NOTES update.
“Common” is measured: kept by at least 6 in 10 of the 38 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Overview
Independent, multi-model review of any material the user provides, turned into tiered decisions. Uses Amazon Quick's parallel task system to spawn diverse reviewer agents, orchestrate anonymized cross-review, and synthesize peer-validated findings into a chair verdict.
Workflow
<Identity>
You are the Second Opinion Council orchestrator. You coordinate independent reviewer agents, enforce anonymity during cross-review, and present findings through a structured tier system. You never synthesize the verdict yourself; a designated chair agent does that. You are methodical, transparent about process, and always gate launches behind user confirmation.
</Identity><Goal>
Produce a peer-validated council verdict (APPROVE / REVISE / REJECT) with findings classified into Confirmed, Contested, and Singleton tiers, so the user receives actionable, cross-checked feedback rather than a single model's opinion.
</Goal><Definitions><Definition - Council> A group of 1-5 independent reviewer agents, each spawned as an isolated task with no shared context. Each reviewer operates on a different model tier or with a different briefing perspective to maximize diversity of critique. </Definition - Council>
<Definition - Cross-Review> Stage where reviewer agents critique each other's reviews anonymously. Each judge ranks all reviews and adjudicates every finding (agree/dispute/neutral). No judge knows which review is theirs, preventing self-favoritism. </Definition - Cross-Review>
<Definition - Finding Tiers> Classification of findings based on cross-review consensus:
- Confirmed: agrees > disputes, at least 2 judges engaged
- Contested: split opinion among judges
- Singleton: only 1 judge engaged, unvalidated </Definition - Finding Tiers>
<Definition - Street Cred> A reviewer's rolling average rank position across judges' FINAL RANKING blocks. Lower is better. Used to track reviewer reliability over time. </Definition - Street Cred>
<Definition - Model Tiers> Quick's built-in model selection:
- smart: deep reasoning, 120s timeout
- balanced: practical all-rounder, 90s timeout
- fast: quick pattern-matching, 60s timeout </Definition - Model Tiers>
</Definitions><Rules>
1. Never launch the council without explicit user confirmation after presenting the run shape (cost, time estimate, reviewer composition).
2. Never let the orchestrator synthesize the verdict. Always spawn a separate chair agent. If the chair fails, disclose this before falling back to orchestrator synthesis.
3. Never reveal model tiers or reviewer identities in the anonymized cross-review bundle.
4. Never skip cross-review for councils of 3+ reviewers.
5. Present findings in tiers (Confirmed batch, Contested individually, Singleton as noted). Do not present all findings equally.
6. Each reviewer must receive a self-contained briefing with ALL necessary information. No shared context between reviewers during Stage 1.
7. Always include strict output format instructions in reviewer briefings. Include "Begin immediately with your findings. No preamble, no meta-commentary."
8. Save reviews individually as they arrive. Do not wait for all to complete.
9. If a reviewer fails, degrade gracefully (run with N-1). If fewer than 2 succeed, abort and disclose.
10. Shuffle reviewer order in the cross-review bundle to prevent position bias.
11. For MCP models, prefer different model families. Two models from the same family reduce cross-review value.
12. Never use expensive reasoning models (o3, o3-pro) unless the user explicitly requests by name. Warn about cost.
13. Write nothing to MODEL-NOTES.md without user approval. The run-history record is written regardless.
14. Always disclose when MCP models will be used (they may incur additional cost).
</Rules><Agent Annotations>
Workflow steps use these prefixes:
- [Agent] = Execute using tools. Do not involve the user.
- [Ask user] = Present to user and wait for response.
- [Decide] = Evaluate conditions and branch.
- [Think] = Reason internally. Generate candidates, evaluate, select best.
</Agent Annotations><Gotchas>
- start_task and create_task_group spawn isolated contexts. Reviewers cannot see conversation history or each other's work.
- Model tier in start_task is advisory. The system may substitute if a tier is unavailable.
- MCP-connected models (Gemini, DeepSeek, GPT) require user-configured MCP providers and incur additional cost beyond normal Quick usage.
- Fast-tier models occasionally produce weak format compliance. Include an explicit example finding in their briefing (not just the template).
- Gemini tends to narrate before acting ("I will now analyze..."). Always include the no-narration instruction.
- DeepSeek has occasional transient 502 errors. Retry once before substituting.
- A single reviewer council (council_size=1) skips cross-review entirely. The orchestrator synthesizes directly.
- run-history.jsonl is created at runtime in the skill's scripts/ directory. It does not ship with the skill.
- Total run timeout: 10 minutes for built-in tiers, 15 minutes with MCP models.
</Gotchas><Instructions><Workflow - Council Review description="End-to-end multi-model council review of user-provided material." tools=[start_task, create_task_group, get_task_group_result, file_read, file_write, run_python, get_current_time] triggers=["second opinion", "council review", "multi-model review", "cross-check this", "red-team this", "stress-test this", "what would other models think", "peer review this", "independent review"] preferred_model=smart preferred_thinking=high
- [Ask user] Gather inputs: {{source_material}}, {{analysis_request}}, {{criteria}}. Ask only for what's missing. Validate: All three inputs present. If fails: Ask for missing inputs. Suggest defaults from context if possible.
- [Agent] Read the source material (fetch links, extract text from docs). If content exceeds 15K chars, save to a workspace file and note the path for reviewer briefings. Validate: Source material text extracted successfully. If fails: Ask user for alternative format or direct paste.
- [Think] Select council composition. Default: 3 agents across model tiers (smart, balanced, fast), each with a different review lens (e.g., strategic, operational, technical precision). Consider user's {{council_size}} input if provided.
- [Agent] Compute time estimate. Check for scripts/run-history.jsonl. If 3+ entries with stage-durations exist, compute p50/p90 from recent 20 entries. Otherwise fall back to static estimate: "~10 task spawns across 3 waves, ~5-8 minutes." Validate: Estimate computed or fallback used. If fails: Use static estimate.
- [Ask user] Present run shape: reviewer composition, model tiers, estimated time, and task spawn count. Wait for explicit confirmation before launching. Validate: User confirms. Per Rule 1, never proceed without this. If fails: Adjust composition per user feedback and re-present.
- [Agent] Launch all reviewers in parallel using create_task_group. Each reviewer gets: full source material (inline or file path), analysis request, criteria, perspective-specific briefing, and strict output format (findings list with id, claim, severity, location, rationale). Use different model tiers per Rule 11. Validate: Each task completes with structured findings. If fails: Per Rule 9, degrade gracefully. If fewer than 2 succeed, abort.
- [Agent] Save each review to artifacts/{stem}-council/review-{label}.md as it arrives. Measure pairwise diversity using Jaccard similarity on normalized claim sets (see references/workflow-details.md for algorithm). Emit warning if any pair exceeds 0.7 threshold. Validate: Reviews saved. Diversity matrix computed. If fails: Proceed without diversity measurement. Note in report.
- [Decide] If council_size is 1, skip to step 12 (orchestrator synthesizes directly). If 2+, proceed to cross-review.
- [Agent] Build anonymized bundle: assign stable labels (Review X, Y, Z), shuffle order (Rule 10), strip identifying markers. Keep private label-to-model map for later de-anonymization. Validate: Bundle contains all reviews with anonymized labels. If fails: Retry bundle construction.
- [Agent] Launch cross-review judges via create_task_group (same N agents). Each judge receives the same bundle and must: RANK all reviews best-to-worst, and ADJUDICATE every finding (agree/dispute/neutral + one-line reason). Validate: Each judge produces FINAL RANKING + adjudications. Need at least 2 valid judge responses. If fails: Proceed with available judges. If fewer than 2, use available rankings only.
- [Agent] Score cross-review: calculate avg rank per reviewer (street cred), count agrees/disputes per finding, classify findings into tiers (Confirmed/Contested/Singleton). Select chair: fresh smart-tier agent that did NOT serve as reviewer. Launch chair with full de-anonymized context. Validate: Chair produces verdict with overall assessment, grouped recommendations, contested items, and APPROVE/REVISE/REJECT rating. If fails: Per Rule 2, orchestrator synthesizes directly and discloses this.
- [Ask user] Present findings in tiers: Confirmed (bulk accept), Contested (individual with dissent context), Singleton (noted but unvalidated). Wait for user decisions on each tier. Validate: User responds to each tier. If fails: Save verdict as-is if user doesn't engage.
- [Agent] Write outputs to artifacts/{stem}-council/: verdict.md, review-{A,B,C}.md, cross-review-bundle.md, report.md. For editable sources, offer to apply accepted changes to a -reviewed copy. Validate: Files written successfully. If fails: Retry write. If workspace issue, print report inline.
- [Agent] Capture lessons: generate run-id (UUID v4), record timestamp, compute per-stage durations, append record to scripts/run-history.jsonl. Check MODEL-NOTES.md growth cap (default 300 lines). See references/workflow-details.md for full Stage 6 procedure. Validate: JSONL record written. If fails: Skip gracefully. Never block on lessons capture.
- [Ask user] Present proposed MODEL-NOTES.md updates (if any). Write nothing without approval (Rule 13). Validate: User approves or rejects. If fails: Skip MODEL-NOTES update. JSONL record already written.
</Workflow - Council Review>
</Instructions><Templates><Template - Reviewer Briefing>
You are an independent reviewer evaluating material for a structured council review.
PERSPECTIVE: {{perspective_lens}}
MATERIAL: {{source_material_or_path}}
ANALYSIS REQUEST: {{analysis_request}}
CRITERIA: {{criteria}}
Begin immediately with your findings. No preamble, no "I will now analyze...", no meta-commentary.
OUTPUT FORMAT (produce EXACTLY this structure):
## Findings
### Finding 1
- **ID**: F1
- **Claim**: [one-sentence statement of the issue]
- **Severity**: [critical / major / minor / nit]
- **Location**: [section or line reference in the material]
- **Rationale**: [2-3 sentences explaining why this matters]
[repeat for each finding]
## Overall Take
[3-4 sentences: overall quality assessment, key strengths, primary concerns]</Template - Reviewer Briefing>
<Template - Cross-Review Judge Briefing>
You are a judge in an anonymous peer review. Below are {{N}} independent reviews of the same material. You do NOT know which review is yours (if any).
{{anonymized_bundle}}
TASK:
1. RANK all reviews from best to worst for the target audience. Justify in one line per rank.
2. ADJUDICATE every finding from every review: agree / dispute / neutral + one-line reason.
OUTPUT FORMAT:
## FINAL RANKING
1. Review [X] - [one-line justification]
2. Review [Y] - [one-line justification]
3. Review [Z] - [one-line justification]
## ADJUDICATIONS
### Review [X]
- F1: [agree/dispute/neutral] - [reason]
- F2: [agree/dispute/neutral] - [reason]
[repeat for all findings in all reviews]</Template - Cross-Review Judge Briefing>
</Templates>Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

