jurisdiction-format

Compile drafted patent applications into CNIPA, USPTO, and EPO filing-ready documents.

1|1|Updated May 19, 2026
One-click install
npx skills add https://github.com/zhuyingqin/ARIS-WEB --skill jurisdiction-format-zhuyingqin
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jurisdiction-format
Source: https://github.com/zhuyingqin/ARIS-WEB/tree/main/crates/runtime/assets/skills/jurisdiction-format
Command: npx skills add https://github.com/zhuyingqin/ARIS-WEB --skill jurisdiction-format-zhuyingqin

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) and references (resource) components.

What problem does it solve?

This Skill converts a drafted patent application into jurisdiction-specific filing formats, so you can produce CNIPA, USPTO, and EPO-ready documents without manually reformatting each section.

Core Features & Use Cases

  • Jurisdiction-specific compilation (CN/US/EP): Generates claims and full specification structure aligned to each office’s conventions.
  • Claim formatting rules per jurisdiction: CN claim phrasing and numbering, US sequential claim numbering with compliant wording, and EP two-part claim form with required “characterised in that.”
  • Output options for review vs filing: Produces markdown for review or docx for filing when document tooling is available.
  • Consistency checks and output summary: Ensures claims, numbering, and references remain aligned across generated formats.

Quick Start

Use the jurisdiction-format skill to compile your patent files into CN/US/EP formats and write the results to the patent/output directory.

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 CNIPA, USPTO, and EPO jurisdictions?

Patent claims formatting for CNIPA, USPTO, and EPO requires applying jurisdiction-specific rules like CN phrasing, US sequential numbering, and EP two-part forms. This Skill compiles a drafted patent application into filing-ready documents aligned to each office's conventions.

What is the difference between EPO two-part claims and standard USPTO claim formatting?

EPO two-part claims require a specific structure featuring the phrase "characterised in that," while USPTO claim formatting uses sequential numbering with compliant wording. This Skill applies these distinct jurisdiction formatting rules automatically when generating filing-ready patent documents.

Can I generate both markdown and docx output for patent filing documents?

You can generate markdown for review or docx for filing when document tooling is available. The Skill outputs compiled patent specifications and reformatted claims to the patent directory, ensuring references remain aligned across both formats through consistency checks.

What input files are needed to compile a patent application into jurisdiction-specific formats?

Compiling patent applications into jurisdiction-specific formats requires standardized inputs like drafted claims, specification sections, figures, and invention disclosure. The Skill reads these from a standard patent directory layout to produce CNIPA, USPTO, and EPO-ready documents.

Does claim formatting automatically check consistency across CN, US, and EP patent outputs?

Claim formatting includes consistency checks that ensure claims, numbering, and references remain aligned across generated CN, US, and EP formats. The Skill verifies this alignment while outputting the compiled patent documents to the specified output directory.

What's the best way to convert a drafted patent application into multiple jurisdiction filing formats?

The best way to convert a patent draft is using a jurisdiction compilation Skill that applies CN, US, and EP formatting rules. It processes standardized inputs and outputs filing-ready documents with consistent claims and specifications for each office.