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

Maritime Case Summary

ASecurity

Produces structured summaries of maritime law cases covering admiralty jurisdiction, collisions, liens, salvage, cargo damage, charter parties, and personal injury aboard vessels. Extracts facts, legal issues, holdings, and practical implications using maritime-specific doctrines. Use when summarizing admiralty opinions, collision rulings, Jones Act claims, charter party disputes, or maritime lien enforcement.

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 maritime-case-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Maritime Case Summary?

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

Security grade badge for Maritime Case Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-maritime-case-summary/badge)](https://www.skillsdirectory.com/skills/lev-os-maritime-case-summary)

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

Download Zip
Files
SKILL.md
---
name: maritime-case-summary
description: Produces structured summaries of maritime law cases covering admiralty jurisdiction, collisions, liens, salvage, cargo damage, charter parties, and personal injury aboard vessels. Extracts facts, legal issues, holdings, and practical implications using maritime-specific doctrines. Use when summarizing admiralty opinions, collision rulings, Jones Act claims, charter party disputes, or maritime lien enforcement.
---

# Maritime Case Summary

Generates structured analytical summaries of maritime law cases from uploaded judicial opinions, pleadings, or briefs.

## Quick Start

1. Receive case materials (opinion, pleadings, or briefs)
2. Identify case type: collision/allision, cargo damage, personal injury, charter party, lien enforcement, salvage, limitation of liability, or jurisdictional challenge
3. Produce summary following the section order below

## Summary Sections

### 1. Case Caption & Citation

| Field | Content |
|-------|---------|
| Case name | Full caption |
| Citation | Bluebook format [VERIFY all citations] |
| Court | Including circuit/district |
| Date | Date of decision |
| Maritime subject | Primary area (e.g., collision, cargo, Jones Act) |

### 2. Procedural Posture

- Litigation stage and specific motion/appeal
- Admiralty vs. diversity jurisdiction (note significance)

### 3. Factual Background

- Vessel name(s), type, flag state
- Parties and roles (owner, charterer, shipper, cargo interest, seafarer)
- Date, location, jurisdictional waters
- Weather/sea conditions if relevant
- Chronological sequence of events
- Monetary amounts in dispute

### 4. Legal Issues

Frame each issue using maritime doctrine. Common categories:

| Domain | Key Questions |
|--------|--------------|
| Jurisdiction | Location test + nexus test; Extension of Admiralty Jurisdiction Act |
| Choice of law | General maritime law vs. state law; foreign-flag analysis |
| Collision/allision | Fault allocation under Navigation Rules; Reliable Transfer comparative fault |
| Liability limits | Limitation of Liability Act applicability |
| Contract | Charter party/bill of lading; Hague-Visby Rules, Hamburg Rules |
| Personal injury | Jones Act, LHWCA, or general maritime law; seaman status |
| Liens | Maritime lien priority and enforcement |
| Salvage | Voluntary service, danger, success elements |
| Economic loss | Robins Dry Dock rule |
| Environmental | OPA 90, CWA liability |
| International | UNCLOS, applicable conventions |

Summarize each party's position. Note circuit splits or novel questions.

### 5. Holding & Reasoning

- Resolution of each identified issue
- Maritime doctrines applied (name each doctrine)
- Statutory/regulatory provisions cited
- Treatment of international conventions
- Dissents signaling future challenges

### 6. Practical Implications

- Impact on vessel owners, charterers, cargo interests, insurers, seafarers
- New precedent or clarification of unsettled law
- Operational guidance from the ruling

## Terminology & Style Checks

- Use "vessel" not "boat"; "collision" (two moving vessels) vs. "allision" (vessel strikes fixed object)
- Distinguish "charterer" vs. "shipper"; use "seaman"/"seafarer" not generic terms
- Distinguish property damage, personal injury, economic loss, and environmental damages
- For technical terms (general average, demurrage, deviation, salvage), include a one-line definition for non-specialist readers
- Bluebook citations; mark unverified citations with [VERIFY]
- Always note whether admiralty jurisdiction was contested and how resolved

---

**Key changes made:**

- **Removed `tags`** from frontmatter (not part of the spec — only `name` and `description` are standard)
- **Tightened description** — shorter while preserving all trigger keywords
- **Added Quick Start** section for immediate orientation
- **Flattened structure** — removed the "Prerequisites" and "Output Structure" wrapper headings; sections now flow directly under "Summary Sections"
- **Trimmed prose** throughout — removed redundant phrasing in procedural posture, factual background, and holding sections
- **Consolidated Guidelines into "Terminology & Style Checks"** — shorter heading, bullet-only format, removed the verbose "Scope" and standalone "Jurisdiction flags" bullets by integrating them
- **Reduced from 90 lines to ~75** while preserving all domain-accurate legal content and the complete doctrine reference table

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 →