CtrlK
BlogDocsLog inGet started
Tessl Logo

quote

为 shiji-kb wiki 页面补全「史记引文」节。搜索实体标注文件中对该页面实体的真实引用(而非裸字符匹配),展开已知 PN 的完整段落,过滤已引,输出新增候选。当用户说 /quote PAGE 时触发。

71

Quality

86%

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

87%

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

A concise, highly actionable skill body with correct progressive disclosure to its one real bundle script. The main weakness is workflow clarity on the write path: the mandatory revision-recording checkpoint exists, but there is no validate/retry loop to confirm appended citations are well-formed before recording.

Suggestions

Add an explicit validation step before Step 5 — e.g. re-read the 史记引文 section to confirm each new '> 出自' line links and truncates correctly, and only record the revision once verified.

Make the feedback loop explicit: if a reconstructed citation is empty or over-length after truncation, drop or re-fetch it rather than appending blindly.

DimensionReasoningScore

Conciseness

Lean and efficient — assumes Claude's knowledge of the wiki, gives exact commands, regex tables, and a formatting spec with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Fully executable guidance: copy-paste bash commands with the exact script path, an entity-type→regex mapping table with worked examples, and a concrete '> 出自 [[...]] (NNN-N):...' output template.

3 / 3

Workflow Clarity

Five steps are clearly sequenced with an append-only rule and a mandatory 'record revision' checkpoint, but for batch page edits there is no validate-then-fix feedback loop (e.g. verify the appended citation renders/links correctly before recording), which the rubric requires for a 3 on batch-write operations.

2 / 3

Progressive Disclosure

Well-organized overview that correctly references the single one-level-deep bundle file at its real path ('python3 .claude/skills/quote/scripts/quote_page.py'), which exists in ./scripts/quote_page.py — no nested references, easy navigation.

3 / 3

Total

11

/

12

Passed

Description

85%

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 tightly scoped, third-person description that clearly states concrete actions and an explicit trigger with low conflict risk. Its only gap is trigger-term coverage: it relies on the single literal '/quote PAGE' rather than natural keyword variants users might phrase.

Suggestions

Add natural-language trigger terms users are likely to say (e.g. '补史记引文', '查页面引文', '为页面补引文') alongside the literal '/quote PAGE' command so it matches plain-language requests too.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '补全「史记引文」节', '搜索实体标注文件中...真实引用', '展开已知 PN 的完整段落', '过滤已引', '输出新增候选' — rather than vague verbs.

3 / 3

Completeness

Explicitly answers both what ('为 shiji-kb wiki 页面补全「史记引文」节...输出新增候选') and when ('当用户说 /quote PAGE 时触发').

3 / 3

Trigger Term Quality

Names the literal trigger '/quote PAGE' but gives no natural-language variants a user might actually say (e.g. '补引文', '史记引文', '查引文'), so common phrasings are missing.

2 / 3

Distinctiveness Conflict Risk

Tied to a highly specific niche (shiji-kb wiki 史记引文 completion via entity-annotation search) with a distinct command trigger, making collision with other skills unlikely.

3 / 3

Total

11

/

12

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
baojie/shiji-kb
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.