jurisdiction-format

Compile drafted patent applications into CN, US, and EP filing formats.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/Shallow-W/llm-wiki --skill jurisdiction-format-shallow-w
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jurisdiction-format
Source: https://github.com/Shallow-W/llm-wiki/tree/main/.claude/skills/jurisdiction-format
Command: npx skills add https://github.com/Shallow-W/llm-wiki --skill jurisdiction-format-shallow-w

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

It turns a drafted patent application into jurisdiction-specific, submission-ready document structure and formatting without mixing CN/US/EP conventions.

Core Features & Use Cases

  • CN/US/EP formatting compilation: Produces Claims, Description/Specification, and jurisdiction-specific Abstracts in the correct order and style.
  • Rules-based claim formatting: Applies CNIPA dependent/independent claim phrasing, US sequential claim numbering, and EPO two-part claims with mandatory “characterised in that”.
  • Multi-jurisdiction consistency checks: Ensures claims remain technically identical while only the formatting differs across jurisdictions.
  • Output options: Writes results as reviewable Markdown or generates docx documents when docx tooling is available.

Quick Start

Use the jurisdiction-format skill on your patent directory to compile patent filing documents for CN, US, and EP outputs.

Frequently Asked Questions about jurisdiction-format

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

FAQPage Schema
How do I format a patent application for filing in CN, US, and EP jurisdictions?

To format a patent application for CN, US, and EP filing, compile drafted claims, specification sections, and abstracts into jurisdiction-specific submission-ready documents using jurisdiction formatting rules. This reorganizes inputs into the correct office style without mixing conventions.

What are the claim formatting differences between CNIPA, USPTO, and EPO?

CNIPA requires specific dependent and independent claim phrasing, USPTO enforces sequential claim numbering, and EPO mandates two-part claims featuring the phrase "characterised in that". These distinct formatting rules apply while keeping the technical content identical across jurisdictions.

Can I generate docx patent filing documents from a drafted markdown application?

Yes, you can generate filing-ready patent documents as reviewable Markdown or output docx files when docx tooling is available. The formatted application documents are written to a structured patent output directory for CN, US, and EP jurisdictions.

How do I ensure claims remain consistent across CN, US, and EP patent filings?

Multi-jurisdiction consistency checks ensure claims remain technically identical while only the formatting differs across CN, US, and EP outputs. This prevents altering the scope of the invention when applying different office-specific formatting rules.

Does patent jurisdiction formatting require loading specific reference files?

Yes, jurisdiction-specific formatting references for CN, US, and EP must be loaded to apply the correct office styles. It then extracts inputs from your given patent directory to reorganize claims, specification sections, figures, and abstracts.

When do I need to compile a drafted patent application into jurisdiction formats?

You need patent jurisdiction formatting when a drafted application must be reorganized and reformatted per the respective office style for submission. This is intended for patent drafting workflows where claims, specifications, figures, and abstracts require specific CN, US, and EP formats.