
Jurisdiction Format
FreeCompile patent applications into jurisdiction-specific formats.
Free · Opens the source repo
What Jurisdiction Format does
The Jurisdiction Format skill is designed to streamline the process of preparing patent applications for various jurisdictions including China (CN), the United States (US), and the European Patent Office (EP). This skill allows users to convert drafted patent documents into the required filing formats based on jurisdiction-specific guidelines. By simply providing the necessary input files and specifying the desired jurisdiction, users can generate formatted documents that comply with the respective patent office requirements.
This skill works by taking in various components of a patent application, such as claims, specifications, figures, and metadata, and formatting them according to the conventions of the selected jurisdiction. For example, when preparing a document for CN filing, the skill ensures that claims are structured in accordance with CNIPA rules, while for US filings, it adheres to USPTO standards. The output can be generated in either markdown for review purposes or docx for official filing, depending on user preference.
The Jurisdiction Format skill is particularly useful for patent attorneys, agents, and inventors who need to file applications across different jurisdictions. It eliminates the manual effort of formatting documents to meet specific legal standards, thereby reducing the risk of errors and ensuring compliance with local regulations. Users can easily switch between jurisdictions, making it a versatile tool for international patent filing.
By automating the formatting process, this skill not only saves time but also enhances the accuracy of patent applications. It is an essential tool for anyone involved in the patent filing process who requires jurisdiction-specific formatting for their documents.
When to use it
Use this skill when preparing patent applications for filing in CN, US, or EP jurisdictions.
When not to use it
This skill is not suitable for jurisdictions outside of CN, US, or EP or for non-patent document formatting.
What you can build with it
Preparing CN Patent Applications
Use this skill to format your patent application documents according to CNIPA standards for filing in China.
Filing US Patents
Quickly generate USPTO-compliant patent documents, ensuring all claims and specifications meet US requirements.
European Patent Office Submissions
Compile your patent application in the EPO format, adhering to the necessary rules and structure for successful filing.
How to install Jurisdiction Format
View source1. Install with the skills CLI
npx skills add wanshuiyin/auto-claude-code-research-in-sleep/jurisdiction-format --agent claude-code2. Or install it manually
Download the skill folder and drop it into ~/.claude/skills/ for all projects, or .claude/skills/ to scope it to one repo. Restart Claude Code so it picks up the new skill.
Anthropic's agentic coding CLI, and the reference implementation of Agent Skills. Drop a skill folder into ~/.claude/skills and Claude Code loads it automatically whenever a task matches the skill's description. Claude Code docs
Inside SKILL.md
Written by wanshuiyinJurisdiction Format: Patent Filing Compilation
Compile the patent application into filing-ready format based on: $ARGUMENTS
Analogous to /paper-compile but for patent document formatting instead of LaTeX.
Constants
JURISDICTION = "auto"— From pipeline or args:CN,US,EP,ALLPATENT_TYPE = "invention"—invention(发明专利) orutility_model(实用新型, CN only)OUTPUT_FORMAT = "markdown"—markdown(for review) ordocx(for filing, requires python-docx)OUTPUT_DIR = "patent/output/"— Base output directory
Inputs
patent/CLAIMS.md— drafted claimspatent/specification/— all specification sections (title, technical_field, background, summary, drawings_description, detailed_description, abstract)patent/figures/— figure descriptions and numeral indexpatent/INVENTION_DISCLOSURE.md— for metadata
Shared References
Load ../shared-references/patent-format-cn.md for CNIPA document structure and formatting rules.
Load ../shared-references/patent-format-us.md for USPTO document structure.
Load ../shared-references/patent-format-ep.md for EPO document structure.
Workflow
Step 1: Determine Output Jurisdictions
From $ARGUMENTS or constant:
CN-> Generate CNIPA format onlyUS-> Generate USPTO format onlyEP-> Generate EPO format onlyALL-> Generate all three formats
Step 2: Generate CN Format (if CN or ALL)
Output to patent/output/CN/:
权利要求书 (Claims)
- Extract claims from
patent/CLAIMS.md - Format per CNIPA conventions:
- Independent claims: "1. 一种[主题]的方法,...其特征在于..."
- Dependent claims: "2. 根据权利要求1所述的方法,其特征在于..."
- Ensure Chinese terminology is correct (所述, 其特征在于, 包括, 等)
说明书 (Description)
Combine all specification sections in CNIPA order:
- 发明名称 (from title.md)
- 技术领域 (from technical_field.md)
- 背景技术 (from background.md)
- 发明内容 (from summary.md — split into 技术问题/技术方案/有益效果)
- 附图说明 (from drawings_description.md)
- 具体实施方式 (from detailed_description.md)
说明书摘要 (Abstract)
- Extract from abstract.md
- Verify word count <= 300 Chinese characters
- Include most representative claim
Format as markdown or docx
If OUTPUT_FORMAT = "markdown":
- Write as separate .md files with clear section headers
If OUTPUT_FORMAT = "docx":
- Use python-docx to create Word documents matching CNIPA templates
- Set font to 宋体 (SimSun) for body, 黑体 (SimHei) for headers
- Standard margins (上下 2.54cm, 左右 3.17cm)
Step 3: Generate US Format (if US or ALL)
Output to patent/output/US/:
Claims Section
- Number all claims sequentially (1, 2, 3, ...)
- Format per US conventions:
- "1. A method for [purpose], comprising:"
- "2. The method of claim 1, wherein..."
- Ensure antecedent basis is correct ("a" -> "the")
Specification
Combine all sections in USPTO order:
- Title
- Cross-Reference to Related Applications (if any)
- Field of the Invention
- Background of the Invention
- Brief Summary of the Invention
- Brief Description of the Drawings
- Detailed Description of Preferred Embodiments
- Abstract
Format drawings references as "FIG. 1" (not "Figure 1").
Abstract
- Extract from abstract.md
- Verify word count <= 150 words / 2500 characters
Application Data Sheet (ADS) Template
Generate a skeleton ADS with:
- Title
- Inventor information (placeholder)
- Application type
- Entity status (small/micro/large)
Step 4: Generate EP Format (if EP or ALL)
Output to patent/output/EP/:
Claims Section
- Format in two-part form per Rule 43(1) EPC:
- "1. A method for [purpose], comprising [known features], characterised in that [inventive features]."
- Ensure the "characterised in that" phrase is present in all independent claims
Description
Combine all sections in EPO Rule 42 order:
- Title of the Invention
- Technical Field
- Background Art
- Disclosure of the Invention (problem-solution-advantage)
- Description of Embodiments
- Brief Description of Drawings
- Reference Signs List (mandatory at EPO)
Format drawings references as "FIG. 1" or "Figure 1".
Abstract
- Extract from abstract.md
- ~150 words limit
Step 5: Consistency Check
Verify across all generated formats:
- All claims are present in every format
- Claim numbering is consistent
- Reference numerals match specification across all formats
- No format-specific requirements are violated
- Language is correct for each jurisdiction (Chinese for CN, English for US/EP)
Step 6: Output Summary
Write patent/output/OUTPUT_SUMMARY.md:
## Patent Filing Documents
### Generated Files
#### CN (CNIPA)
| File | Description | Status |
|------|-------------|--------|
| 权利要求书.md | Claims in CN format | Complete |
| 说明书.md | Description in CN format | Complete |
| 说明书摘要.md | Abstract (CN) | Complete |
#### US (USPTO)
| File | Description | Status |
|------|-------------|--------|
| claims.md | Claims in US format | Complete |
| specification.md | Description in US format | Complete |
| abstract.md | Abstract (US) | Complete |
| ads_template.md | Application Data Sheet skeleton | Complete |
#### EP (EPO)
| File | Description | Status |
|------|-------------|--------|
| claims.md | Claims in EP format | Complete |
| description.md | Description in EP format | Complete |
| abstract.md | Abstract (EP) | Complete |
### Consistency Check
- [ ] All claims present in all formats
- [ ] Reference numerals consistent
- [ ] Language correct per jurisdiction
Key Rules
- Never mix jurisdiction formats (e.g., do not include "其特征在于" in US claims).
- Claims must be identical in technical content across jurisdictions, only the format differs.
- For CN output, verify Chinese patent terminology is correct and consistent.
- For EP output, the two-part claim form is mandatory -- every independent claim must have "characterised in that."
- Abstract word limits are jurisdiction-specific and must be verified.
- The jurisdiction-format skill does NOT modify claim content -- it reformats existing content only.
- If
OUTPUT_FORMAT = "docx", check that python-docx is available; if not, fall back to markdown.
Frequently asked questions about Jurisdiction Format
Similar skills
Markdown to HTML Conversion
Efficiently convert Markdown documents to HTML.
Code Tour
Create structured walkthroughs for codebases.
Acquire Codebase Knowledge
Streamline onboarding with comprehensive codebase documentation.
Documentation & Modernization
Streamline codebase documentation and modernization planning.
Azure Resource Visualizer
Generate architecture diagrams for Azure resources.
CLAUDE.md Improver
Optimize your CLAUDE.md files for better project context.
