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.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Compile the patent application into filing-ready format based on: $ARGUMENTS
Analogous to /paper-compile but for patent document formatting instead of LaTeX.
JURISDICTION = "auto" — From pipeline or args: CN, US, EP, ALLPATENT_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 directorypatent/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 metadataLoad ../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.
From $ARGUMENTS or constant:
CN -> Generate CNIPA format onlyUS -> Generate USPTO format onlyEP -> Generate EPO format onlyALL -> Generate all three formatsOutput to patent/output/CN/:
patent/CLAIMS.mdCombine all specification sections in CNIPA order:
If OUTPUT_FORMAT = "markdown":
If OUTPUT_FORMAT = "docx":
Output to patent/output/US/:
Combine all sections in USPTO order:
Format drawings references as "FIG. 1" (not "Figure 1").
Generate a skeleton ADS with:
Output to patent/output/EP/:
Combine all sections in EPO Rule 42 order:
Format drawings references as "FIG. 1" or "Figure 1".
Verify across all generated formats:
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 jurisdictionOUTPUT_FORMAT = "docx", check that python-docx is available; if not, fall back to markdown.2028ac4
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.