UI はローカライズ済みです。スキルの紹介と説明文書は選択した言語へ AI が自動翻訳し、コード・コマンド・パス・専門用語は原文のままです。原作者の文書が優先されます。
スキルを探す
データ・研究 · SKILL.md

patent-summary

patent-summary

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.

Independent GitHub snapshot · Automated classification · Original documentation governs

スキルの説明

GitHub

name: patent-summary language: en 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.

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

FieldExtract
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

FigureDescription
Fig. N—

Summarize each referenced figure. Omit unreferenced figures.

6. Claims Analysis

ClaimTypeScope Summary
1Independent—
NIndependent—
Key dependentsDependent—
  • 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

IssueRiskNotes
Enablement (§ 112(a))Low/Med/High—
Written DescriptionLow/Med/High—
Indefiniteness (§ 112(b))Low/Med/High—
Prior Art OverlapLow/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?

保存したスキル