jurisdiction-format
Compile patent application into jurisdiction-specific filing format.
Skill by wanshuiyin
Chalk Labs
Need help deploying jurisdiction-format?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.
npx agentmarket install skill/wanshuiyin-jurisdiction-format
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.
- Tools
- No tools found
- Secrets
- None asked for
- Install scripts
- None found
Network hosts it talks to 1
codeload.github.com· found in install command
Files it touches
~/.claude/skills/jurisdiction-format
Tools it pre-approves 6
From allowed-tools in SKILL.md: the agent may use these without asking you each time.
Bash(*),Read,Write,Edit,Grep,Glob
What's inside
- Skill 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.
- License
- MIT
- Allowed tools
- Bash(*),, Read,, Write,, Edit,, Grep,, Glob
- Instructions
- 187 lines in SKILL.md · view on GitHub
Before installing
- Pre-approves some shell commands
Files (1)
- SKILL.md
SKILL.md (first lines)
# 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 ArtFrom wanshuiyin/Auto-claude-code-research-in-sleep, MIT.
Signals
- Stars
- 18,007
- Forks
- 1,488
- Open issues
- 58
- Last commit (this folder)
- Jul 13, 2026 (4 months ago)
- Last release
- Sep 28, 2026 (1 month ago)
From GitHub (fetched Oct 24, 2026).
Details
- License
- MIT
- First seen
- Oct 24, 2026
- Last checked
- Oct 24, 2026
- Source
- GitHubgithub-graphql
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get jurisdiction-format running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
jurisdiction-format skill. Agent Mart. https://agentmart.dev/skills/wanshuiyin-jurisdiction-format (last updated 2026-10-24)