CtrlK
BlogDocsLog inGet started
Tessl Logo

enrich

升级 shiji-kb wiki 页面质量一档(stub→basic→standard→featured→premium),或升至用户指定档。诊断页面当前指标缺口,执行对应补充操作(补引文、写散文、加节、加图)。当用户说 /enrich PAGE 或 /enrich PAGE 目标档 时触发。

75

Quality

92%

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, actionable skill body: concrete commands, a sequenced workflow with validation and a retry loop, and a single well-signaled reference file. The only minor slack is light duplication between the tier-threshold table and the quick-reference upgrade-workload table.

DimensionReasoningScore

Conciseness

Lean tables and executable commands with no padding; domain-specific metric definitions (PN, 散文 counting rules) earn their place because Claude could not infer them, though the '快速参考' table lightly duplicates the门槛 table.

3 / 3

Actionability

Fully executable commands ('python3 wiki/scripts/compute_quality.py --dry-run PAGE', 'record_revision.py …') with copy-paste-ready summary examples and a concrete gap→operation mapping table.

3 / 3

Workflow Clarity

Five numbered steps (诊断→确定目标→按缺口执行→验证→记录修订) with a dry-run diagnose, a verify-and-retry feedback loop ('若未达到…继续补'), and an emphasized mandatory record step.

3 / 3

Progressive Disclosure

Body is an overview pointing to one clearly-signaled, one-level-deep reference ([references/section_templates.md]) that is a real bundle file, with detailed section templates appropriately split out.

3 / 3

Total

12

/

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 specific, well-scoped description that states concrete actions and an explicit trigger. Its only weakness is trigger-term breadth — it relies on the literal slash command rather than enumerating natural phrasings a user might say.

Suggestions

Add natural-language trigger variants beyond the slash command, e.g. 'Use when the user asks to improve, upgrade, or enrich a wiki page's quality, or to push a page to a specific quality tier.'

DimensionReasoningScore

Specificity

Lists multiple concrete actions — '诊断页面当前指标缺口,执行对应补充操作(补引文、写散文、加节、加图)' — naming the domain and four specific enrichment operations plus diagnosis.

3 / 3

Completeness

Clearly states what (升级页面质量一档/诊断缺口/执行补充操作) and an explicit when clause ('当用户说 /enrich PAGE … 时触发'), answering both questions.

3 / 3

Trigger Term Quality

Trigger guidance is explicit ('当用户说 /enrich PAGE 或 /enrich PAGE 目标档 时触发') but covers only the single slash-command form, lacking natural-language variations a user might say.

2 / 3

Distinctiveness Conflict Risk

Scoped to the shiji-kb wiki quality-tier system with a distinct /enrich trigger, making conflict 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.