jurisdiction-format

Compile patent claims and specifications into CN, US, and EP filing formats.

Updated May 20, 2026
One-click install
npx skills add https://github.com/lightrain-a/medtrace-aris --skill jurisdiction-format-lightrain-a
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jurisdiction-format
Source: https://github.com/lightrain-a/medtrace-aris/tree/main/.vendor/aris/skills/jurisdiction-format
Command: npx skills add https://github.com/lightrain-a/medtrace-aris --skill jurisdiction-format-lightrain-a

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It solves the problem of manually rewriting patent documents into different jurisdiction-specific filing formats, which is time-consuming and error-prone.

Core Features & Use Cases

  • Jurisdiction-specific patent compilation: Reformat claims and full descriptions into CNIPA (CN), USPTO (US), and EPO (EP) structures.
  • Jurisdiction rules enforcement: Applies claim formatting rules (including EP two-part claims with the required “characterised in that” phrase).
  • Review or filing outputs: Produces markdown for review or docx for filing-ready documents (when supported).
  • Consistency checks guidance: Ensures claims content is not modified—only format—and supports cross-format consistency verification.

Quick Start

Use the jurisdiction-format skill to compile your patent directory into a CN, US, and EP filing-ready set of markdown files by running it with your patent directory and selecting ALL as the target jurisdictions.

Frequently Asked Questions about jurisdiction-format

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

FAQPage Schema
How do I format patent claims for filing in multiple jurisdictions like CNIPA, USPTO, and EPO?

To format patent claims for multiple jurisdictions, you can compile drafted claims and specification sections into CNIPA, USPTO, and EPO structures. This process applies jurisdiction-specific formatting rules, such as EPO two-part claims with the characterised phrase, without altering the original claim content.

What is the best way to convert a drafted patent specification into a filing-ready format?

Converting a drafted patent specification into a filing-ready format involves loading shared jurisdiction templates and extracting inputs from CLAIMS.md and specification sources. It outputs claims, descriptions, and abstracts in selected formats like markdown for review or docx for filing.

Does converting patents for USPTO and CNIPA filing change the original claim content?

Converting patents for USPTO and CNIPA filing does not change the original claim content. The compilation process strictly enforces jurisdiction formatting rules and structural changes while ensuring cross-format consistency and leaving the actual claims content unmodified.

How do I generate EPO two-part claims with the required characterised phrase?

Generating EPO two-part claims requires applying specific jurisdiction rules during patent document compilation. The formatting process automatically enforces the required characterised in that phrase structure for European Patent Office submissions while maintaining content consistency.

Can I export patent documents into docx formats for submission preparation?

Yes, you can export patent documents into docx formats for submission preparation. The compilation process supports generating markdown files for internal review and docx files for filing-ready documents when supported by your environment.