Describe your invention in plain words and get back

Claims Drafting: The Core Patent Skill

by wanshuiyin · MIT license · ★ 16,473 on GitHub · updated Sep 18

Claims Drafting: The Core Patent Skill cover

Describe your invention in plain words and get back a numbered set of formal patent claims — the legal wording that defines exactly what you own.

---
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
---

# Claims Drafting: The Core Patent Skill

Draft patent claims based on: **$ARGUMENTS**

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.

## Constants

- `REVIEWER_MODEL = gpt-6-astra` — External examiner for claim quality review
- `MAX_CLAIM_REVISION_ROUNDS = 3` — Maximum revision iterations
- `CLAIM_STYLE = "auto"` — `US` (Jepson or open), `EP` (two-part mandatory), `CN` (two-part), `auto` (detect from jurisdiction)

Overview

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.

Manual install (npx, ZIP)
Claude Codenpx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill claims-drafting -g -a claude-code
Claude Code (manual)mkdir -p ~/.claude/skills && curl -sL https://codeload.github.com/wanshuiyin/Auto-claude-code-research-in-sleep/tar.gz/f1bd907b58f6 \ | tar -xz -C ~/.claude/skills --strip-components=2 Auto-claude-code-research-in-sleep-f1bd907b58f6/skills/claims-drafting
Windows (PowerShell)New-Item -ItemType Directory -Force "$HOME\.claude\skills" | Out-Null; Invoke-WebRequest "https://m.agentalley.io/zip/472492214172380cc6c4/claims-drafting.zip" -OutFile "$env:TEMP\claims-drafting.zip"; Expand-Archive "$env:TEMP\claims-drafting.zip" -DestinationPath "$HOME\.claude\skills" -Force
Claude.ai / desktopDownload the ZIP and upload it under Settings → Capabilities → Skills.
Codex, Cursor, other agentsPoint them at SKILL.md. The other files are plain text.

Connects with Agent Alley MCP · agentalley.io/mcp

Files included

  • SKILL.md9.9 KB
Read the files here
wanshuiyin/f1bd9071 file
SKILL.md
Show the full text228 lines

Claims Drafting: The Core Patent Skill

Draft patent claims based on: $ARGUMENTS

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.

Constants

  • REVIEWER_MODEL = gpt-6-astra — External examiner for claim quality review
  • MAX_CLAIM_REVISION_ROUNDS = 3 — Maximum revision iterations
  • CLAIM_STYLE = "auto" — US (Jepson or open), EP (two-part mandatory), CN (two-part), auto (detect from jurisdiction)
  • MIN_INDEPENDENT_CLAIMS = 2 — Typically method + system. For utility model (实用新型): apparatus/device only, NO method claims.
  • MAX_TOTAL_CLAIMS = 20 — Practical limit (USPTO includes 20 in base fee)
  • PATENT_TYPE = "invention" — invention (发明专利) or utility_model (实用新型, apparatus claims only)

Inputs

  1. patent/INVENTION_DISCLOSURE.md — structured invention with core/supporting/optional features
  2. patent/PRIOR_ART_REPORT.md — prior art to avoid
  3. patent/NOVELTY_ASSESSMENT.md — novelty analysis with suggested amendments
  4. Target jurisdiction from invention disclosure or $ARGUMENTS

Shared References

Load ../shared-references/patent-writing-principles.md for claim drafting principles, antecedent basis rules, and common pitfalls. Load ../shared-references/patent-format-cn.md for CN claim format (其特征在于). Load ../shared-references/patent-format-us.md for US claim format (comprising, means-plus-function). Load ../shared-references/patent-format-ep.md for EP two-part form (characterised in that).

Workflow

Step 1: Determine Claim Style and Patent Type

Based on patent type and jurisdiction:

If PATENT_TYPE = utility_model (实用新型):

  • CN jurisdiction ONLY
  • Apparatus/device claims ONLY — no method, no product-by-process
  • MIN_INDEPENDENT_CLAIMS = 1 (single apparatus claim is sufficient)
  • Claim format: "1. 一种[主题],其特征在于,包括:[组件描述]。"

