One-click install
npx skills add https://github.com/lgwanai/openforce --skill patent-application-creator-lgwanai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patent-application-creator
Source: https://github.com/lgwanai/openforce/tree/main/skills/patent-application-creator
Command: npx skills add https://github.com/lgwanai/openforce --skill patent-application-creator-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It eliminates the fragmented, time-consuming process of turning an invention disclosure into a complete, compliance-checked patent filing package by coordinating research, claims drafting, specification writing, diagram creation, and formalities validation.

Core Features & Use Cases

  • End-to-end patent workflow orchestration: guides users from invention disclosure through a complete filing package, including provisional/utility utility drafting workflows.
  • Prior art discovery and analysis: runs prior art search and produces a patentability-oriented research summary (including a structured prior art/IDS oriented output).
  • Claims + specification generation with validation loops: drafts independent and dependent claims, writes a detailed specification that supports claim elements, and performs compliance checking (35 USC 112 and formalities/MPEP guidance).
  • Diagram and abstract/front-matter production: generates patent figure sets, prepares a USPTO-compliant abstract, and assembles the final documents in filing-ready structure.

Quick Start

Use the patent-application-creator skill to draft a complete patent application from your invention disclosure, then ask it to produce the final USPTO-ready filing package and compliance report.

Frequently Asked Questions about patent-application-creator

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I draft a USPTO-ready patent application from an invention disclosure?

You can create a USPTO-ready patent application by transforming an invention disclosure into drafted claims, a written specification, figures, and an abstract. The workflow requires prior art analysis, claim dependency checking, specification support verification, and compliance validation for 35 USC 112 and MPEP formalities.

What is needed to ensure patent claims comply with 35 USC 112(a) and 112(b)?

Patent claims comply with 35 USC 112(a) and 112(b) through validation loops that check claim dependency and definiteness against a written specification. The specification must provide explicit support for all claim elements to meet USPTO formalities and avoid rejections during examination.

Can I generate patent figures and an abstract automatically during patent drafting?

Yes, you can generate patent figure sets and prepare a USPTO-compliant abstract automatically during patent drafting. The workflow produces front-matter and diagrams alongside the written specification, assembling them into a structured final document package suitable for submission.

How do I prepare an Information Disclosure Statement (IDS) and prior art for a utility patent?

To prepare an IDS and prior art for a utility patent, you run a prior art search and produce a patentability-oriented research summary. This structured output identifies relevant references early, which supports both IDS preparation and the overall compliance validation process.

Does this patent drafting workflow handle both provisional and utility patent applications?

Yes, this patent drafting workflow handles both provisional and utility-style patent preparation. It guides users from the initial invention disclosure through a complete filing package, applying the necessary research, claim drafting, and specification writing required for either application type.

What are the limitations of automated patent specification generation for USPTO submission?

Automated patent specification generation requires a complete invention disclosure to function properly and still requires human review for legal sufficiency. While it performs compliance checking against MPEP formalities and 35 USC 112, users should validate the final assembled documents before actual USPTO submission.