figure-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.
85
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-crafted description with strong trigger terms in both Chinese and English, a clear 'Use when' clause, and a distinctive niche that minimizes conflict risk. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., extracting reference numerals, formatting descriptions per patent office standards).
Suggestions
Add more specific concrete actions to the 'what' portion, e.g., 'extract reference numerals from figures, map numerals to component names, and generate formatted drawing descriptions per patent office standards.'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (patent figures) and two actions (process figures, generate drawing descriptions), but doesn't elaborate on specific sub-actions like extracting reference numerals, formatting output, or handling multiple figure types. | 2 / 3 |
Completeness | Clearly answers both 'what' (process patent figures and generate formal drawing descriptions) and 'when' (explicit 'Use when' clause with specific trigger phrases and a broader condition about describing patent figures with reference numerals). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms in both Chinese ('附图处理', '附图说明') and English ('figure description', 'drawings description'), plus the conceptual trigger 'reference numerals' and 'patent figures'. Good coverage of terms users would actually say. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — patent figure descriptions with reference numerals is very specific and unlikely to conflict with other skills. The bilingual trigger terms further narrow the scope. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill with strong actionability and workflow clarity. The 7-step process is logically sequenced with validation checkpoints, concrete output formats, and clear rules. The main weaknesses are moderate verbosity (some sections could be tighter) and the monolithic structure that could benefit from splitting detailed templates into reference files.
Suggestions
Trim the introductory comparison to /paper-figure and tighten the Discover Figures step by removing obvious search locations Claude would check anyway.
Consider extracting the jurisdiction-specific description templates and the reference numeral index template into separate reference files to improve progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably well-structured but includes some content that could be tightened. The examples in Steps 4 and 5 are helpful but somewhat verbose, and the distinction from `/paper-figure` is unnecessary context. The constants section and input section add useful information concisely, but the overall document could be trimmed by ~20%. | 2 / 3 |
Actionability | The skill provides highly concrete, actionable guidance: specific numeral ranges, exact file paths for output, complete table formats for the reference numeral index, example formal descriptions in both CN and EN jurisdictions, and explicit cross-referencing steps. The output format is copy-paste ready with clear markdown templates. | 3 / 3 |
Workflow Clarity | The 7-step workflow is clearly sequenced with logical progression from discovery through analysis, assignment, generation, cross-referencing, and output. Step 6 serves as an explicit validation checkpoint that flags missing figures and numerals, creating a feedback loop. The cross-reference verification table ensures completeness before final output. | 3 / 3 |
Progressive Disclosure | The content is well-organized with clear sections and headers, but everything is in a single monolithic file with no references to supporting documents. The reference numeral index template, jurisdiction-specific examples, and cross-reference tables could be split into separate reference files. However, given no bundle files exist, the inline approach is somewhat justified. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
2028ac4
- Reviewed
Table of Contents
Is this your skill?
If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.