Mmcp.market

figure-description skill

by wanshuiyin·wanshuiyin/Auto-claude-code-research-in-sleep·17k stars·MIT

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.

A100/100content scan

Is the figure-description skill safe?

Clean: nothing in its files matched our rules. We read 1 file in the folder on 2026-09-28.

No findings.

Install the figure-description skill

A skill is a folder. Copy it into your agent's skills folder and the agent loads it when the task matches its description.

git clone --depth 1 https://github.com/wanshuiyin/Auto-claude-code-research-in-sleep.git /tmp/Auto-claude-code-research-in-sleep
mkdir -p ~/.claude/skills
cp -r /tmp/Auto-claude-code-research-in-sleep/skills/skills-codex/figure-description ~/.claude/skills/figure-description
available in every project

In the Claude apps, zip the folder and upload it from the Skills settings. The folder on GitHub

The instructions your agent would load

SKILL.md as published, without the frontmatter. Read it on GitHub

Figure Description for Patents

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.

Constants

  • FIGURE_DIR = "patent/figures/" — Output directory for figure descriptions
  • REFERENCENUMERALPREFIX = 100 — Starting numeral for first figure's components
  • NUMERAL_SERIES = 100 — Each figure uses a separate 100-series (Fig 1: 100-199, Fig 2: 200-299, etc.)

Inputs

  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

Workflow

Step 1: Discover Figures

  1. Search the project directory for figure files:
  • Check patent/figures/, figures/, root directory
  • Look for PNG, JPG, SVG, PDF files
  • Check INVENTIONBRIEF.md or INVENTIONDISCLOSURE.md for figure references
  1. List all discovered figures with their paths
  2. If figures are missing that claims require, note them as [MISSING: description needed]

Step 2: Analyze Each Figure

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?

Step 3: Assign Reference Numerals

For each figure, assign numerals using the series convention:

For each identified component:

  • Assign the next available numeral in the series
  • Cross-reference to the claim elements it supports
  • Note if a component appears in multiple figures (use same numeral across figures)

Step 4: Generate Drawing Descriptions

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;

Step 5: Generate Reference Numeral Index

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 |

Step 6: Cross-Reference to Claims

Verify that every claim element has at least one reference numeral:

If any claim element has no corresponding figure or numeral, flag it:

  • [MISSING FIGURE: Need a diagram showing {element description}]
  • [MISSING NUMERAL: Component {name} in figure {X} needs a numeral]

Step 7: Output

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]

Key Rules

  • Every component in every figure must have a reference numeral.
  • Every reference numeral must be explained in the specification.
  • Numeral series must be consistent: 100-series for FIG. 1, 200-series for FIG. 2.
  • If the same component appears in multiple figures, use the SAME numeral.
  • Do NOT modify user-provided figures -- only describe them.
  • Flag missing figures that the claims require but the user has not provided.
  • Drawing descriptions are one sentence each, in a consistent format.

More skills from wanshuiyin/Auto-claude-code-research-in-sleep

  • Aablation-plannerUse when main results pass result-to-claim (claim_supported=yes or partial) and ablation studies are needed for paper submission.
  • Aablation-plannerUse when main results pass result-to-claim (`claim_supported = yes` or `partial`) and ablation studies are needed for paper submission. A secondary Codex agent designs ablations from a reviewer's perspective; the local executor reviews feasibility and implements.
  • AalphaxivQuick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this paper", "summarize paper", pastes an arXiv/AlphaXiv URL, or provides a bare arXiv ID for quick understanding - not for broad literature search.
  • AalphaxivQuick single-paper lookup via AlphaXiv LLM-optimized summaries with tiered source fallback. Use when user says "explain this paper", "summarize paper", pastes an arXiv/AlphaXiv URL, or provides a bare arXiv ID for quick understanding - not for broad literature search.
  • Aanalyze-resultsAnalyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says "analyze results", "compare", or needs to interpret experimental data.
  • Aanalyze-resultsAnalyze ML experiment results, compute statistics, generate comparison tables and insights. Use when user says \"analyze results\", \"compare\", or needs to interpret experimental data.
  • AarxivSearch, download, and summarize academic papers from arXiv. Use when user says "search arxiv", "download paper", "fetch arxiv", "arxiv search", "get paper pdf", or wants to find and save papers from arXiv to the local paper library.
  • AarxivSearch, download, and summarize academic papers from arXiv. Use when user says \"search arxiv\", \"download paper\", \"fetch arxiv\", \"arxiv search\", \"get paper pdf\", or wants to find and save papers from arXiv to the local paper library.
  • Aauto-paper-improvement-loopAutonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user says \"改论文\", \"improve paper\", \"论文润色循环\", \"auto improve\", or wants to iteratively polish a generated paper.
  • Aauto-paper-improvement-loopAutonomously improve a generated paper via Claude review through claude-review MCP → implement fixes → recompile, for 2 rounds. Use when user says \"改论文\", \"improve paper\", \"论文润色循环\", \"auto improve\", or wants to iteratively polish a generated paper.
  • Aauto-paper-improvement-loopAutonomously improve a generated paper via Gemini review through gemini-review MCP → implement fixes → recompile, for 2 rounds. Use when user says \"改论文\", \"improve paper\", \"论文润色循环\", \"auto improve\", or wants to iteratively polish a generated paper.
  • Aauto-paper-improvement-loopAutonomously improve a generated paper via GPT-6-Astra xhigh review → implement fixes → recompile, for 2 rounds. Use when user says \"改论文\", \"improve paper\", \"论文润色循环\", \"auto improve\", or wants to iteratively polish a generated paper.

All agent skills → · MCP servers