patent-pipeline
Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents. Supports CN (CNIPA), US (USPTO), EP (EPO). Supports invention patents and utility models
Install / Use
npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill patent-pipelineInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
AutomationSupported Platforms
Our assessment of patent-pipeline
patent-pipeline scores 98/100 on our quality scale, 85th of 2,780 Automation skills we index (top 4%).
Its SKILL.md is 14 KB long, well organised into 28 sections with 15 code examples: a thorough specification that gives an agent plenty to work with.
With 19,197 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 2 days ago, so patent-pipeline is actively maintained.
- Our last check on 2026-11-14 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit â read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-09-28. Automated pattern scan on 2026-09-28. It catches known dangerous patterns, not every risk â read a skill before letting an agent act on it.
patent-pipeline compared with similar skills
All 4 of these similar skills score higher than patent-pipeline; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| patent-pipeline (this skill)by wanshuiyin | 98 | 19.2k | 2d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.8k | today | CLAUDE.md |
| CowAgentby zhayujie | 100 | 48.0k | today | CLAUDE.md |
Frequently asked questions
- How do I install patent-pipeline?
- Run
npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill patent-pipeline. The install tabs above show the steps for each supported agent. - Which AI agents does patent-pipeline work with?
- It is written for OpenAI Codex, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is patent-pipeline safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is patent-pipeline still maintained?
- The repository was last updated 2 days ago, so patent-pipeline is actively maintained.
Skill content
View source on GitHubname: patent-pipeline description: "Full patent drafting pipeline from invention description to jurisdiction-formatted filing documents. Supports CN (CNIPA), US (USPTO), EP (EPO). Supports invention patents and utility models. Use when user says "åä¸åŠ", "patent pipeline", "ä¸åŠįŗč¯ˇ", "draft patent", "åæåŠčĻæąäšĻ", or wants to draft a complete patent application." argument-hint: "[invention-description â jurisdiction]" allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, Skill, mcp__codex__codex
Patent Pipeline: From Invention to Filing
Draft a complete patent application based on: $ARGUMENTS
Overview
This skill orchestrates the full patent drafting lifecycle -- from prior art search through jurisdiction-formatted filing documents. It chains sub-skills into a patent-specific pipeline:
/prior-art-search â /patent-novelty-check â /invention-structuring â /claims-drafting â /specification-writing â /patent-review â /jurisdiction-format
(search) (verify) (structure) (claims) (description) (examiner) (compile)
âââ /figure-description
âââ /embodiment-description
This is a parallel branch, not part of the linear research pipeline. After /idea-discovery produces validated ideas, the user can either:
- Go to
/experiment-bridgeâ/auto-review-loopâ/paper-writing(publish track) - Go to
/grant-proposal(funding track) - Go to
/patent-pipeline(patent track) <-- this skill
ââ /experiment-bridge â /auto-review-loop â /paper-writing (publish track)
/idea-discovery âââââ¤
ââ /grant-proposal â [get funded] â ... (funding track)
ââ /patent-pipeline â [file patent] (patent track)
Patents are about protecting inventions (legal scope), not publishing results (academic contribution). This skill handles the unique requirements of patent drafting: prior art analysis, claims hierarchy design, specification writing with enablement support, embodiment descriptions, and jurisdiction-specific formatting.
Constants
- JURISDICTION =
CNâ Target patent jurisdiction. Options:CN(CNIPA),US(USPTO),EP(EPO),ALL(generate all three). Override via argument (e.g.,/patent-pipeline "invention â US"). - PATENT_TYPE =
inventionâinvention(åæä¸åŠ, 20 year protection) orutility_model(åŽį¨æ°å, CN only, 10 year protection, apparatus claims only). Override via argument. - REVIEWER_MODEL =
gpt-6-astraâ Model used via Codex MCP for examiner-style review. - MAX_REVIEW_ROUNDS = 2 â Maximum review-revision cycles.
- AUTO_PROCEED = false â At each checkpoint, always wait for explicit user confirmation. Patent applications require inventor judgment at every stage. Set
trueonly if user explicitly requests autonomous mode. - LANGUAGE =
autoâ Output language. Auto-detected from jurisdiction: CN->Chinese, US->English, EP->English. Override explicitly if needed. - OUTPUT_DIR =
patent/â Directory for generated patent files. - OUTPUT_FORMAT =
markdownâ Draft format.markdownfor review,docxfor filing-ready.
Override defaults via arguments:
/patent-pipeline "invention â US, utility model"or/patent-pipeline "invention â ALL, language: Chinese".
Patent Type Specifications
Invention Patent (åæä¸åŠ)
| Field | Detail | |-------|--------| | Protection | 20 years from filing date | | Subject matter | Methods, systems, products, compositions, processes | | Examination | Substantive examination required | | Inventive step | High (must involve an inventive step / åé æ§) | | Timeline | 2-4 years to grant (CN); 2-3 years (US); 3-5 years (EP) | | Claims | Method + system + product claims allowed |
Utility Model (åŽį¨æ°å) â CN Only
| Field | Detail | |-------|--------| | Protection | 10 years from filing date | | Subject matter | Product shape, structure, or combination thereof only | | Examination | Formal examination only (no substantive examination) | | Inventive step | Lower than invention patent | | Timeline | 6-8 months to grant | | Claims | Apparatus/device claims only. NO method claims. | | Restriction | CN jurisdiction only |
State Persistence (Compact Recovery)
Patent drafting is a long task that may trigger context compaction. Persist state to patent/PATENT_STATE.json after each phase:
{
"phase": 3,
"jurisdiction": "CN",
"patent_type": "invention",
"language": "Chinese",
"codex_thread_id": "019cfcf4-...",
"invention_title": "...",
"claims_count": 15,
"status": "in_progress",
"timestamp": "2026-04-10T15:00:00"
}
Write this file at the end of every phase. On invocation, check for this file:
- If absent or
status: "completed"-> fresh start - If
status: "in_progress"and within 24h -> resume from saved phase (read output files to restore context) - If older than 24h -> fresh start (stale state)
On completion, set "status": "completed".
Workflow
Phase 0: Input Parsing & Context Gathering
Parse $ARGUMENTS to extract:
- Invention description â may be structured (references INVENTION_BRIEF.md), conversational with figures, or output from IDEA_REPORT.md
- Jurisdiction â detect from keywords (e.g., "CN" or "ä¸åŊ" -> CN, "US" or "USPTO" -> US, "EP" or "EPO" -> EP, "ALL")
- Patent type â detect from keywords (e.g., "utility model" or "åŽį¨æ°å" -> utility_model, default -> invention)
- Overrides â language, output format, review rounds
Then gather context from the project directory:
- Read
INVENTION_BRIEF.mdif it exists (user filled in the template) - Read
IDEA_REPORT.mdif it exists (from/idea-discovery-- can extract invention from research results) - Read
refine-logs/FINAL_PROPOSAL.mdif it exists - Read
NARRATIVE_REPORT.mdif it exists (research results that may be patentable) - Search for user-provided figures (PNG, JPG, SVG, PDF) in the project directory
- Check for
patent/PATENT_STATE.json(resume from prior interrupted run)
If insufficient context exists:
- No invention description at all -> suggest user describe the invention or fill in
INVENTION_BRIEF.md - Has IDEA_REPORT.md -> extract patentable aspects from the research
- Has figures -> reference them in the invention brief
- No figures -> note that figures will be needed and plan what drawings are required
If the input is conversational (not a structured brief), parse the description into the invention brief structure and write patent/INVENTION_BRIEF.md for downstream phases.
Phase 1: Prior Art Search & Novelty Assessment
1.1 Prior Art Search
Invoke /prior-art-search:
/prior-art-search "patent/INVENTION_BRIEF.md"
This searches patent databases (Google Patents, Espacenet) and academic literature for relevant prior art.
1.2 Novelty Check
Invoke /patent-novelty-check:
/patent-novelty-check "patent/INVENTION_BRIEF.md"
This assesses novelty and non-obviousness against the prior art found in step 1.1.
đĻ Checkpoint: Present the prior art landscape and novelty assessment:
Prior art search complete:
- [X] patent references found
- [Y] non-patent literature references found
- Closest prior art: [reference] -- [why it's closest]
- Novelty assessment: [PATENTABLE / PATENTABLE WITH AMENDMENTS / NOT PATENTABLE]
- Key risk areas: [list]
Ready to proceed with invention structuring?
â STOP HERE and wait for user response. Do NOT auto-proceed unless AUTO_PROCEED=true.
Options:
- Reply "go" -> proceed to Phase 2
- Reply with adjustments -> refine the invention scope and re-check novelty
- Reply "stop" -> save progress to
patent/DRAFT_NOTES.md
State: Write PATENT_STATE.json with phase: 1.
Phase 2: Invention Structuring & Claims Design
2.1 Structure the Invention
Invoke /invention-structuring:
/invention-structuring "patent/INVENTION_BRIEF.md"
This decomposes the invention into core inventive concept, supporting features, and optional features. Produces patent/INVENTION_DISCLOSURE.md.
2.2 Draft Claims
Invoke /claims-drafting:
/claims-drafting "patent/INVENTION_DISCLOSURE.md"
This drafts the claims hierarchy -- the most critical part of the patent. Produces patent/CLAIMS.md.
đĻ Checkpoint: Present the invention structure and claims:
Invention structured:
- Core inventive concept: [summary]
- Claim categories: [method, system, etc.]
- Claims drafted: [X] independent + [Y] dependent = [Z] total
- Independent claim 1 (broadest): [first 50 words of claim 1]
- Examiner review score: [X]/10
The claims define the legal scope of protection. Please review before proceeding to specification.
â STOP HERE and wait for user response. Do NOT auto-proceed unless AUTO_PROCEED=true.
Options:
- Reply "go" -> proceed to Phase 3
- Reply with adjustments (e.g., "broaden claim 1", "add more dependent claims") -> revise claims
- Reply "stop" -> save progress
State: Write PATENT_STATE.json with phase: 2.
Phase 3: Specification Writing
Invoke /specification-writing:
/specification-writing "patent/CLAIMS.md"
This writes the full specification section by section. Internally invokes /figure-description (if user-provided figures exist) and /embodiment-description for the detailed description. The specification-writing skill handles figure processing and embodiment writing as sub-skills.
đĻ Checkpoint: Present the specification overview:
Specification written:
- Title: [title]
- Sections: Technical Field, Background, Summary, Drawings Description, Detailed Description, Abstract
- Embodiments: [X]
- Reference numerals: [Y] components mapped
- Abstract length: [Z] words (limit: [jurisdiction limit])
- Claim support: [all elements covered / X elements missing]
Ready to proceed to review?
â STOP HERE and wait for user response.
State: Write PATENT_STATE.json with phase: 3.
Phase 4: Patent Review
Invoke /patent-review:
/patent-review "patent/"
This runs 2 rounds of examiner-style review via GPT-6-Astra xhigh. The examiner evaluates clarity, written description, enablement, novelty, non-obviousness, and claim scope.
State: Write PATENT_STATE.json with phase: 4 and review score.
Phase 5: Jurisdiction Formatting & Output
Invoke /jurisdiction-format:
/jurisdiction-format "patent/"
This compiles the application into the target jurisdiction format(s).
Final Deliverables
| Output | Location | Description |
|--------|----------|-------------|
| CN: æåŠčĻæąäšĻ | patent/output/CN/ | Claims in CNIPA format |
| CN: 蝴æäšĻ | patent/output/CN/ | Description in CNIPA format |
| CN: 蝴æäšĻæčĻ | patent/output/CN/ | Abstract (CN) |
| US: Claims | patent/output/US/ | Claims in USPTO format |
| US: Specification | patent/output/US/ | Description in USPTO format |
| US: Abstract | patent/output/US/ | Abstract (US) |
| EP: Claims | patent/output/EP/ | Claims in EPO format |
| EP: Description | patent/output/EP/ | Description in EPO format |
| EP: Abstract | patent/output/EP/ | Abstract (EP) |
Final Report
## Patent Pipeline Complete
### Application Summary
- Title: [invention title]
- Jurisdiction: [CN/US/EP/ALL]
- Patent Type: [Invention / Utility Model]
- Language: [Chinese/English]
- Total Claims: [X] independent + [Y] dependent
### Pipeline Scores
| Phase | Score |
|-------|-------|
| Prior Art Search | [completeness assessment] |
| Novelty Assessment | [PATENTABLE/PATENTABLE WITH AMENDMENTS/NOT PATENTABLE] |
| Examiner Review Round 1 | [X]/10 |
| Examiner Review Round 2 | [Y]/10 |
| Fin
Truncated for display â read the full file on GitHub.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu â one CLI, zero API fees.
ruflo
81.9kđ The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.8kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
CowAgent
48.0kOpen-source personal AI assistant & Agent Harness. Plans tasks, runs tools and skills, self-evolves with memory and knowledge. Multi-agent, multi-model, multi-channel. Lightweight, extensible, one-line install.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit â see the Safety scan above for what the skill file itself contains.
