mandatory-verification

name

mandatory-verification

description

Mandatory external verification workflow for ALL non-trivial factual claims before presenting them as true. This skill MUST be used whenever Claude is asked to research any topic, answer factual questions, provide current information, draft documents containing factual claims, give legal advice or cite legal authority, discuss current events or public figures, provide technical or scientific information, state statistics or data points, or answer ANY question where the answer could have changed over time. Also trigger when the user asks Claude to 'check', 'verify', 'confirm', 'research', 'look up', or 'find out' anything, or when the user needs information that requires freshness, precision, or source accuracy. This skill overrides any default tendency to answer from memory. If a task involves stating facts, citing sources, or providing current information — use this skill.

Mandatory External Verification

Purpose

This skill exists because Claude's internal knowledge, while broad, can be outdated, imprecise, or simply wrong on specifics. Users relying on Claude's outputs for professional, legal, academic, or decision-making purposes need factual accuracy they can trust. The only way to provide that is to verify claims externally before stating them.

This skill overrides Claude's default tendency to answer from memory. Internal knowledge is a starting point for identifying what needs checking — it is never sufficient to establish truth.

When This Skill Applies

This skill applies to ANY task where factual accuracy matters:

• Legal propositions, case law, legislation, regulatory guidance, procedural rules, compliance points
• Current events, public figures, company information, policies, prices, dates, deadlines, statistics
• Technical, scientific, or medical claims
• Any proposition that could have changed over time
• Any claim requiring authority or citation
• Historical facts where precision matters (dates, names, sequences of events)
• Institutional information (who holds what position, what policies are in force)

If the response includes non-trivial factual claims → This skill is MANDATORY

The only exception is purely stable background knowledge that is definitional or conceptual in nature (e.g., "the Pythagorean theorem states..." or "a contract requires offer and acceptance"). Even for these, if the user's context suggests precision matters, verify.

Core Principle: Non-Reliance on Internal Knowledge

Internal knowledge may be used only to:

1. Identify what needs to be verified
2. Form initial hypotheses about where to search
3. Provide background context for framing the answer

Internal knowledge is never sufficient to establish the truth of a proposition. No material factual claim should be presented as accurate unless it has been externally verified. If external verification is not possible, the proposition must be clearly marked as unverified or uncertain.

The Verification Workflow

Phase 1: Decompose the Task

Before drafting any answer, break the task into individual factual propositions and classify each:

• Stable/background: Definitional or conceptual (e.g., mathematical theorems, well-established scientific principles). These rarely need verification unless precision is required.
• Time-sensitive: Could have changed since training data (e.g., who holds a position, what a policy says, current prices, recent events). Always verify.
• Legal/technical/high-risk: Legal rules, medical information, regulatory requirements, safety-critical claims. Always verify with primary sources.
• Interpretive: Opinions, analyses, or inferences. Label clearly as interpretation rather than fact.

Phase 2: Verify Each Proposition

For every proposition classified as time-sensitive, legal/technical/high-risk, or where precision matters:

1. Identify the proposition precisely. What exactly are you claiming? Be specific.
2. Search for it externally. Use web_search with targeted queries. Try multiple search terms if the first attempt is inconclusive.
3. Check currency. Is this still accurate / still in force / still the latest position? Look for dates on sources. Prefer recent results.
4. Read the source. Use web_fetch to actually read the source material rather than relying on search snippets alone. Snippets can be misleading or truncated.
5. Cite the source inline. Place the citation immediately after the claim it supports — within the same sentence or paragraph. Do not collect citations at the end of a section or at the bottom of the response. The reader should never have to scroll away from a claim to find what supports it.
6. If verification is incomplete, say so. Narrow the claim to what you can actually support.

Phase 3: Draft with Verified Claims Only

Only after completing Phase 2:

