CtrlK
BlogDocsLog inGet started
Tessl Logo

patent-write

基于用户提供的技术方案、草稿或参考专利,生成、改写与统稿中文发明专利的题目、摘要、背景技术、发明内容、权利要求、附图说明和具体实施方式。用于专利撰写、专利摘要、权利要求、说明书、专利润色、专利仿写、参考专利蒸馏等场景。

76

Quality

96%

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

92%

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

A well-organized, concise instruction skill with a clear sequenced workflow and concrete guidance. Its main defect is progressive disclosure: the dispatch table routes every task to reference files that are not present in the bundle, leaving the overview pointing at missing detail.

Suggestions

Ship the referenced reference/*.md files (full-patent, title, abstract, background, invention-content, claims, figures-desc, figures-drawio, implementation, review, distill) — currently the entire dispatch table routes to files that do not exist, so the skill's promised detail is unreachable.

Add a brief inline skeleton for the highest-frequency task (e.g. a minimal claims + abstract template) so the skill remains usable even before a reference file is opened.

Verify the reference path convention (the body uses singular reference/ while the bundle convention is references/) and align them so links resolve.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a patent is or basic concepts, and every section (dispatch table, input checklist, ordered flow, principles, distilled patterns) earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

As an instruction-only skill it gives concrete, specific guidance: a precise phrase-to-file dispatch table, a concrete input checklist, an explicit 5-step default ordering, and actionable structural heuristics (e.g. '权利要求 1 负责总流程...从属权利要求负责细化子步骤'), so absent code is not penalized.

3 / 3

Workflow Clarity

A clear sequence (identify task → collect input → execute) with an explicit 5-step full-patent ordering and a final '统稿和一致性检查' validation/review checkpoint; patent writing is non-destructive so a retry feedback loop is not required, placing this at the 'clear sequence with explicit validation' anchor.

3 / 3

Progressive Disclosure

The overview is well-designed with a one-level-deep dispatch table, but every referenced file (reference/full-patent.md, reference/claims.md, etc.) is missing — the reference/ directory and references/scripts/assets/ do not exist — so the promised detail is unreachable, which is below the 'clear overview with well-signaled one-level-deep references' anchor and not a 3.

2 / 3

Total

11

/

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, specific description that states concrete actions across all major patent sections and pairs them with an explicit trigger clause. It is concise, uses third person, and is clearly distinguishable from other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('生成、改写与统稿') across seven named patent sections (题目、摘要、背景技术、发明内容、权利要求、附图说明、具体实施方式), matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers both 'what' (generate/rewrite/consolidate the seven sections) and 'when' via an explicit '用于...场景' trigger clause equivalent to 'Use when...', so it is not capped at 2 for a missing trigger.

3 / 3

Trigger Term Quality

The '用于...场景' clause surfaces natural user terms — 专利撰写、专利摘要、权利要求、说明书、专利润色、专利仿写、参考专利蒸馏 — that a Chinese user would actually say, giving good coverage rather than technical jargon.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (Chinese invention patent drafting) with distinctive triggers, making it unlikely to fire for unrelated skills; third-person voice is used with no first/second person to penalize.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

relative_links

Relative link issues: 11 missing

Warning

Total

15

/

16

Passed

Repository
xstongxue/best-skills
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.