red-team-verifier-patrick-munro

Adversarial verification for AI-generated legal content with systematic fact-checking, source validation, and quality control. Use when User requests verification of legal documents, fact-checking of regulatory content, red team review, or quality assurance before distribution to clients/stakeholders. Provides structured verification reports with severity-categorized errors, verified sources, and distribution readiness assessment.

250 stars

Best use case

red-team-verifier-patrick-munro is best used when you need a repeatable AI agent workflow instead of a one-off prompt.

Adversarial verification for AI-generated legal content with systematic fact-checking, source validation, and quality control. Use when User requests verification of legal documents, fact-checking of regulatory content, red team review, or quality assurance before distribution to clients/stakeholders. Provides structured verification reports with severity-categorized errors, verified sources, and distribution readiness assessment.

Teams using red-team-verifier-patrick-munro should expect a more consistent output, faster repeated execution, less prompt rewriting.

When to use this skill

  • You want a reusable workflow that can be run more than once with consistent structure.

When not to use this skill

  • You only need a quick one-off answer and do not need a reusable workflow.
  • You cannot install or maintain the underlying files, dependencies, or repository context.

Installation

Claude Code / Cursor / Codex

$curl -o ~/.claude/skills/red-team-verifier-patrick-munro/SKILL.md --create-dirs "https://raw.githubusercontent.com/lawvable/awesome-legal-skills/main/skills/red-team-verifier-patrick-munro/SKILL.md"

Manual Installation

  1. Download SKILL.md from GitHub
  2. Place it in .claude/skills/red-team-verifier-patrick-munro/SKILL.md inside your project
  3. Restart your AI agent — it will auto-discover the skill

How red-team-verifier-patrick-munro Compares

Feature / Agentred-team-verifier-patrick-munroStandard Approach
Platform SupportNot specifiedLimited / Varies
Context Awareness High Baseline
Installation ComplexityUnknownN/A

Frequently Asked Questions

What does this skill do?

Adversarial verification for AI-generated legal content with systematic fact-checking, source validation, and quality control. Use when User requests verification of legal documents, fact-checking of regulatory content, red team review, or quality assurance before distribution to clients/stakeholders. Provides structured verification reports with severity-categorized errors, verified sources, and distribution readiness assessment.

Where can I find the source code?

You can find the source code on GitHub using the link provided at the top of the page.

SKILL.md Source

# Legal Red Team Verifier

## Purpose

This skill provides systematic adversarial verification of AI-generated legal content to ensure factual accuracy, proper legal citations, and appropriate disclaimers before distribution to clients or stakeholders. It addresses the #1 concern about AI in legal practice: "How do I know this is accurate?"

## When to Use This Skill

Use the Legal Red Team Verifier when User requests:
- Verification of AI-generated legal content before client/stakeholder distribution
- Fact-checking of legal snapshots, briefings, or analyses
- Quality control on compliance documents, regulatory summaries, or legal reports
- Red team review of legal outputs (e.g., "verify this", "fact-check this", "red team this document")
- Adversarial testing of legal claims or arguments

**Trigger phrases**: "verify", "fact-check", "red team", "check accuracy", "validate sources", "quality control", "is this correct", "review for errors"

## Core Verification Categories

### 1. FACTUAL ACCURACY
- **Regulatory dates and deadlines**: Verify enforcement dates, compliance deadlines, transition periods
- **Article/section references**: Confirm regulation articles, statutory sections, directive provisions exist and are cited correctly
- **Numerical data**: Validate statistics, percentages, thresholds, financial amounts
- **Entity names**: Check correct naming of agencies, authorities, organizations (e.g., BaFin, ESTI, ENISA, European Commission)
- **Timeline accuracy**: Verify historical events, legislative milestones, implementation schedules

### 2. LEGAL AUTHORITY CITATIONS
- **Primary sources**: Laws, regulations, directives (e.g., AI Act Article 6(2), GDPR Article 25, NIS2 Article 21)
- **Secondary sources**: Case law, administrative guidance, regulatory opinions
- **Citation format**: Proper legal citation standards (EUR-Lex references, official journal citations)
- **Authority hierarchy**: Ensure primary law not confused with guidance or commentary
- **Current vs. superseded**: Verify using current version, not outdated provisions

