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

Prior Art Summary

ASecurity

Generates structured summaries of prior art references for patent prosecution, validity analysis, and freedom-to-operate assessments. Maps disclosures to claim elements with precise citations. Use when summarizing prior art, analyzing patent landscapes, mapping references to claims, or preparing office action responses.

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

Works with

api

Security Analysis

A100/100

Scanned 9/20/2026

Install to Claude Code

$npx -y skills add lev-os/agents --skill prior-art-summary --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Prior Art Summary?

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

Security grade badge for Prior Art Summary
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/lev-os-prior-art-summary/badge)](https://www.skillsdirectory.com/skills/lev-os-prior-art-summary)

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

Download Zip
Files
SKILL.md
---
name: prior-art-summary
description: Generates structured summaries of prior art references for patent prosecution, validity analysis, and freedom-to-operate assessments. Maps disclosures to claim elements with precise citations. Use when summarizing prior art, analyzing patent landscapes, mapping references to claims, or preparing office action responses.
---

# Prior Art Summary

Synthesizes prior art references into structured summaries mapping disclosures to claim elements for rapid landscape assessment.

## Prerequisites

- **Prior art references** — patents, applications, publications, product docs, or public disclosures
- **Invention description** — claims or specification under analysis
- **Scope directive** — prosecution, validity/invalidity, or FTO

## Workflow

### 1. Executive Overview

Produce a table covering:

- Total references reviewed (count)
- Most material references (top 3-5 with one-line rationale)
- Key gaps (claim elements with no or weak coverage)
- Art type breakdown (patents / applications / publications / other)

### 2. Individual Reference Summaries

For each reference:

| Field | Content |
|-------|---------|
| Document ID | Patent/pub number, DOI, or identifier |
| Title | Full title |
| Date | Pub/issue date; note effective prior art date if different |
| Inventor(s)/Author(s) | Names |
| Technical field | CPC/IPC classes or subject domain |
| Assignee/Publisher | Entity |

Then include:

- **Disclosure summary** — 2-4 sentences on core technical contribution
- **Key features** — bulleted list with exact quoted language and precise citation (¶, col:line, page, figure)
- **Gaps** — what the reference does NOT disclose relative to the invention

### 3. Claim-Element Mapping

| Claim Element | Ref. 1 | Ref. 2 | Ref. 3 |
|--------------|--------|--------|--------|
| Element A | ¶[0032], Fig. 3 | — | p. 12 |
| Element B | — | Col. 4:15-22 | — |

Legend: `✓` full disclosure, `~` partial, `—` absent. Always include citation location.

### 4. Combination Analysis

For each potentially obvious combination:

- **References combined** — which refs
- **Motivation to combine** — analogous art rationale, explicit suggestions, design incentives
- **Missing elements** — what remains undisclosed even in combination

### 5. Timeline

Chronological list by effective date, noting critical date boundaries (priority, filing, publication dates).

## Guardrails

- **Cite precisely** — every factual assertion needs ¶, col:line, page, or figure number
- **No legal conclusions** — organize facts for attorney judgment; never state claims are anticipated or obvious
- **Analogous art** — flag references outside the immediate field with rationale for qualification
- **Prior art status** — note references whose qualification depends on date analysis (pre-AIA vs. AIA § 102) [VERIFY]
- **Foreign-language refs** — flag language, provide translated key passages, note if machine-translated
- **Figures** — describe depicted features with enough detail to be useful without viewing the original
- **Terminology** — define specialized terms on first use in brackets
- **Order by relevance** to claim elements; use chronological only if requested or analytically significant

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 →