Token导航 LogoToken导航

Agent Skill · 研究检索

claims-drafting(索赔起草)

claims-drafting 用于查找、检索和筛选相关信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

claims-drafting 是研究检索类 Agent Skill,可用宿主为 Codex、Claude、Cursor、Gemini CLI,通过GitHub 仓库获取,权限为调用外部服务;许可证信息还不明确,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 45,786。

总安装 824周安装 34GitHub Stars 7,815下载 269核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
unknown

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:claims-drafting(索赔起草)
来源仓库:https://github.com/wanshuiyin/auto-claude-code-research-in-sleep
仓库路径:skills/claims-drafting
安装命令:
npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill claims-drafting
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill claims-drafting

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

专利权利要求书起草核心技能,定义法律保护范围边界。根据技术领域自动选择 Jepson、EP 双段式等格式规范。生成至少两个独立权利要求(方法+系统),提供 fallback 方案。每轮修订不超过三轮,由外部 examiner 模型审核质量。

claims-drafting 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

来源仓库内路径:skills/claims-drafting

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 Codex、Claude、Cursor、Gemini CLI;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

claims-drafting 怎么安装?

在终端执行 npx skills add https://github.com/wanshuiyin/auto-claude-code-research-in-sleep --skill cl…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

claims-drafting 支持哪些 AI 工具?

公开资料标注支持 Codex、Claude、Cursor、Gemini CLI。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

claims-drafting 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

claims-drafting 是免费的吗?

公开资料没有标注明确许可证,收费和商用限制都无法确认。正式使用前请到来源仓库核对授权说明。

claims-drafting 用的人多吗?

公开数据是累计安装 824 次,近一周安装 34 次,下载 269 次,GitHub 7,815 星。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

claims-drafting 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 来源仓库有 7,815 星,维护活跃度相对可查。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 Codex,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 需要明确授权才能用到公司项目里的场景。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
claims-drafting

索赔起草 · 本页

8247,815调用外部服务未明确有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

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-5.4 — 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:

JurisdictionClaim StyleCharacterising PhrasePreamble Format
CNTwo-part (两部式)其特征在于一种...的方法/装置,包括:
USOpen (preferred)comprisingA method for..., comprising:
EPTwo-part (mandatory)characterised in thatA method for..., comprising [known], characterised in that [inventive]
ALLDraft CN + US + EPAll of the aboveAll 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 ElementMust be described in specificationReference 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:
  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.

平台分布

Codex

34.21%
按下载量换算92

Claude

29.65%
按下载量换算80

Cursor

17.72%
按下载量换算48

Gemini CLI

10.35%
按下载量换算28

安全审计

Gen Agent Trust Hub

通过

Socket

可疑

Snyk

通过

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills