skills/legal/request-for-admissions/SKILL.md
Drafts Requests for Admissions under FRCP 36 or state equivalents for personal injury litigation. Extracts facts from case documents to produce numbered admission requests covering factual matters, document authentication, and law-to-fact application. Use when drafting RFAs, narrowing trial issues, authenticating exhibits, or preparing discovery requests.
npx skillsauth add casemark/skills request-for-admissionsInstall 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.
Drafts FRCP 36 / state-equivalent Requests for Admissions that narrow trial issues, establish uncontroverted facts, and authenticate documents.
Collect before drafting:
Before drafting, extract from uploaded documents:
| Extract | Examples | |---|---| | Party names & roles | Full legal names as captioned | | Key dates & timeline | Incident, notice, treatment dates | | Monetary amounts | Medical bills, lost wages, demands | | Documents to authenticate | Contracts, letters, emails, records | | Admitted allegations | Facts already admitted in answer | | Communications | Emails, texts, letters with dates and participants |
[COURT NAME]
[CASE TITLE — all parties as captioned]
Case No. [DOCKET NUMBER]
[Judge / Track designation if required]
[REQUESTING PARTY]'S REQUEST FOR ADMISSIONS TO [RESPONDING PARTY]
Set No. [X]
Include only when specialized terms appear repeatedly. Skip for straightforward cases.
Organize in logical progression:
| Category | Order | Example | |---|---|---| | Foundational facts | First | Relationships, residence, employment, contract existence | | Event-specific facts | Second | Incident details, dates, locations, actions | | Communications | Third | Sending/receipt of documents on specific dates | | Damages | Fourth | Treatment, amounts billed, payment responsibility | | Document authentication | Last | Genuineness of attached exhibits |
Drafting rules:
Bad: "Admit that you received the notice on March 15 and failed to respond within thirty days." Good: Two separate requests — one for receipt, one for response timing.
Include all of:
Dated: _______________
_________________________
[Attorney Name], [Bar No.]
[Firm Name]
[Address]
[Phone] | [Fax]
[Email]
Attorney for [Requesting Party]
Key changes made:
tags from frontmatter — not part of the Agent Skills spec (only name and description are valid)### 1. Caption → ### Caption & Header)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.