Based on target jurisdiction:

Jurisdiction Claim Style Characterising Phrase Preamble Format
CN Two-part (两部式) 其特征在于 一种...的方法/装置,包括:
US Open (preferred) comprising A method for..., comprising:
EP Two-part (mandatory) characterised in that A method for..., comprising [known], characterised in that [inventive]
ALL Draft CN + US + EP All of the above All of the above
Step 2: Draft Independent Claims

CRITICAL — Claims numbering (CN format):

  • Claims must be numbered 1, 2, 3, ... continuously without gaps
  • Independent and dependent claims are INTERMIXED in final numbering
  • Do NOT group independent claims separately from dependent claims
  • 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)...
  • Example WRONG: Claim 1 (independent), Claim 5 (independent), Claim 8 (independent), then Claim 2, 3, 4, 6, 7, 9, 10 as dependents

CRITICAL — No empirical content in claims:

  • Claims describe ONLY structural features or method steps
  • Do NOT include signal characteristics, detection principles, measurement results
  • WRONG: "产生负脉冲信号" / "谐振频率下降" — these are results, not features
  • RIGHT: "所述开口谐振环的开口处形成用于检测通过流体中颗粒物的间隙传感区域"

For each claim category identified in INVENTION_DISCLOSURE.md:

Method Claim (broadest):

  1. Start with preamble identifying the category and purpose
  2. List the core inventive features (from the "Core Inventive Concept" section)
  3. Include enough known features for context (but not more than necessary)
  4. Use open transition ("comprising" / "包括")
  5. Each element should be separated by semicolons or on separate lines
  6. Apply jurisdiction-specific format:
    • CN: 前序部分 + "其特征在于" + 特征部分
    • US: Preamble + "comprising:" + elements
    • EP: Preamble + known features + "characterised in that" + inventive features

System/Apparatus Claim:

  1. Mirror the method claim in structural form
  2. Each method step becomes a "module configured to..." or "component for..."
  3. Same hierarchy of known vs. inventive features

Quality checks for each independent claim:

  • Single sentence (US/EP) or properly structured (CN)
  • Antecedent basis: "a" first, "the" thereafter for each element
  • No relative terms without definition
  • No result-to-be-achieved limitations
  • Transitional phrase is appropriate (open preferred)
  • Preamble does not import unnecessary limitations
  • Each element is necessary for patentability
  • Claim scope is broadest defensible over prior art
Step 3: Draft Dependent Claims

For each independent claim, draft 5-10 dependent claims that:

  1. Narrow the core inventive features: Specific implementations, parameters, ranges
  2. Cover preferred embodiments: Features from the specification's detailed description
  3. Provide fallback positions: If the independent claim is rejected, these narrower claims may survive
  4. Cover alternatives: Different ways to achieve the same inventive result

Dependent claim format:

  • CN: "根据权利要求X所述的[主题],其特征在于,所述[特征]具体为..."
  • US: "The [method/system] of claim X, wherein the [element] comprises [limitation]."
  • EP: "The [method/system] according to claim X, characterised in that [limitation]."

Rules for dependent claims:

  • Each must add at least one meaningful limitation
  • Must reference a prior claim by number
  • Must not merely repeat the parent claim
  • Should not be cumulative (each claim should be independently useful as a fallback)
  • Multiple dependent claims (US: only "or" references, not "and")
Step 4: Claim-to-Specification Mapping

Create a preliminary mapping to verify enablement:

Claim Element Must be described in specification Reference numeral
[element 1] Yes/No [numeral]
[element 2] Yes/No [numeral]

If any element lacks specification support, add it to the specification requirements.

Step 5: Cross-Model Examiner Review

Call REVIEWER_MODEL via mcp__codex__codex with xhigh reasoning:

