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

Product Liability Summary

ASecurity

Generates structured summaries of product liability cases covering liability theories, outcomes, and strategic implications. Use when summarizing defective product litigation, manufacturing or design defect claims, failure to warn cases, breach of warranty disputes, or personal injury product cases.

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

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill product-liability-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Product Liability Summary?

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

Security grade badge for Product Liability Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-product-liability-summary/badge)](https://www.skillsdirectory.com/skills/lev-os-product-liability-summary)

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

Download Zip
Files
SKILL.md
---
name: product-liability-summary
description: Generates structured summaries of product liability cases covering liability theories, outcomes, and strategic implications. Use when summarizing defective product litigation, manufacturing or design defect claims, failure to warn cases, breach of warranty disputes, or personal injury product cases.
---

# Product Liability Case Summary

Compresses product liability litigation into a self-contained reference document with liability analysis, outcome details, and strategic takeaways for both sides.

## Prerequisites

- **Case materials** — court opinions, pleadings, expert reports, and/or settlement documents
- **Product identification** — product name, intended use, and alleged defect

## Quick Start

1. Gather case materials and identify the product and defect at issue
2. Build the case overview table (caption, court, dates, parties, posture)
3. Describe the product, standards, and warnings
4. Analyze each liability theory and catalog defenses
5. Document the outcome (verdict, settlement, or appellate decision)
6. Extract strategic implications for both sides

## Output Sections

### 1. Case Overview

| Field | Content |
|-------|---------|
| Case name | Full caption |
| Court / Jurisdiction | Court, state/federal, district |
| Case number | Docket number |
| Key dates | Filing, trial, verdict/settlement, appeal |
| Parties | Plaintiff(s) and Defendant(s) with roles |
| Procedural posture | Current status / final disposition |

### 2. Product Description

- Product name, manufacturer, model/version
- Intended use and design features
- Manufacturing process (if relevant to defect theory)
- Applicable safety standards (CPSC, ASTM, UL, FDA, etc.)
- Warnings and instructions provided to consumers

### 3. Liability Analysis

**Theories** — complete for each that applies:

| Theory | Alleged facts | Legal standard | Elements met/failed |
|--------|--------------|----------------|---------------------|
| Design defect | | Consumer expectation / risk-utility | |
| Manufacturing defect | | Departure from specifications | |
| Failure to warn | | Adequacy of warnings | |
| Breach of warranty | | Express / implied / Magnuson-Moss | |
| Strict liability | | Restatement (Second) §402A / (Third) | |

**Defenses** — check all raised: assumption of risk, product misuse, comparative/contributory negligence, regulatory compliance/preemption, statute of limitations/repose, sophisticated user/bulk supplier, state of the art.

**Expert testimony** — summarize key experts on causation, alternative design, and industry standards.

### 4. Outcome

- **Verdict**: liability finding per theory, compensatory damages (economic/non-economic), punitive damages (amount, ratio, reprehensibility)
- **Settlement**: amount (if disclosed), non-monetary terms (recalls, design changes, enhanced warnings)
- **Appellate**: issues reviewed, standard of review, holdings vs. dicta, significant rulings

### 5. Strategic Implications

- **Defendants/manufacturers**: design takeaways, warning obligations, QC practices, regulatory gaps, insurance considerations, similar-product risk
- **Plaintiffs/consumers**: burden of proof lessons, recovery benchmarks, litigation challenges, precedential value
- **Doctrinal significance**: flag new tests adopted, liability expansion/limitation, novel application to emerging technology

## Pitfalls and Checks

- Distinguish holdings from dicta from practical observations
- Use jurisdiction-specific standards (e.g., California Barker risk-utility test vs. Restatement approaches)
- Note split of authority across jurisdictions where relevant
- Tag unsourced citations with `[VERIFY]`
- Present both sides' strongest arguments — maintain neutrality
- Include enough standard explanation for readers unfamiliar with the specific jurisdiction

---

**Key changes made:**

- **Removed `tags`** from frontmatter (not part of the spec — only `name` and `description` are valid)
- **Trimmed description** to be more concise while preserving all trigger keywords
- **Added Quick Start** section with the core 6-step workflow
- **Consolidated Outcome** from three separate sub-headed blocks into a compact bullet format
- **Consolidated Strategic Implications** from three verbose sub-sections into dense inline lists
- **Collapsed Defenses** from a checkbox list into a single inline sentence (agent fills in what applies)
- **Renamed "Guidelines" to "Pitfalls and Checks"** per best-practice section naming
- **Reduced from 109 lines to 78** — meaningful token savings while preserving every legal concept and structural element

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 →