skills/claims-drafting/SKILL.md
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.
npx skillsauth add shaun-z/auto-claude-code-research-in-sleep claims-draftingInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
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.
REVIEWER_MODEL = gpt-5.4 — External examiner for claim quality reviewMAX_CLAIM_REVISION_ROUNDS = 3 — Maximum revision iterationsCLAIM_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)patent/INVENTION_DISCLOSURE.md — structured invention with core/supporting/optional featurespatent/PRIOR_ART_REPORT.md — prior art to avoidpatent/NOVELTY_ASSESSMENT.md — novelty analysis with suggested amendments$ARGUMENTSLoad ../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).
Based on patent type and jurisdiction:
If PATENT_TYPE = utility_model (实用新型):
MIN_INDEPENDENT_CLAIMS = 1 (single apparatus claim is sufficient)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 |
CRITICAL — Claims numbering (CN format):
CRITICAL — No empirical content in claims:
For each claim category identified in INVENTION_DISCLOSURE.md:
Method Claim (broadest):
System/Apparatus Claim:
Quality checks for each independent claim:
For each independent claim, draft 5-10 dependent claims that:
Dependent claim format:
Rules for dependent claims:
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.
Call REVIEWER_MODEL via mcp__codex__codex with xhigh reasoning:
mcp__codex__codex:
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.
If the examiner review identifies issues:
mcp__codex__codex with threadId)MAX_CLAIM_REVISION_ROUNDS timesWrite 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]
mcp__codex__codex is not available, skip cross-model examiner review and note it in the output.development
Generate publication-quality academic illustrations through a local Codex app-server bridge that uses Codex native image generation. This is a separate experimental alternative to `paper-illustration`, intended for Claude Code users who want a GPT-image-style renderer without modifying the original skill.
development
Two-way sync between a local paper directory and an Overleaf project via the Overleaf Git bridge (Premium feature). Lets you keep ARIS audit/edit workflows on the local copy while collaborators edit in the Overleaf web UI. Token never touches the agent — user does the one-time auth via macOS Keychain. Use when user says "同步 overleaf", "overleaf sync", "推送到 overleaf", "connect overleaf", "Overleaf 桥接", "pull overleaf", "push overleaf", or wants to bridge their ARIS paper directory with an Overleaf project.
development
Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports. Uses a fresh cross-model reviewer with web/DBLP/arXiv lookup to catch hallucinated authors, wrong years, fabricated venues, version mismatches, and wrong-context citations (cite present but the cited paper does not establish the claim). Use when user says "审查引用", "check citations", "citation audit", "verify references", "引用核对", or before submission to ensure bibliography integrity.
data-ai
Paragraph-level structural blueprint for 10-12 page systems papers targeting OSDI, SOSP, ASPLOS, NSDI, and EuroSys. Provides page allocation, paragraph templates, and writing patterns. Use when user says "写系统论文", "systems paper structure", "OSDI paper", "SOSP paper", or wants fine-grained structural guidance for a systems conference submission.