mcp__codex__codex:
  model: gpt-6-astra
  config: {"model_reasoning_effort": "xhigh"}
  prompt: |
    You are a senior patent examiner at the [USPTO/CNIPA/EPO].
    Review the following patent claims for quality and patentability.

    CLAIMS: [all claims]

    PRIOR ART: [prior art references from PRIOR_ART_REPORT.md]

    INVENTION: [summary from INVENTION_DISCLOSURE.md]

    Analyze each claim for:
    1. Clarity (35 USC 112(b) / Art 84 EPC): Are terms definite?
    2. Written description support: Does the spec support all claim scope?
    3. Anticipation (102/Art 54): Would any single reference anticipate?
    4. Obviousness (103/Art 56): Would any combination render obvious?
    5. Claim scope: Are independent claims broad enough to be valuable?
    6. Dependent claims: Do they provide meaningful fallback positions?
    7. Antecedent basis: Any issues with "a"/"the" usage?
    8. Indefinite terms: Any functional/result language issues?

    For each issue found, provide:
    - The specific claim number and element
    - The problem (cite statute/rule)
    - A suggested fix

    Provide an overall PATENTABILITY SCORE: 1-10.
Step 6: Revision Loop

If the examiner review identifies issues:

  1. Address all CRITICAL issues (anticipation, obviousness, indefiniteness)
  2. Address MAJOR issues (scope too narrow, missing support, weak fallbacks)
  3. Consider MINOR issues (antecedent basis, formatting)
  4. Re-submit to examiner for round 2 (use mcp__codex__codex with threadId)
  5. Repeat up to MAX_CLAIM_REVISION_ROUNDS times
Step 7: Output

Write patent/CLAIMS.md:

## Patent Claims

### Independent Claims

#### Claim 1 — Method
[formatted claim text]

#### Claim X — System/Apparatus
[formatted claim text]

### Dependent Claims

#### Claim 2 (depends on 1)
[formatted claim text]

#### Claim 3 (depends on 1)
[formatted claim text]
...

### Claims Summary Table

| Claim | Type | Depends On | Key Limitation | Prior Art Avoidance |
|-------|------|-----------|----------------|---------------------|
| 1 | Method | — | [core inventive features] | [what makes it novel over prior art] |
| 2 | Method | 1 | [narrowing] | [additional distinguishing] |
| X | System | — | [mirrors claim 1] | [same as claim 1] |
...

### Examiner Review Summary
[Key findings and how they were addressed]

Key Rules

  • Claims are the single most important part of the patent. Everything else supports them.
  • Draft independent claims first, then dependent claims.
  • Independent claims must be broadest defensible scope over prior art -- not broader, not narrower.
  • Each dependent claim should be independently useful as a fallback position.
  • Antecedent basis is mandatory: "a processor" first, "the processor" thereafter.
  • Use "comprising" (open) unless there is a specific reason for "consisting of" (closed).
  • Never include result-to-be-achieved language in claims ("configured to achieve high accuracy").
  • Never fabricate claim language -- every element must come from the actual invention.
  • If drafting for ALL jurisdictions, produce separate claim sets for CN, US, and EP.
  • If mcp__codex__codex is not available, skip cross-model examiner review and note it in the output.