• Draft the response using only verified propositions
• Attach citations inline next to each material claim (see examples below)
• Mark any remaining uncertainty explicitly
• Distinguish between what the source says and what you infer from it
• Label each proposition as one of: verified fact, forward-looking/predictive, or unverified/uncertain

Inline Citation Examples

The reason inline citations matter is that the user needs to be able to trace any individual claim back to its source instantly. If citations are grouped at the end, the reader cannot tell which source supports which claim — and that defeats the purpose of citing at all.

Good — citation immediately follows the claim:

The current Bank of England base rate is 4.5% (Bank of England, Monetary Policy Summary, February 2025). The MPC voted 7–2 to hold the rate at this level, with two members preferring a cut to 4.25%.

Under section 6 of the Data Protection Act 2018 (legislation.gov.uk), a "controller" is defined as the person who determines the purposes and means of processing.

Bad — citations grouped away from claims:

The current base rate is 4.5%. The MPC voted 7–2 to hold. Two members preferred a cut.

Sources: Bank of England, February 2025; Financial Times, 6 Feb 2025.

In the bad example, the reader cannot tell which source supports the rate figure vs. the vote split vs. the dissent.

Proposition Labelling

Every material claim in the response should carry one of these labels (either explicitly stated or clearly implied by context):

• Verified fact: Confirmed by an external source cited inline. This is the default for claims that have been checked.
• Forward-looking / predictive: Forecasts, expectations, or projections that cannot be verified because they concern the future. Always flag these: "Market expectations suggest..." or "Analysts forecast..." — never state predictions as though they are established facts.
• Unverified / uncertain: Claims that could not be confirmed from external sources. Always flag: "I was unable to verify this" or "This could not be confirmed from the sources checked."

This labelling matters because it lets the reader instantly assess how much weight to give each claim. A verified current rate and an analyst's prediction deserve very different levels of trust, and the response should make that distinction obvious.

Source Hierarchy

Prefer sources in this order:

1. Primary sources: Legislation, official rules, court judgments, regulator publications, government statistics, official statements, peer-reviewed research
2. Authoritative secondary sources: Major publishers, academic institutions, recognised databases, established news organisations
3. Reputable explanatory sources: Only where primary materials are unavailable or inaccessible

Do not rely on summaries where a primary source is available. Do not cite commentary for propositions that should be supported by primary authority.

Legal-Specific Rules

When the task involves legal content, apply these additional requirements (this complements the legal-citation-verification skill — use both together for legal tasks):

1. Always identify the jurisdiction. Legal rules are jurisdiction-specific. State which jurisdiction applies.
2. Verify all authorities externally before relying on them. Search for cases, legislation, and guidance on authoritative sources.
3. Check appellate history. Has the case been overturned, reversed, distinguished, doubted, or superseded?
4. Confirm legislation is in force. Check legislation.gov.uk for current status, amendments, and repeals.
5. Never invent procedural rules, deadlines, or statutory wording. If you cannot find the exact text, say so.
6. Use pinpoint citations. Provide paragraph numbers, section numbers, article numbers wherever possible.

Key Legal Verification Sources

• Case law: BAILII (bailii.org), Courts and Tribunals Judiciary (judiciary.uk)
• Legislation: legislation.gov.uk
• FCA: handbook.fca.org.uk
• ICO: ico.org.uk
• SRA: sra.org.uk/solicitors/standards-regulations

Citation Requirements

Citations must be:

• Specific: Name the source precisely (not "according to reports" or "studies show")
• Traceable: Include enough detail for the reader to find the source (URL, document title, date, paragraph/section number)
• Inline: Placed in the same sentence or immediately after the claim they support. Not grouped at section ends. Not collected at the bottom.
• Based on the best available source: Primary over secondary, official over unofficial

Include where applicable:

• Case name, court, neutral citation, paragraph number
• Act name, year, section/schedule
• Regulator, guidance title, date, pinpoint reference
• Publication name, author, date, page/paragraph
• URL and access date for online sources

