jurisdiction-format
Compile patent application into jurisdiction-specific filing format
Install / Use
npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-formatInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Content & MediaSupported Platforms
Tags
Our assessment of jurisdiction-format
jurisdiction-format scores 90/100 on our quality scale, 92nd of 399 Content & Media skills we index (top 24%).
Its SKILL.md is 6.4 KB long, well organised into 29 sections with 1 code example: a thorough specification that gives an agent plenty to work with.
With 16,644 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated 7 days ago, so jurisdiction-format is actively maintained.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.
Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
jurisdiction-format compared with similar skills
All 4 of these similar skills score higher than jurisdiction-format; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| jurisdiction-format (this skill)by wanshuiyin | 90 | 16.6k | 7d ago | SKILL.md |
| siyuanby siyuan-note | 100 | 46.5k | today | MCP Server |
| algorithmic-artby anthropics | 100 | 177.9k | 3d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 3d ago | SKILL.md |
| designby nextlevelbuilder | 100 | 130.2k | 4d ago | SKILL.md |
Frequently asked questions
- How do I install jurisdiction-format?
- Run
npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format. The install tabs above show the steps for each supported agent. - Which AI agents does jurisdiction-format work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is jurisdiction-format safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is jurisdiction-format still maintained?
- The repository was last updated 7 days ago, so jurisdiction-format is actively maintained.
Skill content
View source on GitHubname: jurisdiction-format description: "Compile patent application into jurisdiction-specific filing format. Use when user says "格式转换", "jurisdiction format", "国家格式", "compile patent", or wants formatted patent documents for CN/US/EP filing." argument-hint: "[patent-directory-or-jurisdiction]" allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob
Jurisdiction 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.
Related Skills
siyuan
46.5kAn open-source, privacy-first, self-hosted knowledge workspace where humans and AI agents work together 开源、隐私优先、自托管的知识工作空间,让人与智能体在此协作
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way — as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an em…
design
130.2kComprehensive design skill: brand identity, design tokens, UI styling, logo generation (55 styles, Gemini, Atlas Cloud, or MuAPI AI), corporate identity program (50 deliverables, CIP mockups), HTML presentations (Chart.js), banner design (22 styles, social/ads/web/print), icon design (15 styles, SVG…
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
