CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

specification-writing

Write the full patent specification from claims and invention disclosure. Use when user says "撰写说明书", "write specification", "写说明书", "patent description", or wants to draft the complete patent specification.

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Low

Low-risk findings worth noting

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, highly actionable 11-step workflow for patent specification drafting, with concrete bilingual templates, word-limit tables, claim-support verification, and a reviewer checklist. It scores solidly across all dimensions with only minor gaps: the reviewer-delegation preamble is dense and depends on external resolver files, and the post-review remediation loop is implicit.

DimensionReasoningScore

Conciseness

The body is mostly imperative instructions, tables, and output templates with no padding explaining concepts Claude already knows. Minor trimmable spots exist: the dense reviewer-resolver preamble and the fully inlined SPECIFICATION_INDEX.md template, which keeps it at 'efficient; minor instances of over-explanation' rather than 'every token earns its place'.

4 / 5

Actionability

Concrete guidance throughout: exact output file structure, copy-paste CN/US/EP template sentences, jurisdiction word-limit tables, sub-skill invocation commands, a claim-support verification table schema, and a full reviewer prompt. Minor gaps: reviewer slot resolution depends on external reviewer_route.py/reviewer-backends.md and the spawn_agent block is explicitly only the 'backend=codex' example, so it is 'mostly executable with minor gaps' rather than fully copy-paste ready.

4 / 5

Workflow Clarity

A clear 11-step sequence with real validation checkpoints: Step 9 verifies every claim element has support and instructs adding missing description before proceeding, and Step 10 runs a six-point reviewer checklist. The gap keeping it below the top anchor is that no explicit remediation loop is defined after the Step 10 review (what to do when the reviewer reports failures is left implicit).

4 / 5

Progressive Disclosure

The body is well-sectioned and delegates heavy material one level deep through a dedicated 'Shared References' section with jurisdiction-conditional loading (patent-writing-principles.md, patent-format-cn/us/ep.md) and sub-skill invocations for figures and embodiments. Minor organization gaps: the per-section writing rules and the full index template are inlined, which fits 'good structure; most content appropriately placed' rather than the cleanly split top anchor.

4 / 5

Total

16

/

20

Passed

Description

82%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 that explicitly states what the skill does and when to use it, with bilingual (CN/EN) natural trigger phrases and write/draft synonyms. The only weakness is specificity: it names the composite deliverable but not the constituent specification sections it produces.

DimensionReasoningScore

Specificity

"Write the full patent specification from claims and invention disclosure" names the domain and one composite concrete action with its inputs, but does not enumerate the specific sections produced (title, background, summary, detailed description, abstract). It matches the anchor for naming the domain with 1-2 concrete actions without comprehensive coverage, not the level above which requires several listed specific actions.

3 / 5

Completeness

Explicitly answers both questions: "Write the full patent specification from claims and invention disclosure" states what it does, and "Use when user says '撰写说明书', 'write specification'..." states when with concrete trigger phrases. This clearly matches the top anchor; the anchor below (4) applies only when the 'when' is less explicit.

5 / 5

Trigger Term Quality

Includes natural trigger phrases in both Chinese ("撰写说明书", "写说明书") and English ("write specification", "patent description", "draft the complete patent specification") with write/draft synonyms. Good keyword coverage overall, but a few natural variants are missing (e.g., standalone "说明书", "patent spec"), fitting the 'good coverage, a few natural terms missing' anchor rather than the comprehensive one.

4 / 5

Distinctiveness Conflict Risk

Patent specification writing is a clear niche with distinct triggers that separate it from sibling patent-drafting skills (claims drafting, jurisdiction formatting), and the trigger phrases are unlikely to fire for the wrong skill. Minimal conflict risk matches the top anchor.

5 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 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

relative_links

Relative link issues: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

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

Path

skills/skills-codex/specification-writing/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.