Agent skill

Patent Claims Analyzer

by RobThePCGuy in RobThePCGuy/Claude-Patent-Creator

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

MITAuto-check passedLegal & Compliance

Install Patent Claims Analyzer

skills CLI

$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install RobThePCGuy/Claude-Patent-Creator patent-claims-analyzer --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/patent-claims-analyzer .claude/skills/patent-claims-analyzer && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "patent-claims-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/patent-claims-analyzer into .claude/skills/patent-claims-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-claims-analyzer", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/patent-claims-analyzer

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install RobThePCGuy/Claude-Patent-Creator patent-claims-analyzer --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/patent-claims-analyzer .agents/skills/patent-claims-analyzer && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "patent-claims-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/patent-claims-analyzer into .agents/skills/patent-claims-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-claims-analyzer", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install RobThePCGuy/Claude-Patent-Creator patent-claims-analyzer --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/patent-claims-analyzer .cursor/skills/patent-claims-analyzer && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "patent-claims-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/patent-claims-analyzer into .cursor/skills/patent-claims-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-claims-analyzer", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/RobThePCGuy/Claude-Patent-Creator.git --path skills/patent-claims-analyzer

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install RobThePCGuy/Claude-Patent-Creator patent-claims-analyzer --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/patent-claims-analyzer .gemini/skills/patent-claims-analyzer && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "patent-claims-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/patent-claims-analyzer into .gemini/skills/patent-claims-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-claims-analyzer", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install RobThePCGuy/Claude-Patent-Creator patent-claims-analyzer

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/patent-claims-analyzer .github/skills/patent-claims-analyzer && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "patent-claims-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/patent-claims-analyzer into .github/skills/patent-claims-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-claims-analyzer", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install RobThePCGuy/Claude-Patent-Creator patent-claims-analyzer --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/RobThePCGuy/Claude-Patent-Creator.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/patent-claims-analyzer .opencode/skills/patent-claims-analyzer && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "patent-claims-analyzer" agent skill from https://github.com/RobThePCGuy/Claude-Patent-Creator/tree/main/skills/patent-claims-analyzer into .opencode/skills/patent-claims-analyzer/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "patent-claims-analyzer", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: patent-claims-analyzer
GitHub stars: 196
Token cost: ~1.2k tokens
SKILL.md length: 319 words
Files: 1
Skills in repo: 17
Repo updated: Oct 6, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

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

Works in 4 steps: Antecedent Basis Checking → Definiteness Analysis (35 USC 112(b)) → Claim Structure Validation → …
Tasks that involve Intellectual property
SKILL.md covers When to Use, What This Skill Does, Required Data and How to Use, plus 5 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Patent Claims Analyzer is an agent skill from RobThePCGuy/Claude-Patent-Creator. Automated analysis of patent claims for USPTO compliance with 35 USC 112(b) requirements - antecedent basis, definiteness, claim structure

Its SKILL.md is about 1.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Legal & Compliance, covering Intellectual property. The repository describes itself as: USPTO patent creation system with MCP server + Claude Code plugin. Hybrid RAG search over MPEP/USC/CFR, BigQuery access to 76M+ patents, automated 35 USC 112 compliance checks… The licence is MIT.

When your agent uses it

Tasks that involve Intellectual property

Example prompts

“/patent-claims-analyzer”

Requirements

Python 3

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

Antecedent Basis Checking
Definiteness Analysis (35 USC 112(b))
Claim Structure Validation
Issue Categorization

What it can do on your machine

Read from SKILL.md and the folder at commit a089731. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Patent Claims Analyzer loads about 1.2k tokens when it runs. Until then it costs about 40 tokens; SKILL.md has 319 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~40
When it runs · the whole SKILL.md, loaded when a task matches: ~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from RobThePCGuy/Claude-Patent-Creator at commit a089731, republished under its MIT licence (© RobThePCGuy). 319 words, ~1,172 tokens.

