verdict
Skill9 starsChanged 17 days agoMITView on GitHub
Architect-grade technology decision briefs — "which option should we pick, and why?" Takes a decision question (X vs Y vs Z for a stated context: library, database, framework, platform, buy-vs-build) plus your constraints, fans out parallel sub-agents to research each option's project health, community sentiment, technical claims, and operational story, then scores options across weighted criteria and emits an ADR-style recommendation with a full scorecard and cited evidence. Keyless; the recommendation is advisory — you decide. Use when the user must choose between technologies or approaches — e.g. "/verdict postgres vs mongodb for <use case>", "should we use Kafka or NATS", "compare X and Y", "buy vs build", "which framework for this". Also supports "/verdict revisit <brief>" to cheaply re-check a past verdict's revisit-when triggers. For community buzz on a single topic use pulse; for exhaustive fact-checked research use deep-research.
10 other projects use a version of this.
Adopted by
Most recently taken up by
- ronniepinnell/caspertheir own version, first seen Nov 8, 2026
- rhasselle-oddball/claude-skillstheir own version, first seen Nov 1, 2026
- udecode/platetheir own version, first seen Oct 17, 2026
- alexjmiller5/agent-config-publictheir own version, first seen Oct 15, 2026
- jacobgreenwald21/claude-skillstheir own version, first seen Oct 15, 2026
- arbelh/perduretheir own version, first seen Oct 11, 2026
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- udecode/plate★ 17ksame name
- SanketSapkal/founder-skills★ 10same name
- damionrashford/Adversaria★ 9same name
- ronniepinnell/casper★ 1same name
- alexjmiller5/agent-config-public★ 0same name
- andrewcovenant/skills★ 0same name
- arbelh/perdure★ 0same name
- jacobgreenwald21/claude-skills★ 0same name
- OpentypeAI/opentype-claude-plugin★ 0same name
- rhasselle-oddball/claude-skills★ 0same name
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 repository21 other files it gives its agents.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 6 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 77
If an angle returns nothing usable, record it as unknown — never fabricate.
- Distinctive: line 97
If a criterion doesn't apply, mark it N/A and renormalize the rest — say so.
- Very specific: line 117
Read the previous brief (find it in out/verdicts/ by slug if only a topic is given).
- Distinctive: line 157
Never present a close call as decisive.
- Distinctive: line 158
Symmetric research: Every option gets the same five angles — no strawmanning the option you suspect will lose.
- Distinctive: line 162
No fabrication: Every score traces to cited findings.
- Distinctive: line 164
Keyless: Never ask for API keys; degrade gracefully.
“Common” is measured: kept by at least 6 in 10 of the 9 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
verdict — technology decision briefs
/verdict <option A> vs <option B> [vs <option C>] for <context> [constraints]
/verdict revisit <path-to-previous-brief> — re-check an old verdict (see Revisit mode)
Answer one question: given this context, which option should we pick, and what evidence supports that? You research every option the same way, score against explicit weighted criteria, and write the decision up so it can be defended in a design review — or revisited later when the facts change.
Step 0 — Frame the decision
Extract from the request (ask 1–2 questions only if genuinely blocking):
- Options (2–4). If the user names only one ("should we use X?"), add the status-quo/do-nothing option and the 1–2 strongest alternatives — say you did.
- Decision context: what is being built, scale (users/QPS/data volume), team size and existing skills, current stack, timeline.
- Constraints & dealbreakers: licensing limits, budget, compliance, must-run-on-prem, language lock-in, etc.
- Criteria weights — defaults below; honor plain-language overrides ("ops burden matters most", "we optimize for hiring").
State every assumption you make in the brief header. A verdict against the wrong context is worse than no verdict.
Step 1 — Fan out: parallel research sub-agents (per option)
Spawn one research sub-agent per option, concurrently (one message, multiple
Agent calls, subagent_type: "Explore"). Each covers five angles and returns
structured findings — every claim with a url + 1-line evidence, anything
unverified marked as such:
- Project health (for OSS/tools; skip for pure approaches): GitHub keyless REST — stars trend, commit/release cadence, open-vs-closed issue velocity, bus factor, age, backing org/funding. A beautiful README with a dead repo behind it is a trap; this angle catches it. Note: keyless GitHub REST allows 60 req/hr shared across all sub-agents — budget calls, and on a 403 rate-limit mark the angle unknown rather than retrying in a loop.
- Community sentiment: HN Algolia (
hn.algolia.com/api/v1/search?query=...)- web search + Reddit fallback — what practitioners report after adopting: praise, recurring pain points, migration-away stories. Weight experience reports over launch-day hype — and over SEO comparison content ("X vs Y in 2026" listicle farms are marketing surface, not adoption evidence; a real practitioner thread outweighs ten of them).
- Technical claims: official docs + independent benchmarks/comparisons for the capabilities the context actually needs. Label every claim vendor-made vs independently verified. Note version/date — a 2022 benchmark may be void.
- Operational story: licensing (and any recent license changes), managed vs self-hosted options, pricing shape, upgrade pain, hiring pool / learning curve for the stated team.
- Security posture: CVE history and severity pattern, GitHub security advisories, how fast past vulnerabilities were patched, safety of the default configuration, and any compliance certifications the context requires. This evidence feeds the Maturity & health and Operational burden scores (no separate criterion) — but an unpatched-critical-CVE pattern can be a dealbreaker in its own right.
If an angle returns nothing usable, record it as unknown — never fabricate.
Lossless hand-off: each sub-agent writes its full findings to
out/verdicts/.work/<option>.md and returns a compact summary; score in Step 2
from the files, not the summaries — the evidence that decides a verdict must
not be flattened by the relay.
Step 2 — Score
Score each option 0–10 per criterion, weighted. Defaults (overridable in Step 0):
| Criterion | Weight | What it measures |
| Fit for requirements | 30% | Does it actually do what this context needs, natively? |
| Maturity & health | 20% | Project vitality, stability, ecosystem, longevity risk |
| Team & stack fit | 20% | Learning curve vs existing skills; integration cost |
| Operational burden | 15% | Run/upgrade/monitor cost at the stated scale |
| Cost & licensing | 15% | License risk, pricing shape, lock-in |
If a criterion doesn't apply, mark it N/A and renormalize the rest — say so. Dealbreakers (license incompatible, can't meet a hard constraint, project effectively abandoned) disqualify the option outright regardless of score — called out explicitly, not averaged away.
Compute a weighted total /10 per option. Close calls (≤0.5 apart) are ties — say so honestly and let the tiebreaker be a context factor, not false precision.
Step 3 — Emit the brief (ADR-style)
Render the brief in chat per references/adr-template.md (read it when
you reach this step), then save as .md + a self-contained .html (see Output
files). Cite inline with linked URLs; label vendor claims.
Revisit mode
/verdict revisit <path> (or "revisit the postgres verdict") turns the
Revisit when section from a wish into a mechanism. Much cheaper than a full
re-run:
- Read the previous brief (find it in
out/verdicts/by slug if only a topic is given). Extract the recommendation, scores, dealbreakers, and the Revisit when triggers. - Research only the triggers plus two standing checks: any license change and any major-release/abandonment signal since the brief's run date. One Explore sub-agent per option, narrow scope — not the full five angles.
- Emit a short addendum, not a new brief: per trigger — fired / not fired / unknown, with citation — and an overall call: verdict stands / weakened (why) / overturned → recommend a full re-run. Never silently flip a recommendation from a partial check; an overturn verdict recommends the re-run, the human decides.
- Save as
out/verdicts/<slug>-revisit-<YYYY-MM-DD>.md(markdown only — no HTML for addenda) and link the original brief in its header.
Output files
Save to ./out/verdicts/ in the current working directory:
out/verdicts/<slug>-<YYYY-MM-DD>.md— the brief verbatim.out/verdicts/<slug>-<YYYY-MM-DD>.html— a bespoke, distinctively designed version. Self-contained: inline<style>, no JavaScript, no external requests (system fonts), links preserved, the scorecard and recommendation as first-class visual elements, responsive, print-friendly.
<slug> = options joined by -vs-, lowercased. Compute the date with a shell
command (date +%F) — do not guess. Create out/verdicts/ if needed. Briefs
make good shared history, but they may contain internal project context —
committing them is the user's call, not the skill's.
Design the HTML via the frontend-design skill: subject is an engineering
decision record; the page's one job is to make the recommendation, scorecard,
and dealbreakers scannable in ten seconds, with the full evidence beneath.
Design changes presentation only — never scores, evidence, or citations. Fall
back to a clean self-contained no-JS layout if the skill is unavailable.
Tell the user the two saved paths at the end.
Guardrails
- Advisory, not authoritative. Recommend with evidence; the human decides. Never present a close call as decisive.
- Symmetric research. Every option gets the same five angles — no strawmanning the option you suspect will lose.
- Vendor claims labeled. Marketing pages are evidence of intent, not of performance. Independent verification or it's marked "vendor claim."
- No fabrication. Every score traces to cited findings; unknowns stay unknown and are listed in the brief.
- Keyless. Never ask for API keys; degrade gracefully.
- Context is king. The same two options can produce opposite verdicts for different contexts — restate the context prominently so the brief can't be misapplied later.
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.

