patent-pipeline

Generate jurisdiction-formatted patent drafts from invention descriptions.

2|1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/raja21068/AutoResearch --skill patent-pipeline-raja21068
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: patent-pipeline
Source: https://github.com/raja21068/AutoResearch/tree/main/skills/aris/patent-pipeline
Command: npx skills add https://github.com/raja21068/AutoResearch --skill patent-pipeline-raja21068

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill turns an invention description into a complete, jurisdiction-formatted patent draft by enforcing an execution-grounded workflow (prior art search, novelty/claim checks, specification writing, and examiner-style review).

Core Features & Use Cases

  • End-to-end patent drafting pipeline: From invention structuring and claims drafting to specification and jurisdiction formatting.
  • Prior art and novelty assessment checkpoints: Produces a patentability outlook before claims/specification are finalized.
  • Claims-first support with examiner-style review: Runs structured review cycles to improve clarity, written description, enablement, and claim scope.
  • Jurisdiction coverage: Supports CN (CNIPA), US (USPTO), and EP (EPO), including invention and CN-only utility model modes.
  • Persistence for long drafting sessions: Saves phased progress to enable resuming after context compaction.

Quick Start

Use the skill on your invention by providing an invention description and the target jurisdiction, for example: Run patent-pipeline with the argument "your invention description — US".

Frequently Asked Questions about patent-pipeline

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

FAQPage Schema
How do I draft a patent application that meets USPTO formatting requirements?

Drafting a jurisdiction-ready patent application requires structuring your invention description, designing claims, writing specifications, and performing examiner-style review. The pipeline enforces prior art novelty checkpoints and produces formatted outputs for CN, US, and EP jurisdictions.

What is the process for conducting a prior art search before writing patent claims?

A prior art search assesses existing inventions to determine novelty before finalizing claims. This pipeline enforces mandatory prior art novelty checkpoints, producing a patentability outlook that must be satisfied before proceeding to claims hierarchy design and specification writing.

Can I draft a utility model patent for CNIPA using an automated drafting pipeline?

Yes, you can draft a CN-only utility model using this patent drafting pipeline. It supports CNIPA jurisdiction formatting alongside USPTO and EPO, applying prior art search, claims drafting, and examiner review checkpoints to utility models and invention patents.

How do I structure patent claims to survive examiner review?

To survive examiner review, patent claims require structured review cycles checking clarity, written description, enablement, and claim scope. This pipeline runs claims-first support with examiner-style review iterations to improve these specific aspects before final formatting.

Does patent drafting software work for European Patent Office applications?

Patent drafting software works for European Patent Office applications if it supports EPO jurisdiction formatting. This pipeline generates structured patent outputs tailored to EP requirements, alongside CN and US formats, after completing novelty assessment and specification checkpoints.

Why does my long patent drafting session lose context and progress?

Long patent drafting sessions lose progress due to context compaction without persistence. This pipeline saves phased progress to a state file, enabling you to resume prior art search, claims drafting, and specification writing workflows exactly where you left off.