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

83%

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

SKILL.md
Quality
Evals
Security

Quality

Content

82%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, highly actionable instruction-only skill: concrete paths, templates, and output schemas for both CN and US/EP jurisdictions, plus an explicit claim-coverage verification step. Weaknesses are minor: triple-stated numeral-series rules and no remediation loop after missing-element flags.

Suggestions

State the numeral-series convention once (either the Constants block or the Key Rules) and reference it from the other location instead of repeating it in three places.

Add a short remediation step after Step 6 flagging, e.g. what to do when a [MISSING FIGURE] is found (skip, or report to the user for figure creation).

DimensionReasoningScore

Conciseness

The body is lean and assumes competence (no explanation of what patents or figures are), but the numeral-series convention is stated three times (Constants NUMERAL_SERIES, the FIG. 1/2/3 range table, and Key Rules "Numeral series must be consistent: 100-series for FIG. 1, 200-series for FIG. 2"), which is trimmable redundancy — anchor 4, not 5.

4 / 5

Actionability

Fully concrete guidance throughout: exact paths (patent/figures/figure_descriptions.md, patent/CLAIMS.md), copy-paste templates for both CN and US/EP jurisdictions, complete numeral-index and claim-mapping table schemas, and exact output file structures — matching anchor 5's copy-paste-ready standard for an instruction-only skill.

5 / 5

Workflow Clarity

A clear 7-step sequence with a real validation checkpoint (Step 6: "Verify that every claim element has at least one reference numeral" with [MISSING FIGURE]/[MISSING NUMERAL] flags), but there is no feedback loop telling Claude what to do after a flag (no remediate-and-re-verify step), so it stops short of anchor 5.

4 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the single file is coherently organized with well-labeled sections sized appropriately for inline content; it exceeds the <50-line simple-skill exception and contains some consolidatable duplicated material, fitting anchor 4 rather than 5.

4 / 5

Total

17

/

20

Passed

Description

78%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 with an explicit what/when structure and natural bilingual trigger phrases targeted at patent drafting. Its main weakness is incomplete coverage of the skill's concrete capabilities (numeral indexing and claim mapping are absent from the description).

Suggestions

Extend the 'what' clause to mention assigning reference numerals and mapping them to claim elements, e.g. 'assign reference numerals and cross-reference them to claim elements'.

Add a couple of common trigger variants such as 'patent drawings' or '附图标记' to widen natural-term coverage.

DimensionReasoningScore

Specificity

"Process user-provided patent figures and generate formal drawing descriptions" names the domain and 2-3 concrete actions, but omits significant capabilities the skill actually has (reference numeral index generation, claim cross-referencing), so coverage is not comprehensive as anchor 5/4 require.

3 / 5

Completeness

Explicitly answers both: what ("Process user-provided patent figures and generate formal drawing descriptions") and when ("Use when user says \"附图处理\", \"figure description\", \"附图说明\", \"drawings description\", or wants to describe patent figures with reference numerals"), with concrete trigger phrases — a direct match for anchor 5.

5 / 5

Trigger Term Quality

Includes natural bilingual trigger phrases ("附图处理", "附图说明", "figure description", "drawings description") that users would plausibly say, but misses common variations like "patent drawings", "附图标记", or standalone "reference numerals"; not the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

"附图说明" and "drawings description" are patent-specific terminology giving a clear niche, but generic phrases like "figure description" carry minor overlap risk with non-patent figure/diagram skills; fits anchor 4 better than anchor 5's "minimal conflict risk".

4 / 5

Total

16

/

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