
claims-drafting
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.
- Installs
- 488
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill claims-drafting- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads claims-drafting automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Claims Drafting: The Core Patent Skill
Before each reviewer slot, follow Selectable Reviewers: resolve invocation →
.aris/reviewer.json→ Claude Code default (Codex MCP) withreviewer_route.pythrough the canonical helper resolver, preserving this slot's tier, fresh contexts, source/image inputs and deterministic gates. Codex examples/pins below apply only tobackend=codex; other routes use their own first-call/reply contract. Save the route and actual returned identity; unavailable selections areREVIEW_UNAVAILABLE. Classify acceptance from actual families/completion/scope. Forward invocation reviewer/model/effort overrides to reviewer-bearing children. Generation workers are unchanged.
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 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(发明专利) orutility_model(实用新型, apparatus claims only)
Inputs
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- 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):
- Start with preamble identifying the category and purpose
- List the core inventive features (from the "Core Inventive Concept" section)
- Include enough known features for context (but not more than necessary)
- Use open transition ("comprising" / "包括")
- Each element should be separated by semicolons or on separate lines
- Apply jurisdiction-specific format:
- CN: 前序部分 + "其特征在于" + 特征部分
- US: Preamble + "comprising:" + elements
- EP: Preamble + known features + "characterised in that" + inventive features
System/Apparatus Claim:
- Mirror the method claim in structural form
- Each method step becomes a "module configured to..." or "component for..."
- 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:
- Narrow the core inventive features: Specific implementations, parameters, ranges
- Cover preferred embodiments: Features from the specification's detailed description
- Provide fallback positions: If the independent claim is rejected, these narrower claims may survive
- 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:
Resolve this reviewer slot first; the following is the
backend=codexexample.
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:
- Address all CRITICAL issues (anticipation, obviousness, indefiniteness)
- Address MAJOR issues (scope too narrow, missing support, weak fallbacks)
- Consider MINOR issues (antecedent basis, formatting)
- Re-submit to examiner for round 2 (use
mcp__codex__codexwith threadId) - Repeat up to
MAX_CLAIM_REVISION_ROUNDStimes
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 the selected reviewer is unavailable, record
REVIEW_UNAVAILABLE; continue only as an explicitly unreviewed draft, without switching providers.
FAQ
What does the claims-drafting skill do?
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.
How do I install claims-drafting?
Run npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill claims-drafting in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/claims-drafting/ (personal) or .claude/skills/claims-drafting/ (project).
Which AI agents can use claims-drafting?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is claims-drafting safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains claims-drafting?
It is published by wanshuiyin in wanshuiyin/auto-claude-code-research-in-sleep. It has 488 recorded installs.
More from wanshuiyin/auto-claude-code-research-in-sleep
paper-figure
wanshuiyin/auto-claude-code-research-in-sleep
Generate publication-quality figures and tables from experiment results. Use when user says "画图", "作图", "generate figures", "paper figures", or needs plots for a paper.
semantic-scholar
wanshuiyin/auto-claude-code-research-in-sleep
Search published venue papers (IEEE, ACM, Springer, etc.) via Semantic Scholar API. Complements /arxiv (preprints) with citation counts, venue metadata, and TLDR. Use when user says "search semantic scholar", "find IEEE papers", "find journal papers", "venue papers", "citation search", or wants published literature beyond arXiv preprints.
research-lit
wanshuiyin/auto-claude-code-research-in-sleep
Search and analyze research papers, find related work, summarize key ideas. Use when user says "find papers", "related work", "literature review", "what does this paper say", or needs to understand academic papers.
idea-discovery
wanshuiyin/auto-claude-code-research-in-sleep
Workflow 1: Full idea discovery pipeline to go from a broad research direction to validated, pilot-tested ideas. Use when user says "找idea全流程", "idea discovery pipeline", "从零开始找方向", or wants the complete idea exploration workflow.
idea-creator
wanshuiyin/auto-claude-code-research-in-sleep
Generate and rank research ideas given a broad direction. Use when user says "找idea", "brainstorm ideas", "generate research ideas", "what can we work on", or wants to explore a research area for publishable directions.
arxiv
wanshuiyin/auto-claude-code-research-in-sleep
Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv", "arxiv search", "get paper pdf", or wants to find and save papers from arXiv to the local paper library.
Popular productivity & automation skills
agent-browser
vercel-labs/agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.
lark-doc
open.feishu.cn
飞书云文档(Docx / Wiki)内容操作:读取、创建、编辑文档,插入或下载图片附件,以及操作思维笔记。用户提供文档 URL/token(包括 doubao.com 的 /docx/、/wiki/)时使用;按 URL 路径/token 而非域名路由;/page/ 是妙搭应用,非飞书云文档。文档内嵌资源按读取参考中的统一规则分流。独立评论操作走 lark-drive;随正文读取评论使用 docs +fetch。表格或 Base 内部数据操作不在本 skill。
lark-base
open.feishu.cn
飞书多维表格(Base)操作:建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式(BaseApp/AppMode 页面与组件)、Workspace 目录、workflow、角色权限、模板中心(多维表格模板分类/列表/搜索);遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps;文件导入/导出转 lark-drive,认证/授权转 lark-shared。
lark-drive
open.feishu.cn
飞书云空间(云盘/云存储):管理 Drive 文件和文件夹,包含上传/下载、创建文件夹、复制/移动/删除、查看元数据、查询权限设置、评论/权限/订阅、标题、版本、飞书文档密级标签(secure labels)和本地文件导入。用户需要整理云盘目录、处理云空间资源 URL/token、判断链接类型/真实 token/标题,或导入 Word/Markdown/Excel/CSV/PPTX/.base 为 docx/sheet/bitable/slides 时使用;doubao.com 云空间 URL/token 也按资源路径和 token 路由,不回退 WebFetch。不负责:文档内容编辑(走 lark-doc)、表格/Base 表内数据操作(走 lark-sheets/lark-base)、知识空间节点/成员管理(走 lark-wiki)、原生 Markdown 文件读写/patch/diff(走 lark-markdown)。
lark-shared
open.feishu.cn
Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling notice JSON.
lark-im
open.feishu.cn
飞书即时通讯:收发消息和管理群聊。发送和回复消息、搜索聊天记录、管理群聊成员、上传下载图片和文件、管理表情回复、发送应用内/短信/电话加急、发送和处理交互卡片(Interactive Card)、监听卡片按钮回调(card.action.trigger)。当用户需要发消息、查看或搜索聊天记录、下载聊天中的文件、查看群成员、搜索群、创建群聊或话题群、管理标记数据、管理 Feed 置顶(添加/移除/查询置顶会话)、管理标签数据、处理卡片回调时使用。