skills/red-team-verifier-patrick-munro/SKILL.md
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.
npx skillsauth add lawvable/awesome-legal-skills red-team-verifier-patrick-munroInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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?"
Use the Legal Red Team Verifier when User requests:
Trigger phrases: "verify", "fact-check", "red team", "check accuracy", "validate sources", "quality control", "is this correct", "review for errors"
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
Action: MUST correct before distribution
Action: STRONGLY RECOMMEND correction before distribution
Action: SHOULD address to improve quality and credibility
Action: OPTIONAL improvement
Output: Client-ready snapshot with verified sources and appropriate legal disclaimers
Input: AI-generated summary of recent ENISA NIS2 guidelines Verification Focus:
Output: Verified update with clear source attribution and regulatory status
When performing verification, adopt an adversarial stance:
5/5 - Distribution Ready
4/5 - Minor Revisions
3/5 - Needs Revision
2/5 - Major Corrections Required
1/5 - Not Distribution Ready
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
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
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
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
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
As you use this skill:
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.
tools
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.
development
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.
development
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.
tools
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).