jurisdiction-format

Compile patent drafts into CN, US, and EP filing documents.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Mang30/myskills --skill jurisdiction-format-mang30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jurisdiction-format
Source: https://github.com/Mang30/myskills/tree/main/skills/jurisdiction-format
Command: npx skills add https://github.com/Mang30/myskills --skill jurisdiction-format-mang30

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill converts a drafted patent document into jurisdiction-specific filing-ready formatting, so you do not have to manually rewrite structure, sections, and claim phrasing for CN/US/EP submissions.

Core Features & Use Cases

  • Jurisdiction-specific formatting: Generates CNIPA (CN), USPTO (US), and EPO (EP) structures from the same source content.
  • Claims transformation by rule set: Reformats claims to match CNIPA/USPTO/EPO conventions without changing the underlying technical content.
  • Output modes for review or filing: Produces markdown for review or docx for filing workflows (when python-docx is available).

Quick Start

Use the jurisdiction-format skill to compile your patent draft in CN/US/EP format by telling it to run for the target jurisdictions and read the existing files from your patent directory.

Frequently Asked Questions about jurisdiction-format

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

FAQPage Schema
How do I convert a patent draft into CNIPA, USPTO, and EPO filing formats?

To convert a patent draft into CNIPA, USPTO, and EPO filing formats, the skill compiles source content into jurisdiction-specific structures by applying office-specific section orders, claims styles, and abstract limits, outputting markdown or docx files.

What is the best way to reformat patent claims for different jurisdictions without changing the technical content?

Reformatting patent claims for different jurisdictions involves applying CNIPA, USPTO, and EPO rule sets to transform claims phrasing and structure, ensuring format-only consistency while preserving the original technical content.

Do I need python-docx to generate patent filing documents in docx format?

You need python-docx to generate patent filing documents in docx format, as this output mode depends on the library's availability. Without it, you can still produce markdown outputs for review workflows.

Can I use the same patent content to generate submission-ready documents for CN, US, and EP offices?

Yes, you can use the same patent content to generate submission-ready documents for CN, US, and EP offices by loading shared formatting references and writing formatted outputs to jurisdiction-specific patent output directories.

What are the limitations of automated patent formatting for multiple jurisdictions?

The limitations of automated patent formatting include performing only format-only consistency checks without altering underlying technical content, and requiring python-docx installation for docx generation, restricting outputs to markdown otherwise.