patent-claims-analyzer

Automated analysis of patent claims for USPTO compliance with 35 USC 112(b) requirements - antecedent basis, definiteness, claim structure

By robthepcguy · 435 installs

npx skills add robthepcguy/claude-patent-creator --skill patent-claims-analyzer

Source repository · Upstream listing

Patent Claims Analyzer Skill Automated analysis of patent claims for USPTO compliance with 35 USC 112(b) requirements. 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 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 Required Data This skill uses the automated claims analyzer from: Location : ${CLAUDE PLUGIN ROOT}/python\claims analyzer.py How to Use When this skill is invoked: 1. Load the claims analyzer : 2. Analyze claims : 3. Present analysis : Show compliance score (0 100) List issues by severity (critical, important, minor) Provide MPEP citations for each issue Suggest specific fixes Analysis Output Structure 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 Presentation Format Present analysis as: Integration with 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 Tools Available Read : To load claims from files Bash : To run Python analyzer Write : To save analysis reports