### 3. ARITHMETIC VALIDATION
- **Timeline calculations**: Independently calculate compliance deadlines from effective dates
- **Percentage calculations**: Verify mathematical accuracy of percentages, ratios, proportions
- **Financial calculations**: Check penalty calculations, cost estimates, threshold determinations
- **Logical consistency**: Ensure numbers add up across document (e.g., if mentioning "3 categories" verify exactly 3 are listed)

### 4. SOURCE VERIFICATION
- **Verifiable claims**: Every factual claim must link to a verifiable source
- **Official sources prioritized**: EUR-Lex, official gazettes, government websites, regulatory authority publications
- **No unsourced statistics**: Flag any statistical claim without attribution
- **No unsourced quotes**: Every quote must have proper attribution
- **Cross-referencing**: Critical claims verified against multiple independent sources

### 5. SPECULATION DETECTION
- **Opinion vs. fact**: Clearly distinguish editorial opinion from factual legal requirements
- **Uncertainty acknowledgment**: Identify areas where legal interpretation is unsettled or debated
- **Predictive claims**: Flag statements about future regulatory developments as speculation
- **"Likely" and "probably"**: Ensure speculative language is clearly labeled as such
- **Editorial framing**: Identify where AI has inserted interpretive framing not present in source material

### 6. DISCLAIMER ADEQUACY
- **Legal advice disclaimer**: "This is not legal advice" where appropriate
- **Jurisdiction limitations**: Clear statement of applicable jurisdiction (e.g., "Based on German/EU law")
- **Date/version disclaimer**: Document version/date of regulations cited
- **Professional consultation**: Recommendation to consult qualified legal professionals for specific situations
- **Regulatory uncertainty**: Disclosure where regulation is pending, in draft, or interpretation unclear

## Verification Methodology

### STEP 1: Initial Content Review
- Read entire document to understand scope and claims
- Identify all factual claims, legal citations, numerical data, and authoritative statements
- Note any missing sources, vague language, or unsupported assertions

