Guide · Agent skill
How to use the Jurisdiction Patent Formatter agent skill
Updated · written with AI from the project's own documentation and checked against our catalogue data
The Jurisdiction Patent Formatter is an agent skill, named jurisdiction-format, that tells an AI agent how to take a patent draft you already have and lay it out in the format used by the Chinese (CNIPA), US (USPTO) or European (EPO) patent office. This guide explains what the skill does, how to install it, how to ask for it in plain language, and what you need to prepare before you run it. Patent professionals should review every output before filing.
Quick start
- 1Download and unzip. Download the skill ZIP from this page and unzip it into ~/.claude/skills/ or the project's .claude/skills/ folder.
- 2Gather your patent files. Put your claims, specification sections, figures index and invention disclosure in a patent/ folder.
- 3Add the shared references. Place patent-format-cn.md, patent-format-us.md and patent-format-ep.md at ../shared-references/, since they are not included in the download.
- 4Ask for the jurisdiction. Request CN, US, EP or ALL in plain language, or use the argument hint with the patent directory.
- 5Review the output. Check patent/output/ and OUTPUT_SUMMARY.md, then have a patent attorney verify everything before filing.
What the jurisdiction-format skill makes the agent do
An agent skill is a folder containing a SKILL.md file with instructions. When the skill is active, the agent follows those instructions for matching tasks. This skill covers one task: compiling an existing patent application into filing-ready documents for a specific office.
The skill reads your claims, specification sections, and metadata, then reorders sections, applies numbering, and adjusts wording to each office's conventions. Its stated rule is that it reformats content only and does not modify claim content.
- CN (CNIPA): claims in Chinese with the 其特征在于 form, and a description in CNIPA section order.
- US (USPTO): numbered claims using 'The method of claim 1, wherein...' style, a specification in USPTO order, and a skeleton Application Data Sheet.
- EP (EPO): claims in two-part form with 'characterised in that', and a description in EPO order ending with a Reference Signs List.
- Each office gets its own folder, plus a summary file and a consistency checklist.
Install the jurisdiction-format skill
Download the skill ZIP from this page. You can install it for yourself across all projects, or for one project only.
For a personal install, unzip the file into ~/.claude/skills/. For a single project, unzip it into the project's .claude/skills/ folder. Either way, the skill folder should contain SKILL.md.
If you use the Claude apps instead, open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Personal: ~/.claude/skills/
- Project only: the project's .claude/skills/ folder
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP
~/.claude/skills/Prepare your input files before you run it
The skill assumes the patent draft already exists. It does not write claims or specification text from scratch. Organise your files in a patent/ folder with these inputs.
Two requirements are easy to miss. The shared reference files (patent-format-cn.md, patent-format-us.md, patent-format-ep.md) must sit at ../shared-references/ relative to the skill, and the source says they are not included in the provided file. Without them, the skill cannot load the office rules. Python with python-docx is needed only if you choose docx output.
- patent/CLAIMS.md: drafted claims
- patent/specification/: title, technical_field, background, summary, drawings_description, detailed_description and abstract sections
- patent/figures/: figure descriptions and numeral index
- patent/INVENTION_DISCLOSURE.md: metadata
- ../shared-references/: patent-format-cn.md, patent-format-us.md and patent-format-ep.md (not included in the download)
Trigger the skill with natural requests
You can invoke the skill with its argument hint, which accepts a patent directory or a jurisdiction. You can also simply describe what you want. The skill's description lists these trigger phrases: 格式转换, jurisdiction format, 国家格式, compile patent, and requests for formatted patent documents for CN, US or EP filing.
If you do not name a jurisdiction, the skill's constant is set to auto, so state the office in your request to be sure. The skill accepts CN, US, EP or ALL.
- "Format my patent in patent/ for USPTO filing."
- "Compile patent for CN and EP."
- "国家格式: generate all three jurisdictions."
- "Jurisdiction format this application for EP only."
/jurisdiction-format [patent-directory-or-jurisdiction]Understand the output files and checks
Files are written to patent/output/, with subfolders CN, US and EP. The skill also writes patent/output/OUTPUT_SUMMARY.md, which lists each file and includes a consistency checklist: all claims present in every format, claim numbering consistent, reference numerals matching across formats, no format-specific rules broken, and correct language per jurisdiction.
Output is Markdown by default, which the skill describes as suitable for review. Docx output is for filing and needs python-docx. If python-docx is not available, the skill is instructed to fall back to Markdown.
- CN: 权利要求书.md, 说明书.md, 说明书摘要.md
- US: claims.md, specification.md, abstract.md, ads_template.md
- EP: claims.md, description.md, abstract.md
- Summary: OUTPUT_SUMMARY.md
Safety notes: scripts, permissions and review
The skill's tool permissions include Bash(*), along with Read, Write, Edit, Grep and Glob. That means the agent can run shell commands while it works, so read the SKILL.md before installing and run the skill on a copy of your files if you are cautious. The listing states that the skill runs scripts and does not use the network.
The skill checks formatting and consistency. It does not check legal sufficiency or novelty, and its own rules describe output as needing review. Have a qualified patent attorney verify the filing documents before you file, because formatting errors or missed requirements can affect a filing.
- Read SKILL.md before installing.
- Work on a copy of your patent folder if you are unsure.
- Treat all output as a draft until a patent professional has reviewed it.
What people use it for
- Converting a finished draft into Chinese claims and description files for CNIPA filing.
- Producing a USPTO specification, claims and skeleton Application Data Sheet from the same draft.
- Preparing EP claims in two-part form with a Reference Signs List for a European filing.
- Generating all three office formats at once for an invention being filed in several jurisdictions.
Frequently asked questions
Is the jurisdiction-format skill free to use?
The source material provided does not state a price or licence terms for the skill beyond the listed MIT licence. Check the licence text in the repository before using it commercially.
What do I need to run the jurisdiction-format skill?
You need a drafted patent in a patent/ folder layout, the three shared reference files at ../shared-references/, and an agent environment that loads skills. Python with python-docx is needed only for docx output.
Does the skill write my patent claims?
No. The skill assumes the input files already exist and reformats existing content. It states that it does not modify claim content.
Where do I install the skill?
Unzip it into ~/.claude/skills/ for personal use or into a project's .claude/skills/ folder for one project. In the Claude apps, upload the ZIP under Settings → Capabilities → Skills.
Why does my output folder have no reference rules applied?
The shared reference files are not included in the download. If they are missing from ../shared-references/, the skill cannot load the CNIPA, USPTO and EPO rules, so add them before running the skill.
Can I use this instead of a patent attorney?
No. The skill does not check legal sufficiency or novelty, and formatting errors can affect a filing, so a qualified patent attorney should verify the output.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
This skill suits inventors and patent agents who already have a drafted application and need it laid out for CNIPA, USPTO or EPO filing, especially teams filing one invention in several offices. It is not a drafting tool and does not judge legal sufficiency, so choose a different approach if you need help writing claims or assessing novelty.
Download the skill