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

Appeal Document Summary

ASecurity

Produces structured U.S. appellate document summaries mapping procedural posture, issues on appeal, standards of review, and competing arguments into memo-ready format. Use when summarizing appellate briefs, notices of appeal, records on appeal, or preparing for oral argument. Triggers: appeal, appellate, notice of appeal, standard of review, cross-appeal, appellate brief intake, record on appeal synthesis.

22 stars
0 votes
0 copies
0 views
Added 9/20/2026
code-quality

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill appeal-document-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Appeal Document Summary?

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

Security grade badge for Appeal Document Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-appeal-document-summary/badge)](https://www.skillsdirectory.com/skills/lev-os-appeal-document-summary)

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

Download Zip
Files
SKILL.md
---
name: appeal-document-summary
description: >-
  Produces structured U.S. appellate document summaries mapping procedural
  posture, issues on appeal, standards of review, and competing arguments
  into memo-ready format. Use when summarizing appellate briefs, notices of
  appeal, records on appeal, or preparing for oral argument. Triggers:
  appeal, appellate, notice of appeal, standard of review, cross-appeal,
  appellate brief intake, record on appeal synthesis.
tags:
  - litigation
  - summarization
  - summary
---

# Appeal Document Summary

Generates a record-grounded, issue-driven appellate summary with standard-of-review analysis for each issue on appeal.

## Prerequisites

Collect before starting:

1. **Record set** — lower court orders/judgment, briefs, transcripts, docket, exhibits
2. **Party posture** — appellant/appellee, cross-appeals, consolidated matters
3. **Procedural timeline** — judgment date, notice of appeal, briefing schedule
4. **Jurisdictional context** — appellate court, originating court, applicable rules

## Quick Start

Build the memo in this order. Cite the record for every factual assertion or mark the gap explicitly.

1. Identify parties, courts, and appeal type
2. Map procedural posture and jurisdictional basis
3. List each issue on appeal with its standard of review
4. Summarize record-bound facts (disputed facts labeled)
5. Present each side's arguments with authorities
6. Assess dispositive issues and risk
7. Note related proceedings, pending motions, and deadlines
8. Flag research gaps and record supplement needs

## Memo Structure

### Section Outline

1. Case Caption and Courts — parties, originating court, appellate court, appeal type (as of right / discretionary / interlocutory)
2. Procedural Posture and Jurisdiction — judgment/order on appeal, notice of appeal date, timeliness, jurisdictional basis, preservation status
3. Issues on Appeal and Standards of Review — use Table 1
4. Factual Background (Record-Bound) — chronology, key record cites, disputed facts
5. Arguments and Authorities — appellant position, appellee position, conflicts or issues of first impression
6. Dispositive Issues and Risk Assessment — strongest/weakest points, standard-of-review sensitivity
7. Related Proceedings and Collateral Effects — prior appeals, parallel cases, preclusion risks, amicus/public interest
8. Pending Motions and Deadlines — motions, briefing schedule, oral argument date
9. Next Steps and Research Gaps — research tasks, record supplement needs

### Required Tables

**Table 1 — Issues and Standards**

| Issue | Appellant Claim of Error | Appellee Response | Standard of Review | Record Support | Dispositive? |
|-------|--------------------------|-------------------|--------------------|----------------|--------------|

**Table 2 — Key Orders and Rulings**

| Date | Court | Order/Ruling | Impact on Appeal | Record Cite |
|------|-------|--------------|------------------|-------------|

**Table 3 — Authorities Map**

| Issue | Primary Authorities | Opposing Authorities | Conflicts/Novelty |
|-------|---------------------|----------------------|-------------------|

**Table 4 — Record Gaps**

| Topic | Missing/Weak Record Support | Risk | Suggested Remedy |
|-------|----------------------------|------|------------------|

## Pitfalls and Checks

- **Record-binding**: Every fact must cite the record. If unsupported or disputed, label it — never infer facts not in the record.
- **Preservation**: Flag preservation defects and waiver risks in Section 2; these can be dispositive.
- **Jurisdictional defects**: Surface timeliness and jurisdictional issues early — they moot all other analysis.
- **Standard-of-review impact**: For each issue, state the standard and explain in one sentence how it affects the outcome.
- **Relief beyond record**: Note any requested relief that exceeds what the record or standard of review supports.
- **Tone**: Neutral and analytic — assess both sides without advocacy.

---

Key changes from the original:

- **Description** tightened — third-person, includes clear trigger keywords, removed redundant keyword list
- **Eliminated the full markdown template** — the section outline + tables convey the same structure at ~40% of the tokens. The template was largely a repetition of the outline with blank fields.
- **Collapsed "Narrative Rules" and "Guidelines" into "Pitfalls and Checks"** — single section, no repeated advice
- **Added "Quick Start"** — gives the core workflow as an ordered checklist per best practices
- **Overview sentence** kept to one line — Claude already knows what appellate summaries are
- **Total line count** dropped from ~123 to ~73 while preserving all domain-critical content (tables, section structure, record-binding rules, preservation/jurisdictional flags)

It looks like the file write permission was denied. Would you like to approve the write so I can save this to disk?

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

Caveman Review

Ultra-compressed code review comments. Cuts noise from PR feedback while preserving the actionable signal. Each comment is one line: location, problem, fix. Use when user says "review this PR", "code review", "review the diff", "/review", or invokes /caveman-review. Auto-triggers when reviewing pull requests.

1023331 votes

Caveman Commit

Ultra-compressed commit message generator. Cuts noise from commit messages while preserving intent and reasoning. Conventional Commits format. Subject ≤50 chars, body only when "why" isn't obvious. Use when user says "write a commit", "commit message", "generate commit", "/commit", or invokes /caveman-commit. Auto-triggers when staging changes.

1023331 votes

Springboot Verification

Verification loop for Spring Boot projects: build, static analysis, tests with coverage, security scans, and diff review before release or PR.

2456590 votes

Verification Loop

一个全面的 Claude Code 会话验证系统。

2456590 votes

Django Verification

Verification loop for Django projects: migrations, linting, tests with coverage, security scans, and deployment readiness checks before release or PR.

2456590 votes
View all in code-quality →