ablation-planner
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
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.
Claude Code
$ npx -y skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format --agent claude-code
Codex
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format -a codex -y
Cursor
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format -a cursor -y
Gemini CLI
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format -a gemini-cli -y
GitHub Copilot
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format -a github-copilot -y
OpenCode
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format -a opencode -y
Windsurf
$ npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill jurisdiction-format -a windsurf -y
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
Compile the patent application into filing-ready format based on: **$ARGUMENTS**
Analogous to `/paper-compile` but for patent document formatting instead of LaTeX.
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
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.
From `$ARGUMENTS` or constant:
Output to `patent/output/CN/`:
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)
If `OUTPUT_FORMAT = "markdown"`:
If `OUTPUT_FORMAT = "docx"`:
Output to `patent/output/US/`:
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").
Generate a skeleton ADS with:
Output to `patent/output/EP/`:
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".
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 jurisdiction
· · · · · · · · 💬 Join Community · 🌱 ARIS is a methodology, not a platform. What matters is the research workflow — take it wherever you go.
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
Quick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this…
Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results",…
Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv",…
Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user…
Autonomous research review loop using any OpenAI-compatible LLM API. Configure via llm-chat MCP server or environment variables.…
Direct browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work. Also covers…
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling…