Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
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
  • Authors
  • 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
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Patent Summary

ASecurity

Generates structured, prosecution-ready summaries of patent applications covering bibliographic data, claims analysis, and strategic observations. Use when summarizing patent filings, preparing for prosecution, conducting portfolio review, licensing negotiations, or freedom-to-operate analysis.

15 stars
0 votes
0 copies
2 views
Added 6/7/2026
ai-agentsgogit

Security Analysis

A100/100

Scanned 6/7/2026

$npx -y skills add ThomasMoreAI/legal-skills-open --skill patent-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Patent Summary?

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

Security grade badge for Patent Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/thomasmoreai-patent-summary/badge)](https://www.skillsdirectory.com/skills/thomasmoreai-patent-summary)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: patent-summary
title: Patent Application Summary
description: Generates structured, prosecution-ready summaries of patent applications covering bibliographic data, claims analysis, and strategic observations. Use when summarizing patent filings, preparing for prosecution, conducting portfolio review, licensing negotiations, or freedom-to-operate analysis.
author: CaseMark
author_url: https://github.com/CaseMark/skills/tree/main/skills/legal/patent-summary
license: Apache-2.0
version: 0.1.0
execution_mode: open
jurisdiction: general
practice: ip
language: en
---

# Patent Application Summary

Produces a structured summary of a patent application for prosecution, licensing, litigation, or portfolio management. Requires the application document (specification, claims, abstract, drawings) and any priority/related filings.

## Quick Start

1. Gather the patent application and any related filings
2. Identify target audience (prosecution, licensing, litigation, portfolio)
3. Generate the summary following the output structure below
4. Flag prosecution risks and strategic observations
5. Review against checks at the bottom

## Output Structure

### 1. Executive Overview

Two to three sentences: invention essence, technical field, broadest claim scope.

### 2. Bibliographic Data

| Field | Extract |
|---|---|
| Application No. | — |
| Filing Date | — |
| Inventor(s) | — |
| Assignee | — |
| Priority Claims | — |
| Related Applications | — |
| Technical Field | — |

### 3. Background & Problem

- Problem the invention addresses
- Key prior art cited; how applicant distinguishes
- Novelty and non-obviousness positioning

### 4. Invention Description

- How it works — components, steps, or architecture
- Core innovations vs. prior art
- Key embodiments with practical applications
- Write accessibly for non-specialist attorneys; maintain technical precision

### 5. Drawings & Figures

| Figure | Description |
|---|---|
| Fig. N | — |

Summarize each referenced figure. Omit unreferenced figures.

### 6. Claims Analysis

| Claim | Type | Scope Summary |
|---|---|---|
| 1 | Independent | — |
| N | Independent | — |
| Key dependents | Dependent | — |

- **Total claims**: [count] — **Independent**: [count]
- **Format flags**: Note means-plus-function (§ 112(f)), Beauregard, or Jepson claims

### 7. Strategic Observations

**Scope & Strength**

- Claim breadth assessment
- Design-around vulnerabilities
- Commercially significant dependent claim narrowings

**Prosecution Risk Flags**

| Issue | Risk | Notes |
|---|---|---|
| Enablement (§ 112(a)) | Low/Med/High | — |
| Written Description | Low/Med/High | — |
| Indefiniteness (§ 112(b)) | Low/Med/High | — |
| Prior Art Overlap | Low/Med/High | — |

**Commercial & Portfolio**

- Licensing or FTO considerations
- Recommended next steps

## Checks

- Cite specific section headings, claim numbers, and figure references throughout
- Target 1–3 pages; balance comprehensiveness with conciseness
- Use precise IP terminology; keep descriptions accessible to non-specialist attorneys
- Flag potentially relevant uncited prior art with `[NOTE]`
- Do not opine on patentability — present observations only
- For continuations/divisionals, note parent filing relationship
- Default jurisdiction: U.S. (USPTO) unless specified otherwise

---

Shall I try writing this to the file again?

Attribution

ThomasMoreAIThomasMoreAI
View sourceSee grades on GitHubMore from ThomasMoreAI →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

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

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698621 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →