ablation-planner
Use when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
Process user-provided patent figures and generate formal drawing descriptions. Use when user says \"附图处理\", \"figure description\", \"附图说明\", \"drawings description\", or wants to describe patent figures with reference numerals.
$ npx -y skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill figure-description --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/figure-descriptionContext preview
The summary Claude sees to decide when to auto-load this skill.
Process user-provided patent figures and generate formal drawing descriptions. Use when user says \"附图处理\", \"figure description\", \"附图说明\", \"drawings description\", or wants to describe patent figures with reference numerals.
name: figure-description description: "Process user-provided patent figures and generate formal drawing descriptions. Use when user says \"附图处理\", \"figure description\", \"附图说明\", \"drawings description\", or wants to describe patent figures with reference numerals." argument-hint: "[figure-directory-or-figure-list]" allowed-tools: Bash(*), Read, Write, Edit, Grep, Glob, WebSearch, WebFetch
Process patent figures and generate drawing descriptions based on: **$ARGUMENTS**
Unlike `/paper-figure` which generates data plots, this skill processes user-provided technical diagrams and assigns reference numerals.
1. User-provided figures (PNG, JPG, SVG, PDF) — search for them in the project directory 2. `patent/INVENTION_DISCLOSURE.md` — for understanding what components to identify 3. `patent/CLAIMS.md` — for mapping numerals to claim elements
1. Search the project directory for figure files:
2. List all discovered figures with their paths 3. If figures are missing that claims require, note them as `[MISSING: description needed]`
For each figure found:
1. **Read the image** using the Read tool (supports image files) 2. **Identify components**: What labeled or visually distinct components are shown? 3. **Identify connections**: How do components relate to each other? 4. **Identify flow**: If it's a flowchart or sequence, what is the step order?
For each figure, assign numerals using the series convention:
| Figure | Numeral Range | |--------|-------------| | FIG. 1 | 100-199 | | FIG. 2 | 200-299 | | FIG. 3 | 300-399 |
For each identified component:
Write formal drawing descriptions (附图说明):
**For CN jurisdiction (Chinese)**:
图1是[发明名称]的系统结构示意图; 图2是[发明名称]的方法流程图; 图3是[具体组件]的详细结构示意图;
**For US/EP jurisdiction (English)**:
FIG. 1 is a block diagram illustrating the system architecture according to one embodiment; FIG. 2 is a flowchart illustrating the method steps according to one embodiment; FIG. 3 is a detailed view of the processing module of FIG. 1;
Create a complete mapping:
## Reference Numeral Index | Numeral | Component Name | Figure(s) | Claim Element | |---------|---------------|-----------|---------------| | 100 | System | FIG. 1 | Claim X preamble | | 102 | Processor | FIG. 1 | Claim X, element 1 | | 104 | Memory | FIG. 1 | Claim X, element 2 | | 106 | Communication bus | FIG. 1 | Claim X, element 3 | | 200 | Method | FIG. 2 | Claim 1 preamble | | 202 | Receiving step | FIG. 2 | Claim 1, step 1 | | 204 | Processing step | FIG. 2 | Claim 1, step 2 |
Verify that every claim element has at least one reference numeral:
| Claim Element | Figure | Numeral | Status | |---------------|--------|---------|--------| | [element] | [which fig] | [numeral] | Covered / [MISSING] |
If any claim element has no corresponding figure or numeral, flag it:
Write `patent/figures/figure_descriptions.md`:
## Figure Descriptions ### FIG. 1 — [Description] [Formal one-paragraph description with all reference numerals] ### FIG. 2 — [Description] [Formal one-paragraph description with all reference numerals] ...
Write `patent/figures/numeral_index.md`:
## Reference Numeral Index [Complete table of all numerals, components, figures, and claim mappings]
· · · · · · -orange?style=flat) · · 💬 Join Community · 💡 Use ARIS as a skill-based workflow in Claude Code / Codex CLI / Cursor / Trae / Antigravity / GitHub Copilot CLI / OpenClaw / DeepSeek Harness, or get the full experience with the standalone ARIS-Code
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 paper", "summarize paper", pastes…
Analyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results", "compare", or needs to…
Search, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv", "arxiv search", "get paper…
Autonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user says \"改论文\", \"improve paper\",…
Autonomous research review loop using any OpenAI-compatible LLM API. Configure via llm-chat MCP server or environment variables. Trigger with "auto review loop…