Skip to content
Automation
Skill

/jurisdiction-format

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.

From plugin
aris
18k87 skills1 agent1 command

Claude Code

$ npx -y skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format --agent claude-code

SKILL.md

jurisdiction-format.SKILL.md
name: 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`, `ALL`
  • `PATENT_TYPE = "invention"` — `invention` (发明专利) or `utility_model` (实用新型, CN only)
  • `OUTPUT_FORMAT = "markdown"` — `markdown` (for review) or `docx` (for filing, requires python-docx)
  • `OUTPUT_DIR = "patent/output/"` — Base output directory

Inputs

1. `patent/CLAIMS.md` — drafted claims 2. `patent/specification/` — all specification sections (title, technical_field, background, summary, drawings_description, detailed_description, abstract) 3. `patent/figures/` — figure descriptions and numeral index 4. `patent/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 only
  • `US` -> Generate USPTO format only
  • `EP` -> Generate EPO format only
  • `ALL` -> 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: 1. 发明名称 (from title.md) 2. 技术领域 (from technical_field.md) 3. 背景技术 (from background.md) 4. 发明内容 (from summary.md — split into 技术问题/技术方案/有益效果) 5. 附图说明 (from drawings_description.md) 6. 具体实施方式 (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: 1. Title 2. Cross-Reference to Related Applications (if any) 3. Field of the Invention 4. Background of the Invention 5. Brief Summary of the Invention 6. Brief Description of the Drawings 7. Detailed Description of Preferred Embodiments 8. 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: 1. Title of the Invention 2. Technical Field 3. Background Art 4. Disclosure of the Invention (problem-solution-advantage) 5. Description of Embodiments 6. Brief Description of Drawings 7. 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 i
Read more
@wanshuiyin
Ships witharis

· · · · · · · · 💬 Join Community · 🌱 ARIS is a methodology, not a platform. What matters is the research workflow — take it wherever you go.

18k87 skills1 agent
Get the whole plugin

Stars on GitHub

Momentum

stars in total
18.3k
Star history of wanshuiyin/Auto-claude-code-research-in-sleep on GitHub, a chart by star-history.com

Other skills on aris.

ablation-planner

ablation-planner

Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.

@wanshuiyin@wanshuiyinInstall Skill
alphaxiv

alphaxiv

Quick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this…

@wanshuiyin@wanshuiyinInstall Skill
analyze-results

analyze-results

Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results",…

@wanshuiyin@wanshuiyinInstall Skill
arxiv

arxiv

Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv",…

@wanshuiyin@wanshuiyinInstall Skill
auto-paper-improvement-loop

auto-paper-improvement…

Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user…

@wanshuiyin@wanshuiyinInstall Skill
auto-review-loop-llm

auto-review-loop-llm

Autonomous research review loop using any OpenAI-compatible LLM API. Configure via llm-chat MCP server or environment variables.…

@wanshuiyin@wanshuiyinInstall Skill

More skills from other plugins.

agent-builder

agent-builder

Load immediately after an Agent intent, before the first agent_builder_* call. Governs how you create, configure, test, and…

n8n11d209k
@n8n-io@n8n-ioInstall Skill
browser-use

browser-use

Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…

@browser-use@browser-useInstall Skill
agent-browser

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…

@vercel-labs-2@vercel-labs-2Install Skill
add-anydoc

add-anydoc

Add local office-document-to-Markdown conversion to NanoClaw agent containers with the pinned Firecrawl AnyDoc CLI. Use when…

@nanocoai@nanocoaiInstall Skill

Questions about jurisdiction-format.

Which coding agents can use jurisdiction-format?
jurisdiction-format installs in Claude Code, Codex, Cursor, Gemini CLI, GitHub Copilot, OpenCode and Windsurf with the skills CLI, using each agent's flag shown on this page. Flowy's auto-invocation, which fires a skill when your prompt matches, runs in Claude Code only.