CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

61

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/figure-description/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%

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

A well-structured, self-contained workflow with concrete templates and an explicit verification step, but it is held back by duplicated content, open-ended analysis guidance, and the absence of a retry loop for flagged missing items.

Suggestions

Remove the duplicated Reference Numeral Index table — keep it only in the Step 7 output spec — and delete Key Rules entries that restate the numeral-series convention already defined in Constants and Step 3.

Tighten the per-figure analysis in Step 2 with concrete criteria (e.g., label detection, connector/arrow direction, numbered step order) instead of open-ended questions, so guidance is executable rather than interpretive.

Add a feedback loop after Step 6: when a claim element is flagged [MISSING FIGURE] or [MISSING NUMERAL], loop back to request or assign the missing item and re-run the cross-reference until no MISSING flags remain.

DimensionReasoningScore

Conciseness

The body is task-focused without teaching known concepts, but it duplicates content: the Reference Numeral Index table appears in both Step 5 and the Step 7 output spec, and the Key Rules section restate the numeral-series rules already given in Constants and Step 3.

2 / 3

Actionability

It provides concrete file paths, CN/US-EP templates, and table schemas, but the per-figure analysis steps ('Identify components: What labeled or visually distinct components are shown?') are open-ended guidance and the output templates rely on unfilled placeholders like [发明名称] and [Description].

2 / 3

Workflow Clarity

Seven clearly numbered steps with an explicit Step 6 verification cross-reference, but for a batch operation over multiple figures there is no fix-and-revalidate feedback loop — missing items are merely flagged as [MISSING] without a retry path.

2 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single SKILL.md is well-organized into Constants, Inputs, a seven-step Workflow, and Key Rules with no nested references, so navigation is straightforward.

3 / 3

Total

9

/

12

Passed

Description

90%

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, third-person description that clearly states its patent-figure purpose and provides explicit bilingual triggers for when to invoke it. The only weakness is modest action specificity, naming just two operations.

DimensionReasoningScore

Specificity

Names the domain ('patent figures') and two concrete actions ('Process... figures and generate formal drawing descriptions'), but stops at two actions rather than listing multiple specific operations like numeral assignment or claim cross-referencing.

2 / 3

Completeness

Explicitly answers what it does ('Process user-provided patent figures and generate formal drawing descriptions') and when to use it ('Use when user says...'), satisfying both halves with explicit triggers.

3 / 3

Trigger Term Quality

Covers natural user phrasing in both Chinese and English ('附图处理', 'figure description', '附图说明', 'drawings description', 'describe patent figures with reference numerals'), giving good coverage of terms a user would actually say.

3 / 3

Distinctiveness Conflict Risk

The patent-figure niche with bilingual reference-numeral triggers is clearly distinct from general figure or document skills and unlikely to fire for the wrong skill.

3 / 3

Total

11

/

12

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.

Validation14 / 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
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.