Download SKILL.mdSave it as .claude/skills/patent-claims-analyzer/SKILL.md (or your agent's skills folder).

name: patent-claims-analyzer
description: Automated analysis of patent claims for USPTO compliance with 35 USC 112(b) requirements - antecedent basis, definiteness, claim structure
tools: Bash, Read, Write
model: sonnet

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:

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
Definiteness Analysis (35 USC 112(b)):
- Identifies subjective/indefinite terms
- Detects relative terms without reference
- Finds ambiguous claim language
- Checks for clear claim boundaries
Claim Structure Validation:
- Parses independent vs. dependent claims
- Validates claim dependencies
- Checks claim numbering
- Identifies claim type (method, system, etc.)
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:

Load the claims analyzer:

python

import os
import sys
sys.path.insert(0, os.environ.get('CLAUDE_PLUGIN_ROOT', '.'))
from mcp_server.claims_analyzer import ClaimsAnalyzer

analyzer = ClaimsAnalyzer()

Analyze claims:

python

claims_text = """
1. A system comprising:
    a processor;
    a memory; and
    said processor configured to...
"""

results = analyzer.analyze_claims(claims_text)

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

Antecedent Basis Errors:
- Using "said/the" before "a/an" introduction
- Terms appearing in dependent claims not in parent
- Missing antecedent in claim body
Definiteness Issues:
- Subjective terms: "substantially", "about", "approximately"
- Relative terms: "large", "small", "thin"
- Ambiguous language: "and/or", "optionally"
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:

Search MPEP for relevant guidance
Provide specific MPEP section citations
Show examiner guidance on similar issues
Suggest fixes based on USPTO practice

Tools Available

Read: To load claims from files
Bash: To run Python analyzer
Write: To save analysis reports

Files

Just SKILL.md in skills/patent-claims-analyzer of RobThePCGuy/Claude-Patent-Creator.

Open the folder on GitHubat commit a089731

Compare with similar skills

Patent Claims Analyzer next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Patent Claims Analyzer compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Patent Claims Analyzer this skillRobThePCGuy/Claude-Patent-Creator	196	—	~1.2k	Automated safety check: Pass	MIT	2 days ago
Paper to Chinese Patent DrafterYuan1z0825/nature-skills	47k	1 repos	~1.1k	Automated safety check: Pass	Apache-2.0	yesterday
Paper To Cn Patentsnipp-zha/Paper-to-patent-Skill	106	1 repos	~959	Automated safety check: Pass	None	3 mo ago
Patent Examinegfodor/legal-skills	393	—	~4.8k	Automated safety check: Pass	GPL-3.0	1 mo ago
Patent Auditgfodor/legal-skills	393	—	~2.9k	Automated safety check: Pass	GPL-3.0	1 mo ago
Replica BrandJakeschincariol/replica-skill	1.2k	—	~1.1k	Automated safety check: Pass	MIT	6 days ago

Similar skills

Paper to Chinese Patent Drafter
Yuan1z0825/nature-skills
Drafts Chinese invention patent applications and technical disclosures from research papers or inventor materials, tying each claim feature to source evidence.
47k GitHub starsUsed in 1 repo~1.1k tokens
Legal & ComplianceAuto-check passed
Paper To Cn Patent
snipp-zha/Paper-to-patent-Skill
Convert scientific papers, theses, technical reports, source code, figures, or research manuscripts into evidence-grounded Chinese invention patent drafts.
106 GitHub starsUsed in 1 repo~959 tokens
Legal & ComplianceAuto-check passed
Patent Examine
gfodor/legal-skills
Iteratively examine and revise a draft U.S. An agent skill from gfodor/legal-skills.
393 GitHub stars~4.8k tokensUpdated 1 mo ago
Legal & ComplianceAuto-check passed
Patent Audit
gfodor/legal-skills
Audit a draft U.S. An agent skill from gfodor/legal-skills.
393 GitHub stars~2.9k tokensUpdated 1 mo ago
Legal & ComplianceAuto-check passed
Replica Brand
Jakeschincariol/replica-skill
Names and rebrands an app clone so it is the user's own: name candidates with the trademark, domain, store and handle checks to run, a new palette checked for contrast, a logo brief, a voice guide…
1.2k GitHub stars~1.1k tokensUpdated 6 days ago
Legal & ComplianceAuto-check passed
Patent Workaround
gfodor/legal-skills
Adversarially pressure-test a draft or pending U.S. An agent skill from gfodor/legal-skills.
393 GitHub stars~5.7k tokensUpdated 1 mo ago
Legal & ComplianceAuto-check passed

More from RobThePCGuy/Claude-Patent-Creator

All 17 skills in this repo

Bigquery Patent Search
RobThePCGuy/Claude-Patent-Creator
Fast, cloud-based patent searching across 100 million+ worldwide patents using Google BigQuery - keyword search, CPC classification, patent details retrieval
196 GitHub stars~1.4k tokensUpdated 2 days ago
Auto-check: notes
Development Assistant
RobThePCGuy/Claude-Patent-Creator
Guides through adding new features, MCP tools, analyzers, and extending the patent creator system.
196 GitHub stars~1.3k tokensUpdated 2 days ago
Auto-check: notes
Epc Search
RobThePCGuy/Claude-Patent-Creator
RAG search across EPC provisions, EPO Guidelines for Examination, and PCT rules for European and international patent law research
196 GitHub stars~2.2k tokensUpdated 2 days ago
Auto-check passed
Epo Patent Analyzer
RobThePCGuy/Claude-Patent-Creator
Automated analysis of patent applications for EPO compliance with Art.
196 GitHub stars~2k tokensUpdated 2 days ago
Auto-check passed
Epo Patent Search
RobThePCGuy/Claude-Patent-Creator
Search European patents using EPO OPS API (full-text, legal status, families) and BigQuery (100M+ patents, EP filter) for prior art, competitive intelligence, and freedom-to-operate analysis
196 GitHub stars~1.9k tokensUpdated 2 days ago
Auto-check passed
Index Manager
RobThePCGuy/Claude-Patent-Creator
Manages MPEP index lifecycle including downloads, building, maintenance, and optimization.
196 GitHub stars~994 tokensUpdated 2 days ago
Auto-check passed

Questions about Patent Claims Analyzer

What does Patent Claims Analyzer do?

Automated analysis of patent claims for USPTO compliance with 35 USC 112(b) requirements - antecedent basis, definiteness, claim structure. Patent Claims Analyzer is an agent skill from RobThePCGuy/Claude-Patent-Creator.

When should I use Patent Claims Analyzer?

Patent Claims Analyzer fits situations like: tasks that involve Intellectual property.

How do I install Patent Claims Analyzer in Claude Code?

Run `npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a claude-code`. Or copy the skill folder (skills/patent-claims-analyzer in RobThePCGuy/Claude-Patent-Creator) into .claude/skills/patent-claims-analyzer in your project. Claude Code loads it when a task matches its description.

How do I install Patent Claims Analyzer in Codex?

Run `npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a codex`. Or copy the skill folder (skills/patent-claims-analyzer in RobThePCGuy/Claude-Patent-Creator) into .agents/skills/patent-claims-analyzer in your project. Codex loads it when a task matches its description.

Can I use Patent Claims Analyzer in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add RobThePCGuy/Claude-Patent-Creator --skill patent-claims-analyzer -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/patent-claims-analyzer, .gemini/skills/patent-claims-analyzer, .github/skills/patent-claims-analyzer and .opencode/skills/patent-claims-analyzer in your project.

What does Patent Claims Analyzer need to run?

SKILL.md names no scripts, command-line tools or credentials: Patent Claims Analyzer is instructions for the agent only. Our summary lists: Python 3.

Does Patent Claims Analyzer access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Patent Claims Analyzer safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Patent Claims Analyzer use?

Patent Claims Analyzer is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Patent Claims Analyzer use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Patent Claims Analyzer?

Skills that share tags, products or a category with Patent Claims Analyzer: Paper to Chinese Patent Drafter (Yuan1z0825/nature-skills, 47k stars), Paper To Cn Patent (snipp-zha/Paper-to-patent-Skill, 106 stars), Patent Examine (gfodor/legal-skills, 393 stars) and Patent Audit (gfodor/legal-skills, 393 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Patent Claims Analyzer?

RobThePCGuy (a GitHub user) maintains it in RobThePCGuy/Claude-Patent-Creator, which has 196 GitHub stars. The repository holds 17 skills in this directory. The repository was last updated on October 6, 2026.

Source: RobThePCGuy/Claude-Patent-Creator on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Install Patent Claims Analyzer

Facts

At a glance

What it does

When your agent uses it

Example prompts

Requirements

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Patent Claims Analyzer Skill

When to Use

What This Skill Does

Required Data

How to Use

Analysis Output Structure

Common Issues Detected

Presentation Format

Integration with MPEP

Tools Available

Files

Compare with similar skills

Similar skills

More from RobThePCGuy/Claude-Patent-Creator

Related

Questions about Patent Claims Analyzer