Claims Drafting: The Core Patent Skill
Unverified●36/40Claude Code●WorksValid SKILL.md that declares allowed-tools
Cursor·UnknownWe have not crawled the repo tree, so we will not guess
Codex·UnknownWe have not crawled the repo tree, so we will not guess
Gemini CLI·UnknownThe spec defines no detection rule for Gemini
Copilot·UnknownWe have not crawled the repo tree, so we will not guess
npx agentalley add claims-draftingWho is stuck, and on what
You've built or thought up something new and want to protect it, but the official patent wording is baffling and lawyers charge a fortune just for a first draft. You don't know how to describe your idea so it's broad enough to matter but tight enough to hold up.
What it gives you
A numbered set of formal patent claims (one broad main claim plus narrower backup claims) written in the required legal format for your chosen country.
When NOT to use it
It will not file your patent, run a legal search of existing patents, or replace sign-off from a licensed patent attorney before you submit.
The whole source
Frontmatter — 4 properties
| name | claims-drafting |
|---|---|
| description | Draft patent claims for an invention. Use when user says \"撰写权利要求\", \"draft claims\", \"写权利要求书\", \"claim drafting\", or wants to create patent claims. The core skill of the patent pipeline. |
| argument-hint | [invention-disclosure-path] |
| allowed-tools | Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-reply |
| 1 | --- |
| 2 | name: claims-drafting |
| 3 | description: "Draft patent claims for an invention. Use when user says \"撰写权利要求\", \"draft claims\", \"写权利要求书\", \"claim drafting\", or wants to create patent claims. The core skill of the patent pipeline." |
| 4 | argument-hint: "[invention-disclosure-path]" |
| 5 | allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-replyA4 — This skill pulls in web or user content but never says to treat that content as data. A signal, not proof. |
| 6 | --- |
| 7 | |
| 8 | # Claims Drafting: The Core Patent Skill |
| 9 | |
| 10 | Draft patent claims based on: **$ARGUMENTS** |
| 11 | |
| 12 | This is the most critical skill in the patent pipeline. Claims define the legal scope of protection -- everything else (specification, figures, abstract) exists to support and enable the claims. |
| 13 | |
| 14 | ## Constants |
| 15 | |
| 16 | - `REVIEWER_MODEL = gpt-6-astra` — External examiner for claim quality review |
| 17 | - `MAX_CLAIM_REVISION_ROUNDS = 3` — Maximum revision iterations |
| 18 | - `CLAIM_STYLE = "auto"` — `US` (Jepson or open), `EP` (two-part mandatory), `CN` (two-part), `auto` (detect from jurisdiction) |
| 19 | - `MIN_INDEPENDENT_CLAIMS = 2` — Typically method + system. For utility model (实用新型): apparatus/device only, NO method claims. |
| 20 | - `MAX_TOTAL_CLAIMS = 20` — Practical limit (USPTO includes 20 in base fee) |
| 21 | - `PATENT_TYPE = "invention"` — `invention` (发明专利) or `utility_model` (实用新型, apparatus claims only) |
| 22 | |
| 23 | ## Inputs |
| 24 | |
| 25 | 1. `patent/INVENTION_DISCLOSURE.md` — structured invention with core/supporting/optional features |
| 26 | 2. `patent/PRIOR_ART_REPORT.md` — prior art to avoid |
| 27 | 3. `patent/NOVELTY_ASSESSMENT.md` — novelty analysis with suggested amendments |
| 28 | 4. Target jurisdiction from invention disclosure or `$ARGUMENTS` |
| 29 | |
| 30 | ## Shared References |
| 31 | |
| 32 | Load `../shared-references/patent-writing-principles.md` for claim drafting principles, antecedent basis rules, and common pitfalls. |
| 33 | Load `../shared-references/patent-format-cn.md` for CN claim format (其特征在于). |
| 34 | Load `../shared-references/patent-format-us.md` for US claim format (comprising, means-plus-function). |
| 35 | Load `../shared-references/patent-format-ep.md` for EP two-part form (characterised in that). |
| 36 | |
| 37 | ## Workflow |
| 38 | |
| 39 | ### Step 1: Determine Claim Style and Patent Type |
| 40 | |
| 41 | Based on patent type and jurisdiction: |
| 42 | |
| 43 | **If `PATENT_TYPE = utility_model` (实用新型)**: |
| 44 | - CN jurisdiction ONLY |
| 45 | - Apparatus/device claims ONLY — no method, no product-by-process |
| 46 | - `MIN_INDEPENDENT_CLAIMS = 1` (single apparatus claim is sufficient) |
| 47 | - Claim format: "1. 一种[主题]，其特征在于，包括：[组件描述]。" |
| 48 | |
| 49 | Based on target jurisdiction: |
| 50 | |
| 51 | | Jurisdiction | Claim Style | Characterising Phrase | Preamble Format | |
| 52 | |-------------|------------|----------------------|-----------------| |
| 53 | | CN | Two-part (两部式) | 其特征在于 | 一种...的方法/装置，包括： | |
| 54 | | US | Open (preferred) | comprising | A method for..., comprising: | |
| 55 | | EP | Two-part (mandatory) | characterised in that | A method for..., comprising [known], characterised in that [inventive] | |
| 56 | | ALL | Draft CN + US + EP | All of the above | All of the above | |
| 57 | |
| 58 | ### Step 2: Draft Independent Claims |
| 59 | |
| 60 | **CRITICAL — Claims numbering (CN format):** |
| 61 | - Claims must be numbered 1, 2, 3, ... continuously without gaps |
| 62 | - Independent and dependent claims are INTERMIXED in final numbering |
| 63 | - Do NOT group independent claims separately from dependent claims |
| 64 | - Example correct: Claim 1 (independent, product), Claim 2 (depends on 1), Claim 3 (depends on 1), Claim 4 (independent, method), Claim 5 (depends on 4)... |
| 65 | - Example WRONG: Claim 1 (independent), Claim 5 (independent), Claim 8 (independent), then Claim 2, 3, 4, 6, 7, 9, 10 as dependents |
| 66 | |
| 67 | **CRITICAL — No empirical content in claims:** |
| 68 | - Claims describe ONLY structural features or method steps |
| 69 | - Do NOT include signal characteristics, detection principles, measurement results |
| 70 | - WRONG: "产生负脉冲信号" / "谐振频率下降" — these are results, not features |
| 71 | - RIGHT: "所述开口谐振环的开口处形成用于检测通过流体中颗粒物的间隙传感区域" |
| 72 | |
| 73 | For each claim category identified in INVENTION_DISCLOSURE.md: |
| 74 | |
| 75 | **Method Claim (broadest)**: |
| 76 | 1. Start with preamble identifying the category and purpose |
| 77 | 2. List the core inventive features (from the "Core Inventive Concept" section) |
| 78 | 3. Include enough known features for context (but not more than necessary) |
| 79 | 4. Use open transition ("comprising" / "包括") |
| 80 | 5. Each element should be separated by semicolons or on separate lines |
| 81 | 6. Apply jurisdiction-specific format: |
| 82 | - CN: 前序部分 + "其特征在于" + 特征部分 |
| 83 | - US: Preamble + "comprising:" + elements |
| 84 | - EP: Preamble + known features + "characterised in that" + inventive features |
| 85 | |
| 86 | **System/Apparatus Claim**: |
| 87 | 1. Mirror the method claim in structural form |
| 88 | 2. Each method step becomes a "module configured to..." or "component for..." |
| 89 | 3. Same hierarchy of known vs. inventive features |
| 90 | |
| 91 | **Quality checks for each independent claim**: |
| 92 | - [ ] Single sentence (US/EP) or properly structured (CN) |
| 93 | - [ ] Antecedent basis: "a" first, "the" thereafter for each element |
| 94 | - [ ] No relative terms without definition |
| 95 | - [ ] No result-to-be-achieved limitations |
| 96 | - [ ] Transitional phrase is appropriate (open preferred) |
| 97 | - [ ] Preamble does not import unnecessary limitations |
| 98 | - [ ] Each element is necessary for patentability |
| 99 | - [ ] Claim scope is broadest defensible over prior art |
| 100 | |
| 101 | ### Step 3: Draft Dependent Claims |
| 102 | |
| 103 | For each independent claim, draft 5-10 dependent claims that: |
| 104 | |
| 105 | 1. **Narrow the core inventive features**: Specific implementations, parameters, ranges |
| 106 | 2. **Cover preferred embodiments**: Features from the specification's detailed description |
| 107 | 3. **Provide fallback positions**: If the independent claim is rejected, these narrower claims may survive |
| 108 | 4. **Cover alternatives**: Different ways to achieve the same inventive result |
| 109 | |
| 110 | **Dependent claim format**: |
| 111 | - CN: "根据权利要求X所述的[主题]，其特征在于，所述[特征]具体为..." |
| 112 | - US: "The [method/system] of claim X, wherein the [element] comprises [limitation]." |
| 113 | - EP: "The [method/system] according to claim X, characterised in that [limitation]." |
| 114 | |
| 115 | **Rules for dependent claims**: |
| 116 | - Each must add at least one meaningful limitation |
| 117 | - Must reference a prior claim by number |
| 118 | - Must not merely repeat the parent claim |
| 119 | - Should not be cumulative (each claim should be independently useful as a fallback) |
| 120 | - Multiple dependent claims (US: only "or" references, not "and") |
| 121 | |
| 122 | ### Step 4: Claim-to-Specification Mapping |
| 123 | |
| 124 | Create a preliminary mapping to verify enablement: |
| 125 | |
| 126 | | Claim Element | Must be described in specification | Reference numeral | |
| 127 | |---------------|-----------------------------------|-------------------| |
| 128 | | [element 1] | Yes/No | [numeral] | |
| 129 | | [element 2] | Yes/No | [numeral] | |
| 130 | |
| 131 | If any element lacks specification support, add it to the specification requirements. |
| 132 | |
| 133 | ### Step 5: Cross-Model Examiner Review |
| 134 | |
| 135 | Call `REVIEWER_MODEL` via `mcp__codex__codex` with xhigh reasoning: |
| 136 | |
| 137 | ``` |
| 138 | mcp__codex__codex: |
| 139 | model: gpt-6-astra |
| 140 | config: {"model_reasoning_effort": "xhigh"} |
| 141 | prompt: | |
| 142 | You are a senior patent examiner at the [USPTO/CNIPA/EPO]. |
| 143 | Review the following patent claims for quality and patentability. |
| 144 | |
| 145 | CLAIMS: [all claims] |
| 146 | |
| 147 | PRIOR ART: [prior art references from PRIOR_ART_REPORT.md] |
| 148 | |
| 149 | INVENTION: [summary from INVENTION_DISCLOSURE.md] |
| 150 | |
| 151 | Analyze each claim for: |
| 152 | 1. Clarity (35 USC 112(b) / Art 84 EPC): Are terms definite? |
| 153 | 2. Written description support: Does the spec support all claim scope? |
| 154 | 3. Anticipation (102/Art 54): Would any single reference anticipate? |
| 155 | 4. Obviousness (103/Art 56): Would any combination render obvious? |
| 156 | 5. Claim scope: Are independent claims broad enough to be valuable? |
| 157 | 6. Dependent claims: Do they provide meaningful fallback positions? |
| 158 | 7. Antecedent basis: Any issues with "a"/"the" usage? |
| 159 | 8. Indefinite terms: Any functional/result language issues? |
| 160 | |
| 161 | For each issue found, provide: |
| 162 | - The specific claim number and element |
| 163 | - The problem (cite statute/rule) |
| 164 | - A suggested fix |
| 165 | |
| 166 | Provide an overall PATENTABILITY SCORE: 1-10. |
| 167 | ``` |
| 168 | |
| 169 | ### Step 6: Revision Loop |
| 170 | |
| 171 | If the examiner review identifies issues: |
| 172 | |
| 173 | 1. Address all CRITICAL issues (anticipation, obviousness, indefiniteness) |
| 174 | 2. Address MAJOR issues (scope too narrow, missing support, weak fallbacks) |
| 175 | 3. Consider MINOR issues (antecedent basis, formatting) |
| 176 | 4. Re-submit to examiner for round 2 (use `mcp__codex__codex` with threadId) |
| 177 | 5. Repeat up to `MAX_CLAIM_REVISION_ROUNDS` times |
| 178 | |
| 179 | ### Step 7: Output |
| 180 | |
| 181 | Write `patent/CLAIMS.md`: |
| 182 | |
| 183 | ```markdown |
| 184 | ## Patent Claims |
| 185 | |
| 186 | ### Independent Claims |
| 187 | |
| 188 | #### Claim 1 — Method |
| 189 | [formatted claim text] |
| 190 | |
| 191 | #### Claim X — System/Apparatus |
| 192 | [formatted claim text] |
| 193 | |
| 194 | ### Dependent Claims |
| 195 | |
| 196 | #### Claim 2 (depends on 1) |
| 197 | [formatted claim text] |
| 198 | |
| 199 | #### Claim 3 (depends on 1) |
| 200 | [formatted claim text] |
| 201 | ... |
| 202 | |
| 203 | ### Claims Summary Table |
| 204 | |
| 205 | | Claim | Type | Depends On | Key Limitation | Prior Art Avoidance | |
| 206 | |-------|------|-----------|----------------|---------------------| |
| 207 | | 1 | Method | — | [core inventive features] | [what makes it novel over prior art] | |
| 208 | | 2 | Method | 1 | [narrowing] | [additional distinguishing] | |
| 209 | | X | System | — | [mirrors claim 1] | [same as claim 1] | |
| 210 | ... |
| 211 | |
| 212 | ### Examiner Review Summary |
| 213 | [Key findings and how they were addressed] |
| 214 | ``` |
| 215 | |
| 216 | ## Key Rules |
| 217 | |
| 218 | - Claims are the single most important part of the patent. Everything else supports them. |
| 219 | - Draft independent claims first, then dependent claims. |
| 220 | - Independent claims must be broadest defensible scope over prior art -- not broader, not narrower. |
| 221 | - Each dependent claim should be independently useful as a fallback position. |
| 222 | - Antecedent basis is mandatory: "a processor" first, "the processor" thereafter. |
| 223 | - Use "comprising" (open) unless there is a specific reason for "consisting of" (closed). |
| 224 | - Never include result-to-be-achieved language in claims ("configured to achieve high accuracy"). |
| 225 | - Never fabricate claim language -- every element must come from the actual invention. |
| 226 | - If drafting for ALL jurisdictions, produce separate claim sets for CN, US, and EP. |
| 227 | - If `mcp__codex__codex` is not available, skip cross-model examiner review and note it in the output. |
| 228 |
Reviews
Installed this one?Write the first review and take the Trailblazer badge.
Alternatives
Structure Your Invention For A Patent FilingDescribe your invention in plain words and get back a formal write-up that lays out the problem it solves, how it works, and which parts are worth protecting.●····●37/40Patent Novelty and Non-Obviousness CheckDescribe your invention in everyday words and get back a clear read on whether it's new and original enough to patent, plus where it might hit trouble.●····●35/40Patent Pipeline: From Invention to FilingDescribe your invention in plain words and get back a complete first-draft patent application — claims, full description, and abstract — ready to hand to a patent attorney.●····●35/40Codebase ScannerScans the codebase to generate project-doc.md and AGENTS.md. Use when bootstrapping a new agent-driven repo, refreshing project documentation after architectural changes, or running a delta scan to detect drift. Runs a full scan on first use and a smart delta scan on subsequent runs. Uses understand-anything + context-mode when available, falls back to native tools otherwise. Only updates AGENTS.md on detected architectural changes with human confirmation.◐◐◐◐◐●33/40