Token导航 LogoToken导航TokenDH.com
研究检索external-servicegithub未标认证来源可访问许可证需确认审计通过

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

Agent Skill

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

总安装

250

周安装

10

GitHub Stars

96

下载量

81
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 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

简介

epo-patent-analyzer 用于欧洲专利局专利申请合规性分析,支持 EPC 条款和形式要求检查。

  • 适用于权利要求书 Art.84 合规、充分公开 Art.83 分析和正式程序 Rule 42-49 审查。
  • 可转换 USPTO 风格权利要求为 EPO 两段式结构,准备答复审查意见或 Euro-PCT 进入。
  • 安装前建议确认权限范围和维护状态,注意是否会触发专利数据库访问或网络请求,确保合法使用。
  • 适用宿主包括 Codex、Claude、Cursor、Gemini CLI,接入前应确认版本、权限和运行环境要求。

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

38.5%
按下载量换算31

Claude

28.93%
按下载量换算23

Cursor

18.48%
按下载量换算15

Gemini CLI

9.12%
按下载量换算7

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

external-service

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

安装前确认

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

来源信息

继续浏览同类 Skills