CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

The canonical home for this skill is figure-description in wanshuiyin/Auto-claude-code-research-in-sleep

SKILL.md
Quality
Evals
Security

Quality

Content

75%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, actionable single-file skill with clear sequencing and genuine validation checkpoints (missing-figure and missing-numeral flagging). Its weaknesses are modest: a triple-stated numeral convention, no guidance for choosing between the CN and US/EP description templates, and no remediation path for flagged missing figures or numerals.

Suggestions

Add one line stating how to select the jurisdiction template in Step 4 (e.g., derive from the language of patent/CLAIMS.md or an explicit --jurisdiction argument), since both CN and US/EP templates are given but the choice criterion is never specified.

Deduplicate the numeral-series convention: state it once in Constants and have Step 3 and Key Rules reference it, rather than explaining the 100/200/300 ranges in three places.

Add a brief remediation step after Step 6 for flagged items (e.g., generate placeholder descriptions or ask the user for the missing figures) so the validation loop closes instead of only recording MISSING flags.

DimensionReasoningScore

Conciseness

The body is tight — constants, tables, and one-line rules with no padding of concepts Claude already knows. Minor trimmable redundancy exists: the numeral-series convention is explained three times ("NUMERAL_SERIES = 100" in Constants, the table in Step 3, and "Numeral series must be consistent" in Key Rules), keeping it just below the 'lean and efficient' anchor.

4 / 5

Actionability

Guidance is largely executable: exact output paths ("patent/figures/figure_descriptions.md"), copy-paste formal sentence templates for both jurisdictions, and concrete table schemas for the numeral index and claim cross-reference. The main gap is that Step 4 provides CN and US/EP templates but never states how to determine which jurisdiction applies, a missing key detail for execution.

4 / 5

Workflow Clarity

Seven well-sequenced steps with explicit validation checkpoints: Step 1 flags figures missing relative to claims and Step 6 verifies "every claim element has at least one reference numeral" with MISSING flags. It falls short of the score-5 anchor because there is no error-recovery loop — flagged items are recorded but no step says what to do next — and the jurisdiction-selection decision point is implicit.

4 / 5

Progressive Disclosure

No bundle files exist and none are referenced; the single-file body is organized into clear headed sections (Constants, Inputs, Workflow steps, Key Rules) of appropriate length for one-level content. Structure is good but a couple of sections (e.g., the two output templates and jurisdiction variants) would sit equally well in a reference file, so it matches 'good structure; minor organization gaps' rather than optimal.

4 / 5

Total

16

/

20

Passed

Description

95%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description: concrete domain-specific actions, explicit 'Use when' triggers with bilingual synonyms, and a clearly bounded niche. The only gap is that the description under-sells the skill's numeral-assignment and claim-mapping work, which is its most distinctive capability.

DimensionReasoningScore

Specificity

"Process user-provided patent figures and generate formal drawing descriptions" names the domain plus concrete actions, and "describe patent figures with reference numerals" adds a third capability. It stops short of comprehensive coverage — numeral assignment conventions and claim cross-referencing (core to the skill) are not mentioned — so it matches 'several specific actions; minor gaps' rather than the score-5 comprehensive anchor.

4 / 5

Completeness

It explicitly answers both questions: what ("Process user-provided patent figures and generate formal drawing descriptions") and when ("Use when user says '附图处理', 'figure description', ..."), with concrete quoted trigger phrases matching the score-5 anchor exactly.

5 / 5

Trigger Term Quality

The description lists natural trigger phrases in both languages users would actually say: "figure description", "drawings description", "附图处理", "附图说明", plus a plain-language trigger ("wants to describe patent figures with reference numerals"). This is comprehensive synonym coverage for the domain; file extensions are irrelevant here since the skill triggers on task phrasing, not file type.

5 / 5

Distinctiveness Conflict Risk

The niche is clear — patent figures, formal drawing descriptions, reference numerals — with distinct bilingual trigger terms that no adjacent skill (e.g., data-plot figure generation) would naturally claim. "User-provided patent figures" further narrows it against figure-generation skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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

14

/

16

Passed

Repository

wanshuiyin/Auto-claude-code-research-in-sleep

Path

skills/skills-codex/figure-description/SKILL.md

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.