patent-claims-analyzer

Compare original and translation side by side

🇺🇸

Original

English
🇨🇳

Translation

Chinese

Patent Claims Analyzer Skill

专利权利要求分析Skill

Automated analysis of patent claims for USPTO compliance with 35 USC 112(b) requirements.
针对USPTO 35 USC 112(b)要求的专利权利要求自动分析。

When to Use

使用场景

Invoke this skill when users ask to:
  • Review patent claims for definiteness
  • Check antecedent basis in claims
  • Analyze claim structure
  • Find claim drafting issues
  • Validate claims before filing
  • Fix USPTO office action issues related to claims
当用户提出以下需求时调用此Skill:
  • 审查专利权利要求的明确性
  • 检查权利要求中的先行基础
  • 分析权利要求结构
  • 查找权利要求撰写问题
  • 提交前验证权利要求
  • 解决与权利要求相关的USPTO审查意见问题

What This Skill Does

功能说明

Performs comprehensive automated analysis:
  1. Antecedent Basis Checking:
    • Finds terms used without prior introduction
    • Detects missing "a/an" before first use
    • Identifies improper "said/the" before first use
    • Tracks term references across claims
  2. Definiteness Analysis (35 USC 112(b)):
    • Identifies subjective/indefinite terms
    • Detects relative terms without reference
    • Finds ambiguous claim language
    • Checks for clear claim boundaries
  3. Claim Structure Validation:
    • Parses independent vs. dependent claims
    • Validates claim dependencies
    • Checks claim numbering
    • Identifies claim type (method, system, etc.)
  4. Issue Categorization:
    • Critical: Must fix before filing
    • Important: May cause rejection
    • Minor: Best practice improvements
执行全面的自动化分析:
  1. 先行基础检查
    • 查找未预先引入就使用的术语
    • 检测首次使用前缺少“a/an”的情况
    • 识别首次使用前不当使用“said/the”的情况
    • 追踪术语在各权利要求中的引用
  2. 明确性分析(35 USC 112(b)):
    • 识别主观/不明确术语
    • 检测无参考的相对术语
    • 查找模糊的权利要求表述
    • 检查权利要求边界是否清晰
  3. 权利要求结构验证
    • 解析独立权利要求与从属权利要求
    • 验证权利要求的从属关系
    • 检查权利要求编号
    • 识别权利要求类型(方法、系统等)
  4. 问题分类
    • 严重:提交前必须修复
    • 重要:可能导致驳回
    • 轻微:最佳实践优化

Required Data

所需数据

This skill uses the automated claims analyzer from: Location:
${CLAUDE_PLUGIN_ROOT}/python\claims_analyzer.py
本Skill使用的自动化权利要求分析器来自: 位置
${CLAUDE_PLUGIN_ROOT}/python\claims_analyzer.py

How to Use

使用方法

When this skill is invoked:
  1. Load the claims analyzer:
    python
    import sys
    sys.path.insert(0, os.path.join(os.environ.get('CLAUDE_PLUGIN_ROOT', '.'), 'python'))
    from python.claims_analyzer import ClaimsAnalyzer
    
    analyzer = ClaimsAnalyzer()
  2. Analyze claims:
    python
    claims_text = """
    1. A system comprising:
        a processor;
        a memory; and
        said processor configured to...
    """
    
    results = analyzer.analyze_claims(claims_text)
  3. Present analysis:
    • Show compliance score (0-100)
    • List issues by severity (critical, important, minor)
    • Provide MPEP citations for each issue
    • Suggest specific fixes
调用此Skill时:
  1. 加载权利要求分析器
    python
    import sys
    sys.path.insert(0, os.path.join(os.environ.get('CLAUDE_PLUGIN_ROOT', '.'), 'python'))
    from python.claims_analyzer import ClaimsAnalyzer
    
    analyzer = ClaimsAnalyzer()
  2. 分析权利要求
    python
    claims_text = """
    1. A system comprising:
        a processor;
        a memory; and
        said processor configured to...
    """
    
    results = analyzer.analyze_claims(claims_text)
  3. 展示分析结果
    • 显示合规分数(0-100)
    • 按严重程度列出问题(严重、重要、轻微)
    • 为每个问题提供MPEP引用
    • 给出具体修复建议

Analysis Output Structure

分析输出结构

