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
Draft, adapt, and review contracts and clauses aligned with The Chancery Lane Project's methodology for reducing carbon emissions through legal agreements. Use when Claude needs to: (1) Draft new climate-aligned clauses (e.g., net zero commitments, carbon accounting, supply chain decarbonization), (2) Adapt or modify existing contracts to incorporate climate objectives, (3) Review and analyze clauses for alignment with climate goals and decarbonization strategies, (4) Provide guidance on The Chancery Lane Project's house style and drafting methodology for climate-conscious legal work.
development
Matter budgeting and ongoing WIP/variance monitoring. Build phase-based fee estimates at matter setup, run bottom-up budgets by jurisdiction or workstream, calculate contingency, and structure AFA arrangements (fixed fee, capped fee, phased fixed fees). Ongoing monitoring: WIP tracking against budget, proportionality assessment (spend vs progress), variance commentary with root cause analysis, forecast-to-complete, realisation monitoring, write-off analysis. Trigger on: 'build a budget', 'fee estimate', 'what will this cost', 'WIP review', 'budget vs actual', 'how are we tracking against budget', 'we're over budget', 'realisation is poor', 'what's our ETC', 'budget for the German workstream', 'model the financial impact of this scope change', 'draft a fee adjustment', 'write-off analysis', 'how much contingency', 'AFA structure', 'fixed fee estimate', 'budget update', 'forecast to complete'.
tools
Operational billing execution for legal matters. Monthly bill prep and billing instructions, LC invoice review and disbursement treatment, client billing query responses, cashflow modelling (LC payment obligations vs client receipts), and leverage and burn analysis (staffing mix, predicted total cost, margin trajectory). Trigger on: 'prepare the bill', 'billing instruction', 'end of month billing', 'LC invoice', 'local counsel invoice', 'pass through as disbursement', 'client querying the invoice', 'billing dispute', 'cashflow gap', 'when will we get paid', 'LC payment due', 'leverage analysis', 'staffing mix', 'predicted total cost', 'burn rate by grade', 'are we on track', 'what will this matter cost'.
tools
When your bar comes asking "show me how you billed AI-assisted work" — and ABA 512, Florida 24-1, California, New York, and DC all have opinions out — you need an artifact that survives review. billable-time produces it. From your Claude Code session logs, it drafts reviewable time entries plus a printable HTML audit packet with: SHA-256 chain of evidence (source files + matter.yml + active disclosure pack + verifiable artifact self-hash), attorney identity and signature block, a bar-opinion disclosure pack with starter language for five jurisdictions, and content-aware deterministic narratives derived from filename and tool shape — never from prompt text by default. The tool refuses to bill on its own. --strict mode refuses to ship the artifact if any audit invariant fails (broad routes, missing attorney, missing/unverified disclosure). Comes as a Node CLI and a self-contained browser version (no backend; JSONL never leaves the page). 15 invariant tests verify the contract. AGPL-3.0.