skills.rest
lgwanai
lgwanaiCOMMUNITY
Explore all skills by this author →
GitHub

patent-claims-analyzer

Analyze patent claim text for 35 USC 112(b) compliance issues.

4|1|Updated Mar 22, 2026
Search Tags:#USPTO#patent claims#MPEP#antecedent basis#definiteness#compliance review#112(b)
One-click install
npx skills add https://github.com/lgwanai/openforce --skill patent-claims-analyzer-lgwanai
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: patent-claims-analyzer
Source: https://github.com/lgwanai/openforce/tree/main/skills/patent-claims-analyzer
Command: npx skills add https://github.com/lgwanai/openforce --skill patent-claims-analyzer-lgwanai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

It helps patent applicants reduce the risk of office actions by automatically identifying claim clarity and antecedent basis problems under 35 USC 112(b), so you can fix drafting defects early.

Core Features & Use Cases

  • Antecedent Basis Checking: Detects missing introductions and incorrect “said/the” usage across independent and dependent claims.
  • Definiteness Analysis (35 USC 112(b)): Flags potentially indefinite subjective or relative terms that may lack objective boundaries.
  • Claim Structure Validation: Verifies independent vs. dependent structure, dependency correctness, and numbering consistency.

Quick Start

Provide your patent claims text and ask the skill to generate a claims analysis report with a compliance score, categorized issues, MPEP citations, and specific fix suggestions.

Frequently Asked Questions about patent-claims-analyzer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I check patent claims for 35 USC 112(b) definiteness and antecedent basis issues?▼

To validate patent claim antecedent basis before filing, submit your claim text to detect missing introductions and incorrect 'said/the' usage across independent and dependent claims, yielding specific fix suggestions.

What is antecedent basis checking in patent claims and how does it work?▼

Antecedent basis checking in patent claims identifies missing introductions and incorrect 'said/the' usage across independent and dependent claims, ensuring proper referential clarity before submitting to the USPTO.

How do I validate dependent claim structure and dependencies before filing a patent application?▼

To validate dependent claim structure before filing, analyze the text to verify independent vs. dependent relationships, dependency correctness, and numbering consistency, producing a structured compliance output.

How do I identify indefinite terms in patent claims under 35 USC 112(b)?▼

To identify indefinite terms in patent claims under 112(b), run a definiteness analysis that flags potentially indefinite subjective or relative terms lacking objective boundaries, complete with MPEP citations.

Can I use automated claim analysis to remediate office action problems related to claim wording?▼

Yes, you can use automated claim analysis to remediate office action problems by detecting antecedent basis and definiteness defects in your claim wording, then applying the suggested specific fixes.

Related Skills

Explore More Legal & Compliance Skills→
zhuyingqinzhuyingqin
1

claims-drafting

Draft jurisdiction-appropriate patent claim sets from invention disclosures.

Community
Advanced
rjwaltersrjwalters
1

ip-uspto

Draft, review, and revise USPTO non-provisional utility patent applications.

Community
Advanced
RobThePCGuyRobThePCGuy
167

patent-reviewer

Automate patent application reviews for USPTO MPEP compliance.

Community
Intermediate
Shallow-WShallow-W

patent-review

Review patent applications for office-action rejections under USPTO, CNIPA, or EPO standards.

Community
Advanced