python
{
    "claim_count": 20,
    "independent_count": 3,
    "dependent_count": 17,
    "compliance_score": 85,  # 0-100
    "total_issues": 12,
    "critical_issues": 2,
    "important_issues": 7,
    "minor_issues": 3,
    "issues": [
        {
            "category": "antecedent_basis",
            "severity": "critical",
            "claim_number": 1,
            "term": "said processor",
            "description": "Term 'processor' used with 'said' before first introduction",
            "mpep_cite": "MPEP 2173.05(e)",
            "suggestion": "Change 'said processor' to 'the processor' or introduce with 'a processor' first"
        },
        # ... more issues
    ]
}
python
{
    "claim_count": 20,
    "independent_count": 3,
    "dependent_count": 17,
    "compliance_score": 85,  # 0-100
    "total_issues": 12,
    "critical_issues": 2,
    "important_issues": 7,
    "minor_issues": 3,
    "issues": [
        {
            "category": "antecedent_basis",
            "severity": "critical",
            "claim_number": 1,
            "term": "said processor",
            "description": "Term 'processor' used with 'said' before first introduction",
            "mpep_cite": "MPEP 2173.05(e)",
            "suggestion": "Change 'said processor' to 'the processor' or introduce with 'a processor' first"
        },
        # ... more issues
    ]
}

Common Issues Detected

常见检测问题

  1. Antecedent Basis Errors:
    • Using "said/the" before "a/an" introduction
    • Terms appearing in dependent claims not in parent
    • Missing antecedent in claim body
  2. Definiteness Issues:
    • Subjective terms: "substantially", "about", "approximately"
    • Relative terms: "large", "small", "thin"
    • Ambiguous language: "and/or", "optionally"
  3. Structure Issues:
    • Means-plus-function without adequate structure
    • Improper claim dependencies
    • Missing preamble or transition
  1. 先行基础错误
    • 在使用"a/an"引入前使用"said/the"
    • 从属权利要求中出现的术语未在母权利要求中出现
    • 权利要求正文中缺少先行基础
  2. 明确性问题
    • 主观术语:"substantially", "about", "approximately"
    • 相对术语:"large", "small", "thin"
    • 模糊表述:"and/or", "optionally"
  3. 结构问题
    • 手段加功能表述但缺乏足够结构支持
    • 不当的权利要求从属关系
    • 缺少前序部分或过渡语

Presentation Format

展示格式

Present analysis as:
CLAIMS ANALYSIS REPORT
======================

Summary:
- Total Claims: 20 (3 independent, 17 dependent)
- Compliance Score: 85/100
- Issues Found: 12 (2 critical, 7 important, 3 minor)

CRITICAL ISSUES (Must Fix):

[Claim 1] Antecedent Basis Error
  Issue: Term 'processor' used with 'said' before introduction
  Location: "said processor configured to..."
  MPEP: 2173.05(e)
  Fix: Change to 'the processor' or introduce with 'a processor' first

[Claim 5] Indefinite Term
  Issue: Subjective term 'substantially' without definition
  Location: "substantially similar to..."
  MPEP: 2173.05(b)
  Fix: Define 'substantially' in specification or use objective criteria

IMPORTANT ISSUES:
...

MINOR ISSUES:
...
分析结果按以下格式展示:
CLAIMS ANALYSIS REPORT
======================

摘要:
- 总权利要求数:20(3项独立,17项从属)
- 合规分数:85/100
- 发现问题:12个(2个严重,7个重要,3个轻微)

严重问题(必须修复):

[权利要求1] 先行基础错误
  问题:术语'processor'在引入前使用了'said'
  位置:"said processor configured to..."
  MPEP参考:2173.05(e)
  修复建议:改为'the processor'或先使用'a processor'引入

[权利要求5] 不明确术语
  问题:主观术语'substantially'未定义
  位置:"substantially similar to..."
  MPEP参考:2173.05(b)
  修复建议:在说明书中定义'substantially'或使用客观标准

重要问题:
...

轻微问题:
...

Integration with MPEP

与MPEP的集成

For each issue, the skill can:
  1. Search MPEP for relevant guidance
  2. Provide specific MPEP section citations
  3. Show examiner guidance on similar issues
  4. Suggest fixes based on USPTO practice
针对每个问题,本Skill可:
  1. 搜索MPEP获取相关指导
  2. 提供具体的MPEP章节引用
  3. 展示审查员对类似问题的指导意见
  4. 根据USPTO实践给出修复建议

Tools Available

可用工具

  • Read: To load claims from files
  • Bash: To run Python analyzer
  • Write: To save analysis reports
  • Read:从文件加载权利要求
  • Bash:运行Python分析器
  • Write:保存分析报告