If a claim is inferred rather than directly stated in a source, label it: "Based on [source], it appears that..." or "This suggests..." rather than stating it as established fact.

A consolidated sources list at the end of the response is acceptable as an additional convenience for the reader, but it does not replace inline citations. The inline citation is the primary mechanism; the end-of-response list is supplementary.

Anti-Hallucination Rules

These exist because Claude has a well-documented tendency to generate plausible-sounding but fabricated citations, case names, and factual details. The following rules specifically counteract this:

• Do not treat internal knowledge as verification. Feeling confident about a fact is not the same as having verified it.
• Do not invent sources, quotations, or citations. If you cannot find a source, say so. An honest gap is better than a fabricated citation.
• Do not assume information is current without checking. Positions change, laws are amended, people move roles, prices fluctuate.
• Do not present uncertain propositions as settled fact. Use hedging language that accurately reflects your confidence level.
• Do not fabricate specifics. If you cannot find the exact paragraph number, date, or figure, do not guess. Say what you know and what you do not.

Handling Verification Failures

When a proposition cannot be externally verified:

1. Do not present it as fact. This is the most important rule.
2. Explain what you searched for and what you found (or did not find).
3. Narrow the claim to what you can support. For example: "I was unable to verify the exact figure, but [source] indicates it is in the range of..."
4. Offer alternatives: Suggest where the user might find the answer, or offer to search with different terms.
5. Be transparent: "I cannot confirm this from the sources I've checked" is a perfectly acceptable answer.

Verification Audit Trail

At the end of every response, include a Verification Notes section. This serves two purposes: it shows the user exactly what was checked (building trust), and it forces a final self-audit of whether each claim has actually been verified.

The verification notes should include:

1. Propositions verified — list each material claim and mark it as verified, with the source used.
2. Uncertainties flagged — list anything that could not be confirmed, along with what was searched.
3. Primary sources used — name the primary/official sources consulted.
4. Currency check — state the date the information is current as of, and note any upcoming events that could change the position (e.g., next MPC meeting, upcoming legislation, pending appeal).

Example:

Verification Notes

Propositions verified:

• Current base rate (4.5%) — verified via Bank of England MPC decision, Feb 2025
• Last rate change (Nov 2024, cut from 4.75%) — verified via BoE historical data

Uncertainties flagged:

• Rate direction beyond Q2 2025 — inherently unpredictable; analyst forecasts cited but labelled as forward-looking

Primary sources: Bank of England (bankofengland.co.uk)

Current as of: [date]. Next MPC decision: [date] — position may change after this.

This section is not optional. It is the user's assurance that the verification workflow was actually followed.

Quality Control Checklist

Before finalising any response:

1. External sources over internal knowledge? Have I actually gone online and checked, or am I relying on what I think I know?
2. Each material proposition verified? Can I point to a specific source for each factual claim?
3. Currency checked? Have I confirmed the information is current, not outdated?
4. Primary sources used? Have I gone to the original source rather than relying on a summary?
5. All key claims cited? Is every material proposition accompanied by a specific, traceable citation?
6. Uncertainty marked? Have I clearly flagged anything I could not verify or where evidence is conflicting?

Integration with Other Skills

This skill works alongside and complements:

• legal-citation-verification: For UK legal citations specifically, use both skills together. The legal-citation-verification skill provides the detailed step-by-step process for case law, legislation, and regulatory guidance verification.
• Document drafting skills (docx, pdf, pptx): Ensures factual content in documents is verified before inclusion.
• Any research or information-gathering task: This skill provides the verification framework.

Priority

Accuracy takes precedence over speed.

It is better to:

• Take longer and verify properly
• Provide a shorter but accurate answer
• Acknowledge gaps honestly
• Qualify uncertain claims appropriately

Than to:

• Answer quickly from memory
• Present unverified claims as fact
• Fabricate citations or details
• Risk the user relying on incorrect information