skills/legal/amicus-brief/SKILL.md
Drafts and analyzes U.S. appellate amicus curiae briefs for non-parties with Rule 29/Rule 37 compliance, unique perspective development, and Bluebook-ready citations. Use when asked to draft or review an amicus brief, friend-of-the-court brief, non-party brief, or anything involving FRAP 29, Supreme Court Rule 37, or appellate amicus practice.
npx skillsauth add casemark/skills amicus-briefInstall 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.
Draft or evaluate U.S. appellate amicus briefs that add a distinct, rule-compliant perspective.
Gather before starting:
Select mode:
| Mode | Trigger | Output | |---|---|---| | Drafting | Creating a new brief | Full brief with all required sections | | Analysis | Reviewing an existing brief | Structured critique with compliance table |
- [ ] Confirm jurisdiction and rule set (federal, state, SCOTUS)
- [ ] Verify consent or prepare motion for leave
- [ ] Identify unique contribution — do not duplicate party arguments
- [ ] Build authority map: controlling precedent, persuasive precedent, statutes, secondary sources
- [ ] Integrate expertise or policy evidence with clear sourcing
- [ ] Draft sections in required order; verify word/page limits
- [ ] Add disclosure statements, certificates, and signatures
- [ ] Run compliance pass: Bluebook, formatting, service, ECF rules
| Section | Purpose | |---|---| | Interest | Establish legitimacy and why amicus perspective matters | | Summary | One page max — unique thesis and outcome requested | | Argument | 2–4 points, each tied to controlling law and practical impact | | Conclusion | Clear request for disposition or rule adoption |
[Cover / Caption]
TABLE OF CONTENTS
TABLE OF AUTHORITIES
STATEMENT OF INTEREST
[Amicus constituency, expertise, direct stake.]
CONSENT / LEAVE STATUS
[Consent or motion for leave.]
SUMMARY OF ARGUMENT
[Thesis and outcome sought.]
ARGUMENT
I. [Legal principle + unique perspective]
II. [Policy/technical evidence tied to law]
III. [Practical consequences or administrability]
CONCLUSION
[Requested disposition.]
DISCLOSURE OF AUTHORSHIP AND FUNDING
[FRAP 29(a)(4)(E) / SCOTUS Rule 37.6.]
CORPORATE DISCLOSURE STATEMENT
[If required.]
CERTIFICATE OF COMPLIANCE
[Word count method and total.]
CERTIFICATE OF SERVICE
[Method, date, recipients.]
- [ ] Identify distinct contribution; check for duplication of party arguments
- [ ] Assess credibility and fit of amicus interest
- [ ] Evaluate authority strength and citation accuracy
- [ ] Flag new issues not raised by parties
- [ ] Check rule compliance and formatting
- [ ] Summarize core arguments and policy impacts
Verify for the specific court:
| Requirement | Confirm | |---|---| | Consent or leave | Parties' consent filed or motion for leave prepared | | Timing | Filing deadline — often 7 days after supported party's principal brief [VERIFY] | | Length | Word/page limits for amicus briefs [VERIFY] | | Disclosure | Authorship and funding (FRAP 29(a)(4)(E); SCOTUS Rule 37.6) | | Corporate disclosure | Entity disclosure if required (FRAP 26.1 or local equivalent) | | Service | Proper service on all parties with proof | | Format | Font, spacing, margins, cover color, ECF requirements |
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.