figure-description
Skill16 starsChanged 6 months agoMITView on GitHub
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.
5 other projects use a version of this, 3 of them edited.
Adopted by
Most recently taken up by
- talhaMah56/claude_skillsedited, first seen Sep 12, 2026
- wanshuiyin/Auto-claude-code-research-in-sleepedited, first seen Jul 15, 2026
- Immortalqx/my_codex_skillsedited, first seen Jun 10, 2026
- Chanw-research/claude-code-paper-writingword for word, first seen May 10, 2026
- raja21068/AutoResearchword for word, first seen May 5, 2026
Other versions5 projects use a version of this.
Word for word · 2
- Chanw-research/claude-code-paper-writing★ 42100% same
- raja21068/AutoResearch★ 2100% same
Edited · 3
- wanshuiyin/Auto-claude-code-research-in-sleep★ 19k100% same
- Immortalqx/my_codex_skills★ 5499% same
- talhaMah56/claude_skills★ 0100% same
Wrote their own version · 0
None found.
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository56 other files it gives its agents.
- argument-stress-testSkill
- citation-auditSkill
- comm-lit-review-claude-singleSkill
- comparative-lawSkill
- exa-searchSkill
- feishu-notifySkill
- figure-specSkill
- formula-derivationSkill
- grant-proposalSkill
- legal-writingSkill
- llm-wikiSkill
- mermaid-diagramSkill
- novelty-checkSkill
- overleaf-syncSkill
- paper-claim-auditSkill
- paper-compileSkill
- paper-figureSkill
- paper-illustrationSkill
- paper-planSkill
- paper-posterSkill
- paper-slidesSkill
- paper-writeSkill
- paper-writingSkill
- prism-pipelineSkill
- proof-checkerSkill
- proof-writerSkill
- rebuttalSkill
- research-litSkill
- research-pipelineSkill
- research-refine-pipelineSkill
- research-refineSkill
- research-reviewSkill
- research-wikiSkill
- semantic-scholarSkill
- comm-lit-reviewSkill
- feishu-notifySkill
- formula-derivationSkill
- grant-proposalSkill
- mermaid-diagramSkill
- novelty-checkSkill
- paper-compileSkill
- paper-figureSkill
- paper-illustrationSkill
- paper-planSkill
- paper-posterSkill
- paper-slidesSkill
- paper-writeSkill
- paper-writingSkill
- proof-writerSkill
- rebuttalSkill
- research-litSkill
- research-pipelineSkill
- research-refine-pipelineSkill
- research-refineSkill
- research-reviewSkill
- statute-case-mapperSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 11 are common, 0 are distinctive, and 3 are very specific to this project.
11
Common
Most of the 3 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Common: line 30
Search the project directory for figure files:
- Very specific: line 31
Check patent/figures/, figures/, root directory
- Common: line 32
Look for PNG, JPG, SVG, PDF files
- Very specific: line 33
Check INVENTION_BRIEF.md or INVENTION_DISCLOSURE.md for figure references
- Very specific: line 35
If figures are missing that claims require, note them as [MISSING: description needed]
- Common: line 44
Identify flow: If it's a flowchart or sequence, what is the step order?
- Common: line 63
Write formal drawing descriptions (附图说明):
- Common: line 81
Create a complete mapping:
- Common: line 99
Verify that every claim element has at least one reference numeral:
- Common: line 105
If any claim element has no corresponding figure or numeral, flag it:
- Common: line 132
Every component in every figure must have a reference numeral.
- Common: line 133
Every reference numeral must be explained in the specification.
- Common: line 135
If the same component appears in multiple figures, use the SAME numeral.
- Common: line 136
Do NOT modify user-provided figures -- only describe them.
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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 descriptionsREFERENCE_NUMERAL_PREFIX = 100— Starting numeral for first figure's componentsNUMERAL_SERIES = 100— Each figure uses a separate 100-series (Fig 1: 100-199, Fig 2: 200-299, etc.)
Inputs
- User-provided figures (PNG, JPG, SVG, PDF) — search for them in the project directory
patent/INVENTION_DISCLOSURE.md— for understanding what components to identifypatent/CLAIMS.md— for mapping numerals to claim elements
Workflow
Step 1: Discover Figures
- 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
- Check
- List all discovered figures with their paths
- If figures are missing that claims require, note them as
[MISSING: description needed]
Step 2: Analyze Each Figure
For each figure found:
- Read the image using the Read tool (supports image files)
- Identify components: What labeled or visually distinct components are shown?
- Identify connections: How do components relate to each other?
- 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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

