Token导航 LogoToken导航

Agent Skill · 研究检索

epo-patent-analyzer(欧洲专利局专利分析仪)

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

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

总安装 250周安装 10GitHub Stars 96下载 81核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:epo-patent-analyzer(欧洲专利局专利分析仪)
来源仓库:https://github.com/robthepcguy/claude-patent-creator
仓库路径:skills/epo-patent-analyzer
安装命令:
npx skills add https://github.com/robthepcguy/claude-patent-creator --skill epo-patent-analyzer
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

skills.shnpx skills
npx skills add https://github.com/robthepcguy/claude-patent-creator --skill epo-patent-analyzer

这个 Skill 是做什么的

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

epo-patent-analyzer 用于欧洲专利局专利申请合规性分析,支持 EPC 条款和形式要求检查。适用于权利要求书 Art.84 合规、充分公开 Art.83 分析和正式程序 Rule 42-49 审查。可转换 USPTO 风格权利要求为 EPO 两段式结构,准备答复审查意见或 Euro-PCT 进入。

安装前建议确认权限范围和维护状态,注意是否会触发专利数据库访问或网络请求,确保合法使用。适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

来源仓库内路径:skills/epo-patent-analyzer

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

    可以直接复制的命令是 npx skills add https://github.com/robthepcguy/claude-patent-creator --skill epo-…;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

epo-patent-analyzer 怎么安装?

在终端执行 npx skills add https://github.com/robthepcguy/claude-patent-creator --skill epo-patent-ana…。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

epo-patent-analyzer 支持哪些 AI 工具?

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

epo-patent-analyzer 需要什么权限?

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

epo-patent-analyzer 是免费的吗?

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

epo-patent-analyzer 用的人多吗?

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

epo-patent-analyzer 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

  • 同时适配 4 种工具,换客户端不用重新找替代品。
  • 第三方扫描已通过,常见的高风险行为没有命中。

先想清楚的地方

  • 许可证没有明确标注,能不能商用、能不能再分发都不确定。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 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调用外部服务未明确有提醒
epo-patent-analyzer

欧洲专利局专利分析仪 · 本页

25096调用外部服务未明确通过

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

SKILL.md 原文

EPO Patent Analyzer Skill

Automated analysis of patent applications for European Patent Office compliance under the European Patent Convention (EPC).

When to Use

Invoke this skill when users ask to:

  • Review patent claims for EPO Art. 84 compliance
  • Check sufficiency of disclosure under Art. 83 EPC
  • Analyze EPO formalities under Rules 42-49 EPC
  • Convert USPTO-style claims to EPO two-part form
  • Prepare for EPO examination or respond to EPO communications
  • Validate applications before EP filing or Euro-PCT entry

What This Skill Does

Performs comprehensive EPO-focused analysis:

  1. Claims Analysis (Art. 84 EPC):

- Clarity: identifies unclear or ambiguous terms - Conciseness: detects redundant or overlapping claims - Support: verifies all claims are supported by description - Two-part form (Rule 43(1) EPC): checks preamble + "characterised in that" - Claim categories: product, process, apparatus, use - Excluded subject matter: Art. 52(2) and Art. 53 EPC

  1. Sufficiency of Disclosure (Art. 83 EPC):

- Reproducibility: can a person skilled in the art reproduce the invention? - Breadth of claims vs disclosure: is the full scope enabled? - Essential technical features: all present and described? - Working examples: at least one concrete embodiment?

  1. Formalities (Rules 42-49 EPC):

- Description format (Rule 42): required sections in correct order - Claims form (Rule 43): two-part form, numbering, references - Drawings (Rule 46): margins, no text, reference signs - Abstract (Rule 47): max 150 words, figure designation - Physical requirements: A4, margins, fonts

  1. Issue Categorization:

- Critical: Will cause objection under EPC - Important: May cause objection or limit scope - Minor: Best practice per EPO Guidelines

Required Data

This skill uses the EPO compliance analyzers and the EPC/EPO Guidelines search:

MCP Tools Available:

  • review_epo_claims - Art. 84 EPC compliance checking
  • review_epo_specification - Art. 83 EPC sufficiency analysis
  • check_epo_formalities - Rules 42-49 EPC formalities
  • search_patent_law - Search EPC, EPO Guidelines, PCT rules

How to Use

When this skill is invoked:

  1. Determine analysis scope:

- Full application review (claims + description + formalities) - Claims-only review (Art. 84 EPC) - Sufficiency-only review (Art. 83 EPC) - Formalities-only review (Rules 42-49 EPC)

  1. Run appropriate analyzers:

- For claims: check clarity, conciseness, support, two-part form - For sufficiency: check reproducibility, scope vs disclosure, examples - For formalities: check all Rules 42-49 requirements

  1. Present analysis:

- Show compliance score (0-100) - List issues by severity (critical, important, minor) - Provide EPC article/rule citations for each issue - Reference EPO Guidelines sections - Suggest specific fixes

Analysis Output Structure

