patent-claims-analyzer

Antecedent basis compliance ensures terms are properly introduced before use; definiteness requires clear, unambiguous claim language. This Skill automates both checks against 35 USC 112(b) standards, flagging terms used without prior introduction or indefinite phrasing that could trigger USPTO rejections.

35 USC 112(b) requires patent claims to be definite and clear in scope. Violations—such as improper antecedent basis or subjective language—are common grounds for office actions. This Skill identifies these issues before filing, reducing rejection risk and rework cycles.

Yes. This Skill parses claim relationships, validates numbering, checks dependent claim references, and confirms proper hierarchical structure. It reports structural issues alongside compliance violations, ensuring claims are USPTO-ready.

Submit your claims for automated analysis. The Skill categorizes defects by severity, cites relevant MPEP sections, and suggests specific fixes. Output includes a compliance score and executable integration path for remediation.

Draft your claims, run them through this Skill for 112(b) compliance analysis, review the categorized issues and MPEP citations, apply suggested fixes, and re-analyze until compliance targets are met—streamlining pre-filing validation.