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.
development
Perform language and framework specific security best-practice reviews and suggest improvements. Trigger only when the user explicitly requests security best practices guidance, a security review/report, or secure-by-default coding help. Trigger only for supported languages (python, javascript/typescript, go). Do not trigger for general code review, debugging, or non-security tasks.
development
Expert CMMC 2.0 (Cybersecurity Maturity Model Certification) advisor for US defense contractors and subcontractors in the Defense Industrial Base (DIB). Use this skill whenever a user asks about CMMC 2.0, CMMC Level 1, Level 2, or Level 3, DoD cybersecurity compliance, NIST SP 800-171, CUI (Controlled Unclassified Information) protection, System Security Plan (SSP), Plan of Action & Milestones (POA&M), C3PAO assessments, DIBCAC audits, self-assessment, SPRS score, or any requirement under DFARS 252.204-7012 or 7021. Also trigger for: "CMMC gap analysis", "CMMC readiness", "FCI protection", "CUI scoping", "CMMC practices", "DoD contract cybersecurity", "defense supply chain security", or "prime contractor flow-down requirements".
tools
Build a client instruction schedule — a plain-English, Scott Schedule-style Word table that gathers a struggling client's evidence and instructions issue by issue, with a one-page covering note. Use whenever the user asks for a "client instruction schedule", "instruction schedule", "client questionnaire", "schedule of questions for the client", "get instructions from the client on the papers", or says the client is overwhelmed and needs the case broken into manageable questions. Also trigger when asked to turn case papers into a structured request for client input. Do NOT use for court-facing Scott Schedules, pleadings, witness statements, or advice letters — this skill produces a client-facing working document only. Output is always a .docx draft for solicitor review, never a final document.
tools
Turn complex legal analysis into clear, commercially useful client-facing advice. Use this whenever the user has dense legal material — drafting, internal analysis, counsel notes, research memos, pleadings, a case update, or correspondence — and wants it converted into something a client can actually understand and act on. Trigger on phrases like 'explain this to the client', 'put this in plain English', 'translate this for a non-lawyer', 'turn this into client-facing advice', 'make this client-ready', 'draft a client update', or when the user shares legal analysis and asks 'what does this mean for them'. Also trigger when the user wants a board summary, litigation risk update, or call script derived from legal material. The skill preserves legal nuance, uncertainty, and risk rather than oversimplifying — it makes advice usable, not just simpler.