jurisdiction-format

Name: jurisdiction-format
Availability: InStock
Author: dogekiki

Compile patent application documents into CNIPA, USPTO, and EPO filing formats.

1|Updated Jul 21, 2026

Search Tags:#automation #formatting #compliance #patent #jurisdiction #filing

Ready to run

npx skills add https://github.com/dogekiki/SP-test --skill jurisdiction-format-dogekiki

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: jurisdiction-format
Source: https://github.com/dogekiki/SP-test/tree/main/.trae/skills/jurisdiction-format
Command: npx skills add https://github.com/dogekiki/SP-test --skill jurisdiction-format-dogekiki

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires python-docx, and includes references (resource) components.

What problem does it solve?

This Skill eliminates the manual effort and formatting errors associated with preparing patent applications for different international jurisdictions, ensuring compliance with specific filing standards.

Core Features & Use Cases

Multi-Jurisdiction Formatting: Automatically compiles patent documents into CNIPA, USPTO, or EPO compliant formats.
Consistency Enforcement: Ensures claims, descriptions, and abstracts adhere to jurisdiction-specific rules like the two-part claim form for EPO or specific terminology for CNIPA.
Use Case: A patent attorney needs to file a single invention disclosure in both the US and China; this tool generates the correctly formatted markdown or docx files for both offices simultaneously.

Quick Start

Run the jurisdiction-format skill to compile the current patent application into all required formats for CN, US, and EP filings.

Frequently Asked Questions about jurisdiction-format

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

FAQPage Schema

How do I automate patent filing document compilation for multiple jurisdictions?▼

Automate patent filing document compilation by running the skill to compile patent applications into jurisdiction-specific formats for CNIPA, USPTO, and EPO standards. It generates compliant markdown or docx files simultaneously, enforcing technical consistency across all required filing formats.

What is the best way to format patent claims for EPO and CNIPA compliance?▼

The best way to format patent claims for EPO and CNIPA compliance is to use predefined regional rules that enforce specific structural requirements, such as the two-part claim form for EPO or specific terminology for CNIPA. This ensures claims adhere to mandatory legal formatting.

Can I generate USPTO and CNIPA patent applications from a single invention disclosure?▼

Yes, you can generate USPTO and CNIPA patent applications from a single invention disclosure. The tool compiles the disclosure into correctly formatted markdown or docx files for both offices simultaneously, ensuring technical consistency across multiple filing formats.

Does python-docx support exporting compiled patent applications into docx format?▼

Yes, python-docx supports exporting compiled patent applications into docx format. As a dependency, it enables the automated generation of formatted claims, specifications, and abstracts into docx files while ensuring technical consistency across multiple filing formats.

Why do patent filings get rejected for formatting errors across different jurisdictions?▼

Patent filings get rejected for formatting errors due to manual effort failing to meet specific regional filing standards. This skill eliminates manual errors by enforcing jurisdiction-specific rules like the EPO two-part claim form and CNIPA terminology, ensuring compliance.