Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsCommunityBlog
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

Back to skills

Request For Admissions

ASecurity

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.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
documentationgo

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill request-for-admissions --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Request For Admissions?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Request For Admissions
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-request-for-admissions/badge)](https://www.skillsdirectory.com/skills/lev-os-request-for-admissions)

More formats (shields.io, HTML) on the badges page.

Download Zip
Files
SKILL.md
---
name: request-for-admissions
description: 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.
---

# Request for Admissions

Drafts FRCP 36 / state-equivalent Requests for Admissions that narrow trial issues, establish uncontroverted facts, and authenticate documents.

## Prerequisites

Collect before drafting:

- **Pleadings** — complaint, answer, party names as captioned, docket number, court, judge
- **Case documents** — contracts, correspondence, medical records, invoices, photos for authentication
- **Prior discovery** — initial disclosures, interrogatory responses, document productions
- **Jurisdiction** — federal (FRCP 36) or state rule (e.g., CA CCP §2033.010, TX TRCP 198)
- **Local rules** — formatting, page limits, RFA number caps (many jurisdictions cap at 25–35)

## Quick Start

1. Extract key facts from uploaded documents (names, dates, amounts, exhibits)
2. Draft numbered requests in logical order: foundational facts → event facts → communications → damages → document authentication
3. Include response instructions with deemed-admitted warning
4. Add caption, signature block, and certificate of service

## Document Extraction

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 |

## Output Structure

### Caption & Header

```
[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]
```

### Introduction

- Identify parties by full legal name
- Cite governing rule (FRCP 36 or state equivalent with section number)
- State purpose: narrow issues, establish facts, authenticate documents

### Definitions

Include only when specialized terms appear repeatedly. Skip for straightforward cases.

### Numbered Requests

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:**

- One fact per request — never compound
- Frame affirmatively ("Admit that X occurred"), not negatively
- Use exact dates, names, amounts from case documents
- No ultimate legal conclusions ("Admit you were negligent")
- No double negatives or trick phrasing
- Attach documents as labeled exhibits for authentication requests

**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.

### Response Instructions

Include all of:

- **Response options:** admit, deny, or state in detail why party cannot truthfully admit or deny
- **Deadline:** 30 days after service (FRCP 36(a)(3)) or jurisdiction-specific period
- **Deemed-admitted warning:** failure to timely respond = matter deemed admitted under [cite rule]
- **Reasonable inquiry obligation:** lack of knowledge invalid unless reasonable inquiry made
- **Supplementation duty:** continuing obligation to correct responses
- **Objection requirements:** must state with specificity; objection does not excuse answering non-objected portions

### Signature Block

```
Dated: _______________

_________________________
[Attorney Name], [Bar No.]
[Firm Name]
[Address]
[Phone] | [Fax]
[Email]
Attorney for [Requesting Party]
```

### Certificate of Service

- Date and method of service (ECF, email, mail, personal delivery)
- Each party/counsel served with address or email
- Signature of certifying attorney

## Pitfalls & Checks

- **One fact per request** — compound requests invite partial denials
- **No legal conclusions** — "Admit you were negligent" is improper; stick to factual predicates
- **Number limits** — check local rules before exceeding 25 RFAs
- **Judicial vs. pleading admissions** — RFA admissions are binding judicial admissions, stronger than pleading admissions
- **Avoid harassing requests** — skip matters of public record, opinions, or facts solely within requesting party's knowledge
- **Verify exhibits** — all referenced exhibits must be properly labeled and attached
- **Verify rule citations** — confirm all citations are current for the specific jurisdiction [VERIFY]
- **Tone** — neutral, professional, firm; never argumentative

---

**Key changes made:**

- **Removed `tags` from frontmatter** — not part of the Agent Skills spec (only `name` and `description` are valid)
- **Trimmed description** — tightened wording while preserving all trigger keywords
- **Added Quick Start section** — gives the agent a fast 4-step overview before diving into details
- **Consolidated Prerequisites** — collapsed from numbered list to bullet list, merged formatting rules into local rules bullet
- **Flattened Output Structure headings** — removed redundant numbering (`### 1. Caption` → `### Caption & Header`)
- **Consolidated Guidelines into Pitfalls & Checks** — merged scattered guidance into a single scannable checklist at the end
- **Removed prose padding** — cut "Include all of the following", "Organize in logical progression" intros, and other filler phrases
- **Reduced line count** — from 124 lines to ~105 while preserving all substantive legal content

Attribution

lev-oslev-os
View sourceMore from lev-os →
SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Your tool, in front of Claude Code builders.

3 founder slots · $299/mo · GSC-verified traffic · sponsors can never buy grades.

See placements

Related Skills

Context Fundamentals

Understand the components, mechanics, and constraints of context in agent systems. Use when designing agent architectures, debugging context-related failures, or optimizing context usage.

179001 votes

release-notes

Draft release notes and changelog entries from git history or merged PRs between two refs (tags/SHAs/branches), including breaking changes, migrations, and upgrade steps. Use when the user asks for release notes, changelog updates, or a GitHub Release draft.

1301 votes

docs-style-guide

Documentation style guide enforcer by @planetabhi. Applies and reviews the writing style guide when authoring or editing product documentation and tutorials. Use to check prose for voice, tense, word choice, inclusive language, formatting, code block, UI, Markdown, and number/date conventions.

11 votes

Caveman Help

Quick-reference card for all caveman modes, skills, and commands. One-shot display, not a persistent mode. Trigger: /caveman-help, "caveman help", "what caveman commands", "how do I use caveman".

1023330 votes

How It Works

Explain how claude-mem captures observations, when memory injection kicks in, and where data lives. Use when the user asks "how does claude-mem work?" or "what is this thing doing?".

929660 votes
View all in documentation →