skills/legal/amicus-interest-statement/SKILL.md
Drafts the "Interest of Amicus Curiae" section of an amicus brief. Establishes institutional credibility, tethers the amicus's interest to the specific legal question, articulates non-party impacts, and embeds disclosure guardrails under FRAP 29 and Supreme Court Rule 37. Trigger when drafting amicus briefs, friend-of-the-court filings, interest statements, amicus disclosures, or when the user asks why an organization belongs in a case.
npx skillsauth add casemark/skills amicus-interest-statementInstall 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.
The Interest of Amicus Curiae section is the credibility gateway. Courts scrutinize amicus filings for "me-too" redundancy — a weak interest statement signals the brief wastes the court's time. This skill produces a statement that passes the clerk test: can someone explain in one sentence why this amicus belongs in this case?
Gather before drafting (skip only if user says "use defaults" or "just draft"):
Defaults when user doesn't respond: stakeholder advocate posture; FRAP 29 rules; disclosure withheld pending confirmation. Label all defaults. Request missing disclosure facts before finalizing.
Open by connecting the amicus to the specific question presented. Mirror the language of the questions presented.
Amicus curiae [Organization] submits this brief to assist the Court in resolving whether [legal issue]. Because [Organization] [work tied to issue], the Court's resolution will have significant consequences for [constituency] and for [system/market/program].
[Organization] is a [entity type] founded in [year] that represents [members/constituency] across [scope]. Its work includes [2-4 activities], including [activity relevant to the issue].
Select 2-3 expertise pillars from: operational experience with the statutory scheme, technical knowledge of the regulated subject, published research or data, professional standards, litigation pattern awareness.
Amicus has particular expertise relevant to the Court's analysis of [issue], including (1) [pillar], which informs how [rule] functions in practice; and (2) [pillar], which bears on [consequences] of adopting [proposed standard].
Translate doctrine into real-world effects via causal chains, not conjecture.
If the Court holds that [rule], then [mechanism], which would [consequence]. Because [Organization] works directly with [group], it has a concrete perspective on how [standard] will shape [behavior].
Neutral expertise posture:
Amicus does not file to support any party as such, but to assist the Court by providing [technical/historical/industry] context relevant to [provision].
Stakeholder advocate posture:
Amicus supports [party position] because the decision below threatens to [consequence] for [constituency], whom amicus serves through [programs].
Draft as though every sentence will be excerpted by opposing counsel.
Disclosure: Include only when user affirmatively confirms facts. Mark unconfirmed elements [VERIFY].
Pursuant to [Rule], amicus curiae states that no counsel for a party authored this brief in whole or in part, and no person or entity other than amicus curiae or its counsel made a monetary contribution intended to fund the preparation or submission of this brief.
Prefix every output with:
Keep the Interest Statement to 1-3 paragraphs.
| Forum | Rule | Key Requirement | |---|---|---| | U.S. Supreme Court | Rule 37.1 | Must bring matter not already presented by parties | | U.S. Supreme Court | Rule 37.6 | Authorship and funding disclosures | | Federal Circuits | FRAP 29(a)(4)(D) | Statement of amicus's interest | | Federal Circuits | FRAP 29(a)(4)(E) | Authorship and funding disclosures | | California | Rule 8.520(f) | Relationship to parties; identify other filings on same issue | | 7th Circuit | Local practice | Must demonstrate unique contribution | | State courts | Varies | Check local rules for motion-for-leave and extra-record restrictions |
All rule citations require verification against current text before filing. [VERIFY]
Ask after delivering the draft:
[VERIFY][VERIFY]development
name: automated-contract-summary language: en description: Generates structured executive summaries of contracts using ML — captures key terms, party obligations, risk allocations, and compliance requirements in a standardized format. Optimized for high-volume review where speed and consistency matter. tags: - summarization - agreement - corporate --- # Automated Contract Summarization Produces standardized executive summaries of contracts using machine learning, capturing essential term
tools
Extracts regulatory obligations from dense regulations across jurisdictions. Breaks down multi-level regulations into clear article-level obligations, classifies applicability to a business, and prioritizes by risk level. Use when translating regulations into actionable compliance requirements.
development
Continuously monitors regulatory landscapes for changes relevant to a specific business. Ingests global regulatory updates, filters by relevance, summarizes impact, and produces an actionable change advisory. Use when tracking regulatory developments affecting a particular product or market.
testing
Compares an organization's existing compliance controls, policies, and procedures against extracted regulatory obligations to identify coverage gaps. Produces a remediation plan with prioritized actions. Use when assessing compliance maturity or preparing for regulatory audits.