### STEP 2: Source Verification (ALWAYS ONLINE)
- **MANDATORY**: Use web_search for EVERY factual claim, legal citation, and statistical assertion
- Prioritize official sources:
  - EUR-Lex (https://eur-lex.europa.eu) for EU legislation
  - Official government websites (.gov, .gov.uk, .bund.de, .europa.eu)
  - Regulatory authority sites (BaFin, ESTI, ENISA, BSI)
  - Official gazettes and legal databases
- Cross-reference critical claims across multiple sources
- Document source URLs for all verified facts

### STEP 3: Arithmetic Verification
- Independently calculate all timelines, deadlines, and dates
- Verify all percentages, ratios, and financial figures
- Check internal consistency (e.g., if document says "3 types" verify exactly 3 are listed)
- Flag any mathematical errors or inconsistencies

### STEP 4: Citation Validation
- Verify article/section numbers exist in cited regulations
- Check that citations match current versions (not superseded provisions)
- Ensure proper legal citation format
- Confirm quotes are accurate (not paraphrased but presented as quotes)

### STEP 5: Speculation Identification
- Flag any predictive statements about regulatory developments
- Identify editorial opinions presented as facts
- Note areas of legal uncertainty or debate
- Ensure speculative content is clearly labeled

### STEP 6: Disclaimer Review
- Check for legal advice disclaimers
- Verify jurisdiction is clearly stated
- Ensure date/version of regulations is specified
- Confirm recommendation for professional consultation where appropriate

## Output Structure

Provide verification results in the following structured format:

```
# LEGAL RED TEAM VERIFICATION REPORT

## Document Analyzed
[Title/description of content verified]

## Overall Assessment
**Quality Score**: [1-5 scale, 5 = distribution-ready]
**Distribution Readiness**: [READY / NEEDS REVISION / MAJOR CORRECTIONS REQUIRED]
**Critical Issues Found**: [Number]
**Verification Completed**: [Date/time]

---

## ✅ VERIFIED FACTS
[List all factual claims successfully verified with sources]
- Claim: [statement]
  Source: [official source URL]
  Status: ✅ VERIFIED

---

## ❌ ERRORS REQUIRING CORRECTION

### CRITICAL (Immediate correction required)
- **Error**: [Description of factual error, legal misstatement, or arithmetic mistake]
  **Location**: [Where in document]
  **Correction**: [What should it say]
  **Source**: [Correct source URL]

### HIGH (Correction strongly recommended)
- **Issue**: [Missing critical disclaimer, regulatory uncertainty not disclosed]
  **Impact**: [Why this matters]
  **Recommendation**: [Suggested addition/revision]

### MODERATE (Should be addressed)
- **Issue**: [Unsourced statistics, editorial framing as fact]
  **Impact**: [Credibility/accuracy concern]
  **Recommendation**: [How to improve]

### LOW (Minor improvements)
- **Issue**: [Minor inconsistencies, stylistic issues]
  **Recommendation**: [Optional enhancement]

---

## ⚠️ UNSUPPORTED CLAIMS
[Claims requiring verification or removal]
- **Claim**: [Statement made without source]
  **Status**: Could not verify through official sources
  **Action Required**: Either provide source or remove claim

---

## 📋 MISSING DISCLAIMERS
[Recommended disclaimer additions]
- **Location**: [Where to add]
  **Type**: [Legal advice / Jurisdiction / Date-version / Professional consultation]
  **Suggested Language**: [Specific disclaimer text]

---

## 🎯 DETAILED FINDINGS

### Factual Accuracy
[Detailed analysis of factual claims]

### Legal Citations
[Analysis of legal authority citations]

### Arithmetic Validation
[Analysis of numerical accuracy]

### Source Quality
[Assessment of sources used]

### Speculation & Opinion
[Analysis of speculative vs. factual content]

### Disclaimer Adequacy
[Assessment of disclaimers and qualifications]

---

## 📊 VERIFICATION STATISTICS
- Total claims verified: [N]
- Official sources consulted: [N]
- Errors found: [N]
- Unsupported claims: [N]
- Missing disclaimers: [N]

---

## RECOMMENDATIONS FOR DISTRIBUTION

**If READY**: Document meets quality standards for distribution
**If NEEDS REVISION**: Address HIGH and CRITICAL issues before distribution
**If MAJOR CORRECTIONS REQUIRED**: Extensive revision needed; consult original sources
```

## Severity Taxonomy

### CRITICAL
- **Factual errors**: Incorrect dates, wrong article numbers, false statements
- **Arithmetic mistakes**: Calculation errors, timeline mistakes, wrong percentages
- **Legal misstatements**: Misrepresenting legal requirements or obligations
- **Attribution errors**: Quotes or claims attributed to wrong source

**Action**: MUST correct before distribution

### HIGH
- **Missing critical disclaimers**: No legal advice disclaimer where needed
- **Regulatory uncertainty not disclosed**: Presenting unsettled law as certain
- **Jurisdiction ambiguity**: Not clear what legal system applies
- **Outdated legal references**: Citing superseded provisions

**Action**: STRONGLY RECOMMEND correction before distribution

### MODERATE
- **Unsourced statistics**: Numbers without attribution
- **Editorial framing as fact**: Opinion presented as objective requirement
- **Vague language**: Ambiguous terms that could mislead
- **Incomplete citations**: Missing EUR-Lex references or official journal citations

**Action**: SHOULD address to improve quality and credibility

### LOW
- **Minor inconsistencies**: Small formatting or style issues
- **Optional enhancements**: Additional context that would improve clarity
- **Stylistic preferences**: Wording choices that could be improved

**Action**: OPTIONAL improvement

## Use Case Examples

**Output**: Client-ready snapshot with verified sources and appropriate legal disclaimers

### Example 3: Regulatory Update for Stakeholders
**Input**: AI-generated summary of recent ENISA NIS2 guidelines
**Verification Focus**:
- Verify ENISA publication exists and date is correct
- Check all quoted guidance language against original
- Validate interpretation of non-binding guidance vs. legal requirements
- Ensure clear labeling of "recommendations" vs. "obligations"
- Verify URLs to official ENISA publications

**Output**: Verified update with clear source attribution and regulatory status

## Critical Requirements

### ALWAYS Verify Online
- NEVER rely solely on AI-generated content or memory
- ALWAYS use web_search to verify factual claims against official sources
- NEVER assume dates, article numbers, or legal citations are correct without verification
- ALWAYS cross-reference critical claims across multiple sources

### Source Hierarchy
1. **Primary legal sources**: Official legislation (EUR-Lex, official gazettes)
2. **Official guidance**: Regulatory authority publications (BaFin, ENISA, BSI, European Commission)
3. **Secondary legal sources**: Court decisions, legal commentary
4. **Tertiary sources**: News articles, blog posts (use with extreme caution)

### Transparency Requirements
- ALWAYS provide source URLs for verified facts
- ALWAYS acknowledge when claims cannot be verified
- ALWAYS disclose areas of legal uncertainty or debate
- NEVER present speculation as fact

## Adversarial Mindset

When performing verification, adopt an adversarial stance:
- **Assume error until proven correct**: Don't trust AI-generated content
- **Seek contradictory evidence**: Actively look for information that contradicts claims
- **Question every number**: Independently verify all calculations
- **Demand sources**: Every factual claim must have verifiable attribution
- **Test logical consistency**: Look for internal contradictions
- **Challenge interpretations**: Where AI presents legal interpretation, verify against authoritative sources

## Quality Standards

**5/5 - Distribution Ready**
- All factual claims verified with official sources
- All legal citations confirmed accurate
- All arithmetic independently validated
- Appropriate disclaimers present
- No critical or high-severity issues
- Professional quality suitable for client/stakeholder distribution

**4/5 - Minor Revisions**
- Factual claims verified but some moderate issues found
- May have unsourced statistics that should be added
- Disclaimers adequate but could be enhanced
- No critical issues, only moderate or low severity

**3/5 - Needs Revision**
- Some factual errors or unsupported claims found
- Missing important disclaimers
- High-severity issues present
- Requires revision before distribution

**2/5 - Major Corrections Required**
- Multiple factual errors identified
- Significant legal citation problems
- Critical issues present
- Extensive revision needed

**1/5 - Not Distribution Ready**
- Fundamental errors in core legal statements
- Pervasive unsupported claims
- Multiple critical issues
- Requires complete rework

## Customization by Jurisdiction

### EU/German Law Focus
- Prioritize EUR-Lex, German official gazettes (BGBl)
- Verify BaFin, BSI, ENISA guidance
- Check German statutory citations (BGB, BDSG, GeschGehG, etc.)
- Verify EU directive transposition status for Germany

### General Legal Verification
- Adapt source hierarchy to relevant jurisdiction
- Use appropriate official sources (gov websites, legal databases)
- Adjust citation formats to jurisdiction standards
- Modify disclaimer language as appropriate

## Examples of Known AI Hallucination Patterns

### Pattern 1: Plausible but Wrong Article Numbers
**Problem**: AI generates realistic-sounding article citations that don't exist
**Example**: "AI Act Article 42(5)" when AI Act only has Article 42(1)-(4)
**Verification**: Always check official EUR-Lex text for exact article structure

### Pattern 2: Confident but Incorrect Dates
**Problem**: AI states dates with confidence but gets them wrong
**Example**: "NIS2 applies from October 2024" when actual date is October 17, 2024
**Verification**: Independently verify all dates against official sources

### Pattern 3: Mixing Guidance and Legal Requirements
**Problem**: AI presents regulatory guidance as legal obligation
**Example**: Treating ENISA recommendations as binding NIS2 requirements
**Verification**: Distinguish between binding legal text and non-binding guidance

### Pattern 4: Outdated Legal References
**Problem**: AI cites superseded or amended provisions
**Example**: Citing original GDPR text when regulation has been practically interpreted by CJEU
**Verification**: Check for amendments, implementing acts, and authoritative interpretations

### Pattern 5: Arithmetic Errors in Timeline Calculation
**Problem**: AI makes mistakes calculating deadlines from effective dates
**Example**: Claiming "18 months from October 2024 is March 2026" (actually April 2026)
**Verification**: Independently calculate all timelines

## Continuous Improvement

As you use this skill:
- **Document new hallucination patterns** encountered
- **Refine verification methodology** based on findings
- **Build library of reliable sources** for different legal areas
- **Track error types** to identify systematic AI weaknesses
- **Share learnings** to improve legal AI verification practices

---

## Critical Reminder

**The purpose of this skill is adversarial verification**. Approach every AI-generated legal claim with skepticism. Your role is not to confirm what the AI said, but to independently verify whether it's accurate, properly sourced, and appropriately disclaimed. When in doubt, verify. When you can't verify, flag it. Better to over-verify than to distribute inaccurate legal information.

Related Skills

vendor-due-diligence-patrick-munro

250
from lawvable/awesome-legal-skills

Framework for assessing IT service providers, technology vendors, and third-party partners. Creates structured risk assessments across financial, operational, compliance, security, and reputational dimensions with regulatory checklists (GDPR, DORA, NIS2, SOX). Use when: (1) Evaluating new vendors or technology providers, (2) Conducting third-party risk assessments for procurement, (3) Performing critical vendor due diligence for regulatory compliance, (4) Creating vendor onboarding documentation, (5) Establishing ongoing vendor monitoring processes, (6) Assessing vendor concentration risk, or (7) Generating executive-level vendor risk reports.

tech-contract-negotiation-patrick-munro

250
from lawvable/awesome-legal-skills

Guide to negotiating technology services agreements, professional services contracts, and commercial B2B transactions. Provides three-position frameworks (provider-favorable, balanced, client-favorable), deal-size tactics, objection handling templates, and concession roadmaps. Use when: (1) Developing negotiation strategies for SaaS, cloud, or managed services agreements, (2) Preparing position papers and fallback positions, (3) Responding to counterparty objections and demands, (4) Creating concession roadmaps that protect critical interests, (5) Assessing tactics based on deal value and leverage, or (6) Structuring balanced outcomes for liability, IP, payment, SLA, or warranty provisions.

legal-simulation-patrick-munro

250
from lawvable/awesome-legal-skills

Framework for demonstrating AI capabilities in legal contexts. Provides detailed personas across tenant law, business contracts, startup disputes, employment claims, and consumer protection with progressive complexity scenarios. Use when: (1) Demonstrating AI-powered legal triage or intake systems, (2) Showcasing responsible AI-assisted client interactions, (3) Training staff on appropriate AI use in legal contexts, (4) Creating realistic scenarios for legal tech presentations, (5) Developing educational materials about AI in legal services, or (6) Testing AI-powered legal information systems in controlled environments.

xlsx-processing-openai

250
from lawvable/awesome-legal-skills

Toolkit for comprehensive Spreadsheet reading, creation, editing, and analysis with visual quality control. Use to work with spreadsheets (.xlsx, .xlsm, .csv, .tsv) for: (1) Creating new spreadsheets with formulas and formatting, (2) Reading or analyzing tabular data, (3) Modifying existing spreadsheets while preserving formulas, (4) Building financial models with proper formatting, (5) Data visualization with in-sheet charts, or any other spreadsheet tasks.

xlsx-processing-manus

250
from lawvable/awesome-legal-skills

Professional Excel spreadsheet creation with a focus on aesthetics and data analysis. Use when creating spreadsheets for organizing, analyzing, and presenting structured data in a clear and professional format.

xlsx-processing-anthropic

250
from lawvable/awesome-legal-skills

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API integration, even if tabular data is involved.

vscode-extension-builder-lawvable

250
from lawvable/awesome-legal-skills

Build VS Code extensions from scratch or convert existing JS/React/Vue apps. Supports commands, webviews (React/Vue), custom editors, tree views, and AI agent integration via file-bridge IPC. Use when user wants to create a VS Code extension, convert a web app to an extension, add webviews or custom UIs to VS Code, implement tree views, build custom file editors, integrate with AI agents, or package/publish extensions (.vsix).

tabular-review-lawvable

250
from lawvable/awesome-legal-skills

Guide to analyze multiple documents (PDF, DOCX) against user-defined columns and produce a structured Excel output with citations. Use when the user wants to: (1) Extract specific information from multiple documents into a table, (2) Compare clauses or provisions across contracts, (3) Create a document review matrix with source citations. Triggers on: 'tabular review', 'document matrix', 'extract from documents', 'compare across documents', 'review multiple contracts'.

statute-analysis-rafal-fryc

250
from lawvable/awesome-legal-skills

Guide for reading, interpreting, and applying statutes, regulations, and rules in legal and compliance contexts. Use when the user asks about (1) how to read and interpret statutes, regulations, or rules, (2) statutory interpretation methods and canons of construction, (3) understanding legislative intent, (4) applying statutes to specific legal situations, (5) extracting requirements from legal text, (6) distinguishing between different types of legal requirements, or (7) cross-jurisdictional compliance analysis.

skill-optimizer-lawvable

250
from lawvable/awesome-legal-skills

Guide to analyze a current work session and propose improvements to skills. Use (1) automatically after working with a skill to capture learnings, (2) when the user suggests improvements, corrections, or additions during a skill-related session, or (3) when the user manually invokes `self-improve`.

skill-creator-openai

250
from lawvable/awesome-legal-skills

Guide for creating effective skills. Use when users want to create a new skill (or update an existing skill) that extends the model's capabilities with specialized knowledge, workflows, or tool integrations.

skill-creator-anthropic

250
from lawvable/awesome-legal-skills

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.