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.

78

Quality

100%

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

100%

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

A well-structured, lean patent-drafting skill with concrete templated guidance, an explicit claim-support verification checkpoint, and clear organization. It avoids teaching concepts Claude already knows and provides copy-ready structural examples and rules.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence; it provides constants, inputs, a structured workflow, and tight rules without explaining what a patent or embodiment is, and every section earns its tokens.

3 / 3

Actionability

Concrete executable guidance throughout: exact constants, file paths (patent/INVENTION_DISCLOSURE.md), templated opening phrasing, reference-numeral formatting rules, a worked pseudocode example, and explicit output location (patent/specification/detailed_description.md).

3 / 3

Workflow Clarity

A clearly sequenced 6-step workflow with an explicit validation checkpoint in Step 4 (Claim Support Verification) that requires adding description for any unsupported claim element before proceeding — a feedback loop for a correctness-critical operation.

3 / 3

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ absent) and the SKILL.md body is self-contained and well-organized into Constants, Inputs, Workflow, and Key Rules sections; per the rubric's simple-skill note, a well-organized single file with no external references scores 3.

3 / 3

Total

12

/

12

Passed

Description

100%

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, concise description that states the concrete capability, uses third-person voice, and provides an explicit 'Use when' trigger with both English and Chinese natural phrases. It cleanly answers both 'what' and 'when' with low conflict risk.

DimensionReasoningScore

Specificity

Lists concrete actions including 'Write detailed embodiment descriptions for patent specifications', naming the domain (patent specifications) and the specific output type (embodiment descriptions), comparable to multi-action good examples.

3 / 3

Completeness

Explicitly answers 'what' (write detailed embodiment descriptions for patent specifications) AND 'when' (Use when user says ... or wants to describe how to practice an invention), with an explicit 'Use when' trigger clause.

3 / 3

Trigger Term Quality

Provides strong coverage of natural trigger phrases in both English and Chinese ('write embodiment', 'detailed description', '撰写实施例', '实施例描述') plus the descriptive clause 'wants to describe how to practice an invention', matching natural user phrasing.

3 / 3

Distinctiveness Conflict Risk

The patent-specific niche and the explicit bilingual trigger terms make it clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.