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

Court Order Summaries

ASecurity

Generates structured summaries of court orders and decisions, extracting obligations, deadlines, monetary awards, injunctive relief, and procedural requirements into an action-oriented reference. Flags ambiguities for attorney review. Converts relative timeframes to calendar dates. Use when summarizing court orders, judgments, injunctions, consent decrees, or compliance orders.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill court-order-summaries --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Court Order Summaries?

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

Security grade badge for Court Order Summaries
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-court-order-summaries/badge)](https://www.skillsdirectory.com/skills/lev-os-court-order-summaries)

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

Download Zip
Files
SKILL.md
---
name: court-order-summaries
description: Generates structured summaries of court orders and decisions, extracting obligations, deadlines, monetary awards, injunctive relief, and procedural requirements into an action-oriented reference. Flags ambiguities for attorney review. Converts relative timeframes to calendar dates. Use when summarizing court orders, judgments, injunctions, consent decrees, or compliance orders.
---

# Court Order Summaries

Transforms a court order into a structured reference covering who must do what, by when, and with what consequences. Scoped to U.S. federal and state courts.

## Prerequisites

- Full text of the court order with entry date visible
- Identification of all named parties and roles
- Applicable court rules for computing time

## Quick Start

1. Identify the entry date and all named parties
2. Extract obligations, deadlines, and monetary awards into the output sections below
3. Convert every relative timeframe ("within 30 days") to a specific calendar date
4. Flag ambiguities — never resolve or gap-fill

## Output Structure

### 1. Executive Overview (2–3 sentences)

Core holding, most urgent deadline, primary obligated party. Flag anything requiring immediate action (TROs, preliminary injunctions, sub-10-day deadlines) here.

### 2. Parties & Roles

| Party | Role | Obligations Under This Order |
|-------|------|------------------------------|
| [Name] | Plaintiff / Defendant / Third Party | Brief description |

### 3. Deadlines & Required Actions

| Party | Action Required | Deadline (Date) | Order Ref. | Consequence if Missed |
|-------|----------------|-----------------|------------|----------------------|

- Convert relative timeframes to calendar dates from the entry date
- Account for weekends, court holidays, and time-computation rules
- Note stays or deadline suspensions pending appeal

### 4. Monetary Obligations

| Obligor | Obligee | Amount | Type | Due Date | Order Ref. |
|---------|---------|--------|------|----------|------------|

Type: judgment / sanction / fee / bond.

### 5. Injunctive & Equitable Relief

| Type | Party Bound | Conduct Required or Prohibited | Duration / Conditions | Order Ref. |
|------|------------|-------------------------------|----------------------|------------|

Types: mandatory injunction, prohibitory injunction.

### 6. Procedural & Ongoing Requirements

- Reporting obligations (frequency, recipient, format)
- Notice provisions
- Compliance certifications
- Court supervision or monitoring requirements

### 7. Findings & Future Proceedings

- Findings of fact or conclusions of law with precedential or preclusive effect
- Rights preserved or limited (appeal, modification, enforcement)
- Conditions precedent or contingent obligations

### 8. Ambiguities & Attorney Review Items

List provisions that are unclear, internally inconsistent, or require legal interpretation. Do not resolve ambiguities — flag them for attorney review.

## Pitfalls & Checks

- **Fidelity**: Reproduce deadlines and obligations verbatim or in direct paraphrase; never alter scope
- **No gap-filling**: If the order is silent on a consequence or procedure, state that explicitly — do not infer
- **Cite everything**: Every obligation, deadline, and finding must reference its ¶, page, or § number
- **Immediate flags first**: Anything actionable within 7 days must appear in the Executive Overview
- **Plain language**: Use accessible terms; retain legal terms of art with brief parenthetical context
- **Jurisdiction header**: Note the specific court and jurisdiction at the top of every summary

---

**Key changes made:**

- **Removed `tags`** — not part of the Agent Skills spec; discovery relies on `description` keywords
- **Tightened description** — same trigger guidance, fewer tokens
- **Added Quick Start** — gives the agent an immediate action sequence before the full output template
- **Removed decorative `---` dividers** between output subsections — unnecessary token cost
- **Removed emoji** (⚠) — per codebase convention
- **Compressed table annotations** — e.g., monetary type values moved to a single inline note instead of a verbose column header
- **Renamed "Guidelines" to "Pitfalls & Checks"** — aligns with best-practice body structure and signals actionable guardrails
- **Reduced from 96 lines to 72 lines** — well under the 500-line budget

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 →