CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

patent-map

专利地图:基于通俗解读已入库的 Obsidian 案例,点名后打开五种图。地形按 bge-small-zh 向量摊开。

Quality

84%

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

93%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.

An exemplary lean, single-purpose skill body: executable commands, explicit input/output contracts, pre-handled failure modes, and well-signaled one-level-deep references. The only weakness is that the post-launch verification step (matching MAP_VAULT to the intended vault) is implicit rather than an explicit checkpoint.

DimensionReasoningScore

Conciseness

The body is dense with operational facts — vault resolution ("PATENT_READER_OBSIDIAN_VAULT 或 ~/.patent-disclosure-skill/obsidian_vault.txt"), the glob "Research/Patents/**/*_解读_*.md", machine-readable prefixes (MAP_URL/MAP_PORT/MAP_VAULT…), model name, and a graceful fallback ("未装 fastembed 时图仍能开,地形退回 IPC 簇") — with no concept explanations Claude already knows. Matches anchor 5 ('lean and efficient; every token earns its place'); not 4 because there is no over-explanation to trim.

5 / 5

Actionability

Copy-paste-ready commands ("python skills/patent-map/tools/serve_map.py", "pip install -r skills/patent-map/tools/requirements.txt", "python tools/serve_map.py") plus a concrete output contract (machine-readable stdout prefixes, random port on 127.0.0.1:0) and failure-mode handling. Matches anchor 5 ('fully executable; copy-paste ready commands; specific examples cover the common cases'); not 4 because even the standalone-copy path and the no-fastembed path are covered.

5 / 5

Workflow Clarity

A clear 3-step sequence (Read prompts/guardrails.md → intake.md; 确认库路径; 启动) with implicit checkpoints — path confirmation and the machine-readable startup prefixes. Matches anchor 4 ('clear sequence with most checkpoints present; minor validation gaps'); not 5 because there is no explicit step verifying MAP_VAULT matches the intended vault before sharing the URL, and not 3 because the sequence and its checkpoints are unambiguous (the skill is read-only, so the destructive/batch validation cap does not apply).

4 / 5

Progressive Disclosure

Under 50 lines, single task, cleanly sectioned (用途/何时用/输入/步骤/护栏/产出物) with one-level-deep, clearly signaled references ("细则 prompts/guardrails.md", "Read prompts/guardrails.md → intake.md"). Per the simple-skill scoring note this matches anchor 5; not 4 because no organizational gaps remain.

5 / 5

Total

19

/

20

Passed

Description

66%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.

The description identifies a distinct niche and an explicit activation condition, but is under-specified on what the five chart types are and which trigger phrases fire the skill. It sits noticeably above the midpoint overall, dragged down mainly by missing synonym triggers.

Suggestions

Enumerate the five chart types and their concrete uses (finding similar cases, applicant overlap, in-text citations) instead of the bare "五种图".

Include the concrete trigger phrases (专利地图 / 案例地图 / patent-map) in the description so users' natural phrasing matches, raising trigger-term coverage.

Replace the terse "点名后" with an explicit 'Use when…' style clause stating the invocation condition, e.g. "Use when the user asks for 专利地图 / 案例地图 / patent-map views of ingested cases."

DimensionReasoningScore

Specificity

"点名后打开五种图" and "地形按 bge-small-zh 向量摊开" name the domain (Obsidian patent-case vault) plus one action and one mechanism, but the five chart types are never enumerated. This matches anchor 3 ('names domain and 1-2 concrete actions, but not comprehensive'); it is not 4 because several distinct actions are not listed.

3 / 5

Completeness

Both parts are present: what ("基于通俗解读已入库的 Obsidian 案例…打开五种图") and when ("点名后" — when the user names the skill). Matches anchor 4 ('both what and when; when could be more explicit'); not 5 because no concrete trigger phrases (专利地图/案例地图/patent-map) appear in the description itself, and not 3 because the when is explicitly stated rather than implied.

4 / 5

Trigger Term Quality

The natural term "专利地图" is present, but the description omits the aliases the body itself lists (案例地图, `/patent-map`), fitting anchor 3 ('some relevant keywords but missing common variations or synonyms'). Not 4: coverage lacks the primary synonym triggers users would actually say.

3 / 5

Distinctiveness Conflict Risk

"专利地图…Obsidian 案例…bge-small-zh 向量" carves out a clear niche with distinct triggers (patent-case visualization over an ingested vault), matching anchor 5 ('clear niche with distinct triggers; minimal conflict risk').

5 / 5

Total

15

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

handsomestWei/patent-disclosure-skill

Path

skills/patent-map/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.