CtrlK
BlogDocsLog inGet started
Tessl Logo

embodiment-description

Write detailed embodiment descriptions for patent specifications. Use when user says "撰写实施例", "write embodiment", "实施例描述", "detailed description", or wants to describe how to practice an invention.

64

Quality

78%

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/embodiment-description/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 workflow with explicit validation and concrete templates. Its main weakness is conciseness, driven by heavy repetition of the no-experimental-data guidance across the Key Rules section.

Suggestions

Consolidate the repeated 'no experimental data / embodiment is not an experiment' warnings in Key Rules into a single concise rule with the WRONG/RIGHT example, removing the redundant restatements.

Add an explicit re-verification loop after Step 4 (e.g., 're-check the claim-support table after adding description') to close the validation feedback loop.

Trim the explanatory lead-in 'they are the patent equivalent of experiment sections' which assumes context Claude already has.

DimensionReasoningScore

Conciseness

Mostly efficient with concrete tables and templates, but the 'no experimental data' rule is restated across five separate CRITICAL/bulleted entries (lines 119-126), which could be tightened into one; matches the 'mostly efficient but could be tightened' anchor rather than a leaner 4.

3 / 5

Actionability

Provides concrete opening-paragraph templates, step-by-step embodiment structures, numeral-formatting rules, a claim-support verification table, and example embodiment prose; minor gaps keep it just below fully copy-paste-ready, matching the 'mostly executable guidance with minor gaps' anchor.

4 / 5

Workflow Clarity

A clear 6-step sequence with an explicit validation checkpoint at Step 4 (claim-support table plus 'If any claim element lacks embodiment support, add the necessary description'), but lacks a re-verify loop after adding description, matching 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

Well-organized into Constants, Inputs, Workflow, and Key Rules with headers and tables and no nested references; the all-inline ~130-line body is appropriately self-contained for a no-bundle skill, matching 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

15

/

20

Passed

Description

90%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, complete description with explicit what/when structure and comprehensive bilingual trigger terms. Its only limitation is specificity, since it names a single action rather than enumerating several concrete capabilities.

DimensionReasoningScore

Specificity

Names the domain (patent specifications) and one concrete action ("Write detailed embodiment descriptions"), but lists only a single action rather than multiple specific actions, matching the '1-2 concrete actions, not comprehensive' anchor.

3 / 5

Completeness

Explicitly answers both 'what' ("Write detailed embodiment descriptions for patent specifications") and 'when' ("Use when user says...") with concrete trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Comprehensive coverage of natural terms including English and Chinese synonyms ("撰写实施例", "write embodiment", "实施例描述", "detailed description") plus a paraphrased intent trigger, matching the 'comprehensive coverage including synonyms' anchor.

5 / 5

Distinctiveness Conflict Risk

A clear niche (patent embodiment writing) with distinctive bilingual triggers unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers; minimal conflict risk' anchor.

5 / 5

Total

18

/

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.

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.