casemark/authority-verification
skills/legal/authority-verification/SKILL.md
Verifies legal citations and retrieves source material using the case.dev Legal Research API and CLI. Use when validating a citation, confirming a case exists, pulling source text, finding related authorities, extracting citations from a brief or opinion, or building a filing-ready authority check without branded citator terminology.
$ install --global
skillsauthnpx skillsauth add casemark/skills authority-verificationInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
Security Scan Results
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
3
Scanners Passed
9
Scanners in report
Clean
TrivyContainer and dependency vulnerability scanner
95%
Clean
SemgrepStatic code analysis for vulnerabilities
95%
Clean
mcp-scan (Snyk)Model Context Protocol security validation
95%
Skipped
Snyk (dep)Open source security scanning
50%
Skipped
Socket.devSupply chain security analysis
50%
Skipped
VirusTotalMulti-engine malware detection
50%
Skipped
CrowdStrikeAdvanced threat intelligence
50%
Skipped
OSV-ScannerOpen Source Vulnerability database check
50%
Skipped
OWASP Dep-Check
50%
Last scanned: May 25, 2026, 3:29 AM29.4s9 files scanned
SKILL.md
- name:
- authority-verification
- language:
- en
- description:
- >-
Authority Verification with case.dev
Use case.dev legal research endpoints to verify citations, retrieve source text, and expand to related authorities. Keep the language generic: "verified citation," "candidate authority," "related authority," and "manual treatment review."
Quick Start
- Verify the citation text with
legal.verify()before citing it. - If verification is unclear, search by topic with
legal.find()orlegal.research(). - Pull the full document text with
legal.fullText()once you have a verified source URL. - Expand outward with
legal.similar()to find related authorities. - Format the result using references/OUTPUT-TEMPLATE.md.
Reference guide: references/CASEDEV-WORKFLOW.md
Runtime and setup: references/RUNTIME.md
Concrete scenarios: references/EXAMPLES.md
Lightweight eval set: references/EVALS.md
Examples:
- Python: scripts/verify_authority.py
- TypeScript: scripts/verify_authority.ts
- CLI: scripts/verify_authority.sh
Core Workflow
1. Verify the citation
Use legal.verify() with the citation text exactly as written.
verifiedmeans the citation matched a real source in the database.not_foundmeans likely typo, hallucination, or unsupported citation.multiple_matchesmeans manual review is required before citation.
2. Retrieve the source text
If verification succeeds, use the returned case URL with legal.fullText() to inspect the opinion and optionally highlight the issue you care about.
3. Expand the authority set
Use legal.similar() on the verified source URL to find related authorities.
Use legal.research() when you need broader issue-based research with multiple phrasings of the same question.
4. Audit a document
If you are checking a brief, opinion, or article URL, use legal.citationsFromUrl() to extract cited authorities, then verify important citations individually.
5. Record the result
Always record:
- the exact citation checked
- verification status
- authoritative URL
- jurisdiction used for search
- date checked
- any manual review needed before filing
Guardrails
- Do not say a case was "Shepardized," "KeyCited," or given a proprietary signal.
- Do not describe case.dev results as editorial treatment analysis unless you performed separate manual review.
- Say "verified citation" instead of "good law."
- Say "manual treatment review required" when the workflow does not establish precedential weight by itself.
- Search results are candidates, not filing-ready authorities, until verified.
- Re-run verification immediately before filing.
Output Standard
Format the final work product using references/OUTPUT-TEMPLATE.md.
Dependencies
Do not assume tools are installed. Check references/RUNTIME.md before running any script.
Pitfalls
- Verifying only the case name and not the reporter citation.
- Treating
legal.find()results as verified authorities. - Assuming related cases from
legal.similar()are citing references or direct history. - Skipping the full-text read after verification.
- Hiding uncertainty when the result is
multiple_matchesornot_found.
Related Skills
casemark/medical-records-gap-analysis
tools
VerifiedTrustedCommunity
Audits the complete in-scope medical-record universe in a litigation matter and produces an attorney-facing, Bates-cited analysis of treatment gaps, missing records or providers, baseline coverage, material billing or production mismatches, and complaint evolution. Use when asked to find missing medical records, analyze treatment gaps or first-care timing, identify absent providers, assess whether a production is complete, or prepare a records-request target list. Use medical-record-chronology instead when the primary request is a chronological clinical narrative.
40SKILL.mdUpdated Sep 3, 2026
casemark/private-placement-memo
development
VerifiedTrustedCommunity
Drafts a legally compliant Private Placement Memorandum for Regulation D offerings (Rule 506(b)/506(c)), covering full disclosure framework including risk factors, capitalization, securities terms, use of proceeds, and investor qualification requirements. Enforces SEC anti-fraud compliance under Section 10(b)/Rule 10b-5, blue sky law considerations, and accredited investor verification under Rule 501. Use this skill when drafting PPMs, offering memorandums, Reg D disclosure documents, or private offering circulars for issuers raising capital from sophisticated investors. Also trigger when the user mentions private placement disclosure, offering memorandum, Reg D fundraising, or accredited investor verification. Even if the user just says "PPM" or "draft our offering memo," use this skill.
40SKILL.mdUpdated Apr 17, 2026
casemark/privacy-law-updates
data-ai
VerifiedTrustedCommunity
Generates structured privacy and data protection law briefings across US, EU, UK, and other jurisdictions. Organizes by jurisdiction with compliance deadlines, enforcement actions, and legislative changes. Use when preparing privacy law briefings, compliance updates, regulatory change summaries, or data protection landscape reviews.
40SKILL.mdUpdated Apr 17, 2026
casemark/prior-art-summary
testing
VerifiedTrustedCommunity
Generates structured summaries of prior art references for patent prosecution, validity analysis, and freedom-to-operate assessments. Maps disclosures to claim elements with precise citations. Use when summarizing prior art, analyzing patent landscapes, mapping references to claims, or preparing office action responses.
40SKILL.mdUpdated Apr 17, 2026