1---
2name: claims-drafting
3description: "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."
4argument-hint: "[invention-disclosure-path]"
5allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch, mcp__codex__codex, mcp__codex__codex-reply
6---
7 
8# Claims Drafting: The Core Patent Skill
9 
10Draft patent claims based on: **$ARGUMENTS**
11 
12This 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 
251. `patent/INVENTION_DISCLOSURE.md` — structured invention with core/supporting/optional features
262. `patent/PRIOR_ART_REPORT.md` — prior art to avoid
273. `patent/NOVELTY_ASSESSMENT.md` — novelty analysis with suggested amendments
284. Target jurisdiction from invention disclosure or `$ARGUMENTS`
29 
30## Shared References
31 
32Load `../shared-references/patent-writing-principles.md` for claim drafting principles, antecedent basis rules, and common pitfalls.
33Load `../shared-references/patent-format-cn.md` for CN claim format (其特征在于).
34Load `../shared-references/patent-format-us.md` for US claim format (comprising, means-plus-function).
35Load `../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 
41Based 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 
49Based 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 
73For each claim category identified in INVENTION_DISCLOSURE.md:
74 
75**Method Claim (broadest)**:
761. Start with preamble identifying the category and purpose
772. List the core inventive features (from the "Core Inventive Concept" section)
783. Include enough known features for context (but not more than necessary)
794. Use open transition ("comprising" / "包括")
805. Each element should be separated by semicolons or on separate lines
816. 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**:
871. Mirror the method claim in structural form
882. Each method step becomes a "module configured to..." or "component for..."
893. 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 
103For each independent claim, draft 5-10 dependent claims that:
104 
1051. **Narrow the core inventive features**: Specific implementations, parameters, ranges
1062. **Cover preferred embodiments**: Features from the specification's detailed description
1073. **Provide fallback positions**: If the independent claim is rejected, these narrower claims may survive
1084. **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 
124Create 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 
131If any element lacks specification support, add it to the specification requirements.
132 
133### Step 5: Cross-Model Examiner Review
134 
135Call `REVIEWER_MODEL` via `mcp__codex__codex` with xhigh reasoning:
136 
137```
138mcp__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 
171If the examiner review identifies issues:
172 
1731. Address all CRITICAL issues (anticipation, obviousness, indefiniteness)
1742. Address MAJOR issues (scope too narrow, missing support, weak fallbacks)
1753. Consider MINOR issues (antecedent basis, formatting)
1764. Re-submit to examiner for round 2 (use `mcp__codex__codex` with threadId)
1775. Repeat up to `MAX_CLAIM_REVISION_ROUNDS` times
178 
179### Step 7: Output
180 
181Write `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 
View all files on GitHub →

Details

Updated
Sep 18, 2026
License
MIT
Stars on the repo
★ 16,473
Checked
Source
wanshuiyin/Auto-claude-code-research-in-sleep ↗
Creator
wanshuiyin · 7 listings
View creator

Made with claims-drafting

Claims Drafting: The Core Patent Skill — ARIS-Movie-Director frame — the evaluator-integrity audit page (from the wanshuiyin/Auto-claude-code-research-in-sleep README)
Claims Drafting: The Core Patent Skill — ARIS-Movie-Director frame — the evaluator-integrity audit page (from the wanshuiyin/Auto-claude-code-research-in-sleep README)

by wanshuiyin

Claims Drafting: The Core Patent Skill — ARIS-Movie-Director frame — a multi-panel scene (from the wanshuiyin/Auto-claude-code-research-in-sleep README)
Claims Drafting: The Core Patent Skill — ARIS-Movie-Director frame — a multi-panel scene (from the wanshuiyin/Auto-claude-code-research-in-sleep README)

by wanshuiyin

Claims Drafting: The Core Patent Skill — ARIS-Movie-Director frame — the integrity beat (reported +6.2, really moved +1.4) (from the wanshuiyin/Auto-claude-code-research-in-sleep README)
Claims Drafting: The Core Patent Skill — ARIS-Movie-Director frame — the integrity beat (reported +6.2, really moved +1.4) (from the wanshuiyin/Auto-claude-code-research-in-sleep README)

by wanshuiyin

Similar skills

See all →
SkillDescribe your invention in everyday words and get backPatent Novelty and Non-Obviousness Checkwanshuiyin/Auto-claude-code-research-in-sleep · by wanshuiyinDescribe 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.★ 16.5k GitHub starsPromptAny invention or product photo can be paired with the promptVintage invention patentf/prompts.chat · by magejoshAny invention or product photo can be paired with the prompt if desired specific form is required. I just used the text "Apple Vision Pro" for the invention with no uploaded pic for the example image here.New listingSkillGenerate patent-office-compliant figuresPatentfigdavila7/claude-code-templates · by davila7Generate patent-office-compliant figures via the PatentFig AI API — patent line art from text (PNG or SVG), vectorize drawings to SVG/DXF/vector PDF, AI-upscale images, and convert to filing-ready TIFF/PDF/PNG. Use when the user asks for patent drawings, patent figures, invention diagrams, USPTO/EPO-compliant line art, vectorizing a drawing for CAD, or preparing figures for a patent filing. Requires a PATENTFIG_API_KEY environment variable.★ 32.3k GitHub starsMCPPatent prior-art + landscape intelligence personaCs patentalirezarezvani/claude-skills · by alirezarezvaniPatent prior-art + landscape intelligence persona. Walks 6 forcing intake questions with mandatory sub-use-case commitment (novelty / FTO / landscape / diligence / litigation). Refuses to start without a sub-use-case picked. Refuses generic "patent help" requests. Searches Google Patents + Espacenet + USPTO + optional Lens.org sequentially at 1 q/sec. Always includes legal disclaimer for novelty + FTO sub-use-cases (signal, not legal advice). Family-resolves duplicates across jurisdictions. Outputs 8-section .docx with verdict + audit log.★ 26.3k GitHub starsSkillPatent prior-art and landscape intelligence skillPatent — Prior-Art + Landscape Intelligencealirezarezvani/claude-skills · by alirezarezvaniPatent prior-art and landscape intelligence skill — not generic patent help. Commits to one of five sub-use-cases via forcing intake (novelty search / freedom-to-operate / competitive landscape / acquisition diligence / litigation prior-art) before any search runs. Searches Google Patents, Espacenet, USPTO, and optionally Lens.org for citation-graph signals. Output is an editable Word document (.docx) with verdict, ranked closest art (claim-text extracted), CPC-class-aware landscape, family-resolved hits, geographic coverage, FTO flags where applicable, strategy recommendations, and full audit log. Use when the user asks for patent searching or analysis (e.g., 'prior art search for [invention]', 'freedom to operate analysis for [product]'). Produces search signal, not legal advice — always recommends consulting a patent attorney before filing or licensing decisions. Trademark, copyright, and trade-secret questions are out of scope.★ 26.3k GitHub starsSkillDescribe your invention in plain words and get backPatent Pipeline: From Invention to Filingwanshuiyin/Auto-claude-code-research-in-sleep · by wanshuiyinDescribe 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.★ 16.5k GitHub stars

More from wanshuiyin

SkillDEFAULT poster pipelinePaper Poster (HTML): measurement-gated poster generationwanshuiyin/Auto-claude-code-research-in-sleep · by wanshuiyinDEFAULT poster pipeline — build an academic conference poster (ICML/NeurIPS/ICLR/CVPR/...) as a single HTML/CSS file with measurement-driven hard gates, real paper figures, a two-hue design-token system, and print-ready PDF via headless Chromium. Use when the★ 16.5k GitHub starsSkillDescribe your invention in everyday words and get backPatent Novelty and Non-Obviousness Checkwanshuiyin/Auto-claude-code-research-in-sleep · by wanshuiyinDescribe 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.★ 16.5k GitHub starsSkillDescribe your invention in plain words and get backPatent Pipeline: From Invention to Filingwanshuiyin/Auto-claude-code-research-in-sleep · by wanshuiyinDescribe 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.★ 16.5k GitHub starsSkillGet a deep critical review of researchResearch Review via External Reviewer Backend (ultra reasoning)wanshuiyin/Auto-claude-code-research-in-sleep · by wanshuiyinGet a deep critical review of research from an external reviewer backend (Codex or manual). Use when user says "review my research", "help me review", "get external review", or wants critical feedback on research ideas, papers, or experimental results.★ 16.5k GitHub starsSkillDescribe your invention in plain words and get back a formalStructure Your Invention For A Patent Filingwanshuiyin/Auto-claude-code-research-in-sleep · by wanshuiyinDescribe 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.★ 16.5k GitHub starsSkillPeriodically check WandB metrics during training to catchTraining checkwanshuiyin/Auto-claude-code-research-in-sleep · by wanshuiyinPeriodically check WandB metrics during training to catch problems early (NaN, loss divergence, idle GPUs). Avoids wasting GPU hours on broken runs. Use when training is running and you want automated health checks.★ 16.5k GitHub stars