ai-output-verifier
Check AI output before you trust or use it — where it's likely wrong, what to verify, and how to catch confident-sounding errors. Use when asked can I trust this AI answer, how do I verify what AI told me, fact-check this AI output, or is this AI response reliable. Produces a risk read on the specific output (the claims most likely to be wrong or made up), the parts that need independent verification vs the parts that are low-risk, how to actually verify each, the tells of AI hallucination and overconfidence, and a habit for building verification into your AI use — because AI is confidently wrong often enough that unchecked trust is a real risk.
git clone --depth 1 https://github.com/mohitagw15856/pm-claude-skills /tmp/ai-output-verifier && cp -r /tmp/ai-output-verifier/exports/openclaw/ai-output-verifier ~/.claude/skills/ai-output-verifierSKILL.md
# AI-Output Verifier AI is fluent, confident, and sometimes completely wrong — inventing facts, citations, and details in the same authoritative tone as the correct ones. That confidence is exactly what makes unverified trust dangerous. This checks a specific output: which claims are most likely wrong or fabricated, what genuinely needs independent verification, how to verify it, and the tells of hallucination — so you use AI's speed without inheriting its errors. ## What This Skill Produces - **A risk read of the output** — which specific claims are most likely to be wrong, outdated, or made up (facts, numbers, citations, names, recent events, specifics) - **Verify vs. low-risk split** — what genuinely needs independent checking vs. what's low-stakes or self-evident, so you spend effort where it counts - **How to verify each** — the concrete way to check the high-risk claims (a primary source, a second tool, a domain expert, testing it) - **The hallucination tells** — the signs AI is likely fabricating (oddly specific citations, confident claims about recent/niche facts, plausible-but-unverifiable details) - **A verification habit** — how to build appropriate checking into your AI use by default, scaled to the stakes (trust more for low-stakes, verify hard for high-stakes) ## Required Inputs Ask for these if not provided: - **The output** — the AI response to check (paste it) - **What it's for** — the stakes (a casual question vs. something you'll publish, decide on, or act on) - **The domain** — factual/technical/legal/medical/current-events (some are far higher-risk for AI) - **What you'd do with it** — trust it, act on it, share it, build on it ## Framework: Risk-Rate The Claims, Verify What Matters 1. **Scan for the high-risk claim types.** Specific facts, numbers, dates, names, citations, recent events, and niche/technical specifics are where AI most often invents — flag these. 2. **Split by risk and stakes.** Separate the claims that genuinely need verification (high-risk × high-stakes) from the low-risk or low-stakes ones you can reasonably accept — don't verify everything equally. 3. **Verify against real sources.** For the high-risk claims, check a primary source, a second independent tool, an expert, or by testing — not by asking the same AI "are you sure?" (it'll often just re-confirm). 4. **Watch the hallucination tells.** Oddly precise citations, confident answers about very recent or obscure things, and unverifiable specifics are red flags — treat them as unverified until checked. 5. **Scale trust to stakes.** For low-stakes uses, light verification is fine; for anything you'll publish, decide on, or that could harm if wrong, verify hard. Build this reflex in. ## Output Format ### Verifying: [the output] · for [use/stakes] **High-risk claims (verify these):** [specific facts/numbers/citations/recent/niche → most likely wrong]. **Low-risk (reasonable to accept):** [self-evident / low-stakes parts]. **How to verify each:** [primary source / second tool / expert / test — not re-asking the same AI]. **Hallucination tells present:** [odd-specific citations · confident on recent/niche · unverifiable specifics]. **Trust level for your use:** [light check for low-stakes / verify hard because it's high-stakes]. ## Quality Checks - [ ] Flags the specific high-risk claim types in the output - [ ] Splits what needs verification from what's low-risk, by stakes - [ ] Gives concrete verification methods (not "ask the AI again") - [ ] Names the hallucination/overconfidence tells present - [ ] Scales the recommended trust to the actual stakes ## Anti-Patterns - **"Verify everything"** equally, ignoring stakes. - **Re-asking the same AI** "are you sure?" as verification. - **Trusting confident tone** as a signal of correctness. - **Missing the high-risk claim types** (citations, recent facts, numbers). - **No stakes-based scaling** of how hard to check. ## Example Trigger Phrases - "Can I trust this answer the AI gave me?" - "How do I verify what ChatGPT told me before I use it?" - "Fact-check this AI output — I'm about to publish it." - "Is this AI response reliable enough to act on?" - "What in this AI answer should I double-check?"
Design a 360-degree feedback survey or write a structured 360 feedback report. Use when asked to build a 360 feedback process, write 360 feedback for a colleague, design a feedback survey, or produce a feedback report. Produces either a complete survey instrument with rating scales and open-ended questions, or a structured narrative feedback report with themes, strengths, and development areas.
Decode a 401k or workplace retirement plan — the real cost of its funds, the match's fine print, vesting math, and the plan features worth using or avoiding. Use when someone asks 'is my 401k any good', 'decode my 401k plan', 'which funds should I look at', or 'what fees am I paying'. Produces a fee decode in dollars-over-time, match and vesting math, a fund-lineup triage by cost, and the questions for HR or the plan administrator.
Design statistically rigorous A/B tests for product features, UI changes, onboarding flows, and pricing experiments. Use when asked to set up an experiment, design an A/B test, calculate sample size, or interpret test results. Produces a complete test plan with hypothesis, variant definitions, sample size, duration estimate, guardrail metrics, and a results interpretation guide.
Analyse a finished A/B test and write the readout — the result, whether it's statistically and practically significant, what it means, and the ship/no-ship call. Use when asked to analyse experiment results, write an A/B test readout, interpret test data, or decide whether to ship a variant. Produces a clear verdict with the lift and confidence, segment cuts, the risks (peeking, novelty, sample), and a recommendation. Distinct from planning a test — this reads results.
Generate a WCAG 2.2 accessibility audit checklist and remediation suggestions for any UI or design. Use when asked to audit for accessibility, check WCAG compliance, review a design for a11y issues, or create an accessibility remediation plan. Produces a prioritised checklist with pass/fail assessments and specific fixes.
Plan a trip that actually works with a disability or access need — confirm real accessibility (not just 'accessible' labels), book the assistance in advance, plan for equipment and medication, and build in the contingencies for when access breaks down. Use when someone says 'plan an accessible trip', 'travelling with a wheelchair/disability', 'book assistance for my flight', or 'will this hotel actually work for me'. Produces an access-verified itinerary, an assistance-booking checklist, an equipment/medication plan, and contingency scripts. Verify specifics with providers.
Request a reasonable accommodation at work or in education — frame it around the barrier and the adjustment (not your diagnosis), cite the right process, and navigate the back-and-forth constructively. Use when someone says 'I need a workplace accommodation', 'request reasonable adjustments', 'ADA/Equality Act accommodation', or 'how do I ask for accommodations for my disability/condition'. Produces the request letter, a barriers-and-adjustments map, disclosure guidance, and a plan for the interactive process. Not legal advice — routes to the formal process and to advocacy where needed.
Build a structured account plan for any key customer or target account. Use when asked to create an account plan, key account strategy, strategic account review, or territory plan. Produces a complete account plan with relationship map, growth opportunities, risks, and 90-day action plan.