patent-claims-analyzer
Automated analysis of patent claims for USPTO compliance with 35 USC 112(b) requirements - antecedent basis, definiteness, claim structure
What this skill does
# 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**:
```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
## 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
]
}
```
## 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:
```
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:
...
```
## 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
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.