{
    "jurisdiction": "EPO",
    "claim_count": 15,
    "independent_count": 2,
    "dependent_count": 13,
    "compliance_score": 72,
    "total_issues": 8,
    "critical_issues": 2,
    "important_issues": 4,
    "minor_issues": 2,
    "issues": [
        {
            "category": "clarity",
            "severity": "critical",
            "claim_number": 1,
            "term": "substantially",
            "description": "Term 'substantially' lacks objective definition under Art. 84 EPC",
            "epc_cite": "Art. 84 EPC",
            "guidelines_cite": "EPO Guidelines F-IV, 4.6",
            "suggestion": "Replace with objective criterion or remove"
        },
        {
            "category": "two_part_form",
            "severity": "important",
            "claim_number": 1,
            "description": "Independent claim not in two-part form per Rule 43(1) EPC",
            "epc_cite": "Rule 43(1) EPC",
            "guidelines_cite": "EPO Guidelines F-IV, 3.2",
            "suggestion": "Restructure: preamble + 'characterised in that' + novel features"
        }
    ]
}

Common EPO Issues Detected

  1. Clarity Issues (Art. 84 EPC):

- Relative terms without objective reference - Inconsistent terminology between claims and description - Functional features not clearly defined - "Means for" language without clear structural support

  1. Support Issues (Art. 84 EPC):

- Claims broader than description discloses - Unsupported generalizations from specific examples - Missing essential technical features - Claim scope exceeding experimental evidence

  1. Sufficiency Issues (Art. 83 EPC):

- Insufficient detail for reproduction - Claims too broad relative to examples - Missing critical parameters or conditions - Undue burden on skilled person

  1. Formality Issues (Rules 42-49 EPC):

- Missing required description sections - Abstract exceeding 150 words - Text in drawings - Claims not in two-part form

Presentation Format

Present analysis as:

EPO COMPLIANCE ANALYSIS REPORT
================================

Jurisdiction: European Patent Office (EPC)
Analysis Date: [Date]

Summary:
- Total Claims: 15 (2 independent, 13 dependent)
- Compliance Score: 72/100
- Issues Found: 8 (2 critical, 4 important, 2 minor)

CLAIMS ANALYSIS (Art. 84 EPC):

  Clarity:
  [Claim 1] CRITICAL - "substantially uniform" lacks objective definition
    Art. 84 EPC / EPO Guidelines F-IV, 4.6
    Fix: Define with measurable criterion (e.g., "within 5% deviation")

  Support:
  [Claim 3] IMPORTANT - "any wireless protocol" exceeds disclosure
    Art. 84 EPC / EPO Guidelines F-IV, 6.2
    Fix: Limit to disclosed protocols (Bluetooth, Wi-Fi, NFC)

  Two-Part Form:
  [Claim 1] IMPORTANT - Not in two-part form
    Rule 43(1) EPC / EPO Guidelines F-IV, 3.2
    Fix: Identify closest prior art, split into known + novel features

SUFFICIENCY ANALYSIS (Art. 83 EPC):

  [PASS] At least one embodiment fully described
  [WARN] Claims 8-10 cover embodiment not exemplified
    Art. 83 EPC / EPO Guidelines F-III, 3
    Consider: Add working example for thermal processing variant

FORMALITIES (Rules 42-49 EPC):

  [PASS] Description sections in correct order (Rule 42)
  [FAIL] Abstract: 167 words (max 150) (Rule 47)
  [PASS] Drawings: no text, proper margins (Rule 46)
  [FAIL] No figure designated for abstract (Rule 47(2)(b))

Key EPO vs USPTO Differences

AspectUSPTO (35 USC)EPO (EPC)
Claim clarityReasonable certainty (112(b))Strict objective clarity (Art. 84)
Claim formOpen formatTwo-part form preferred (Rule 43)
SupportWritten description (112(a))Supported by description (Art. 84)
EnablementEnable POSITA (112(a))Sufficiency of disclosure (Art. 83)
Best modeRequired (112(a))Not required
Terms of degreeAllowed with spec supportMust have objective reference
SoftwarePatent-eligible if technicalMust show "further technical effect"
Medical methodsAllowedExcluded (Art. 53(c))
Novelty102 (1-year grace period)Art. 54 (absolute novelty, no grace period)
Obviousness103 (obvious to POSITA)Art. 56 (inventive step, problem-solution)

Integration with EPC Search

For each issue, the skill can:

  1. Search EPC provisions and EPO Guidelines for relevant guidance
  2. Provide specific article, rule, and Guidelines section citations
  3. Show EPO Board of Appeal case law on similar issues
  4. Suggest fixes based on EPO prosecution practice

Tools Available

  • Read: To load application from files
  • Bash: To run EPO compliance analyzers
  • Write: To save analysis reports

平台分布

Codex

38.5%
按下载量换算31

Claude

28.93%
按下载量换算23

Cursor

18.48%
按下载量换算15

Gemini CLI

9.12%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

调用外部服务

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

安装前确认

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

继续浏览同类 Skills