SkillAgentSearch skills...

figure-description

Process user-provided patent figures and generate formal drawing descriptions

Install / Use

npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill figure-description

Installs into whichever agent you are using.

About this skill
📄

SKILL.md

Installable skill definition

Quality Score

90/100

Supported Platforms

Universal

Tags

Our assessment of figure-description

figure-description scores 90/100 on our quality scale, 372nd of 1,999 Development & Engineering skills we index (top 19%).

Its SKILL.md is 4.8 KB long, well organised into 17 sections with 5 code examples: a solid amount of guidance for an agent.

With 16,644 GitHub stars, it is one of the more widely adopted skills in the catalogue.

Substance
26/30
Structure
20/20
Description
12/15
Adoption
18/20
Freshness
15/15

Maintenance, license and trust

  • The repository was last updated 7 days ago, so figure-description is actively maintained.
  • It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
  • Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.

Safety scan

No issues found

Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands.

Automated pattern scan on 2026-09-26. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.

figure-description compared with similar skills

All 4 of these similar skills score higher than figure-description; compare them before choosing.

SkillScoreStarsUpdatedFormat
figure-description (this skill)by wanshuiyin9016.6k7d agoSKILL.md
ai-job-searchby MadsLorentzen10044.0k5d agoCLAUDE.md
claude-howtoby luongnv8910041.7ktodayCLAUDE.md
algorithmic-artby anthropics100177.9k3d agoSKILL.md
pptxby anthropics100177.9k3d agoSKILL.md

Frequently asked questions

How do I install figure-description?
Run npx skills add wanshuiyin/Auto-claude-code-research-in-sleep --skill figure-description. The install tabs above show the steps for each supported agent.
Which AI agents does figure-description work with?
It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
Is figure-description safe to use?
Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
Is figure-description still maintained?
The repository was last updated 7 days ago, so figure-description is actively maintained.

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

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
  • REFERENCE_NUMERAL_PREFIX = 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 INVENTION_BRIEF.md or INVENTION_DISCLOSURE.md for figure references
  2. List all discovered figures with their paths
  3. 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:

| Figure | Numeral Range | |--------|-------------| | FIG. 1 | 100-199 | | FIG. 2 | 200-299 | | FIG. 3 | 300-399 |

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:

| Claim Element | Figure | Numeral | Status | |---------------|--------|---------|--------| | [element] | [which fig] | [numeral] | Covered / [MISSING] |

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.

Related Skills

View on GitHub
GitHub Stars16.6k
CategoryDevelopment
Updated7d ago
Forks1.4k

Languages

Python

Trust signals

100/100

From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.

No cautions