CtrlK
BlogDocsLog inGet started
Tessl Logo

doc-update

以源码为唯一事实来源,系统性核对并更新项目文档,确保内容与实现一致、多语言文档 1:1 对齐、结构完整。

61

Quality

72%

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

Fix and improve this skill with Tessl

tessl review fix ./jiuwenclaw/jiuwenclaw/resources/agent/jiuwenclaw_workspace/skills/doc-update/SKILL.md
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.

The body is a well-crafted, lean operational guide: concrete audit and fix steps, an explicit acceptance checkpoint, and genuinely non-obvious pitfalls. It assumes Claude's competence and avoids concept-padding throughout.

DimensionReasoningScore

Conciseness

The body is dense and operational — tables, numbered steps, and a pitfalls section — with no padding explaining concepts Claude already knows; every section (核心原则, 操作流程, 常见陷阱) earns its place, matching the 'lean and efficient' anchor.

3 / 3

Actionability

It gives concrete audit checklists ('每个配置项在源码配置文件中是否存在?默认值是否与源码一致?'), a fix-type table, and real examples (e.g. 'agent/skills' → 'workspace/agent/skills/', '60秒' vs '3600'); as an instruction-only skill the absence of code is not penalized because the guidance is specific and actionable.

3 / 3

Workflow Clarity

A clear 0–5 sequence (范围 → 清点配对 → 提取源码事实 → 逐文件审计 → 修复 → 验收) culminates in an explicit 验收 validation checkpoint with a checklist, satisfying the 'clear sequence with explicit validation steps and checklists' anchor.

3 / 3

Progressive Disclosure

It is a single self-contained file with no bundle references, well-sectioned into labeled parts with no nested or dead-end references, so the well-organized structure alone warrants a top score for this scope.

3 / 3

Total

12

/

12

Passed

Description

45%

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 concretely states multiple capabilities but omits any 'when to use' trigger guidance and natural keywords from the description text itself, weakening completeness and trigger-term quality. Moving the user-natural trigger terms into the description would substantially improve it.

Suggestions

Append a 'Use when...' clause to the description naming natural triggers (e.g. '刷文档', '更新文档', 'doc audit') so the what and when are both explicit in one field.

Lead with the concrete verbs users would recognize ('核对并更新文档') and keep the source-of-truth framing as supporting context to reduce overlap with generic editing skills.

Avoid relying on the separate 'trigger' field for discoverability — fold the most likely user phrases directly into the description.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — '系统性核对并更新项目文档', '确保内容与实现一致', '多语言文档 1:1 对齐', '结构完整' — rather than vague abstractions, matching the 'lists multiple specific concrete actions' anchor.

3 / 3

Completeness

It clearly answers 'what' the skill does but offers no 'Use when...' clause or equivalent trigger guidance within the description, so per the rubric completeness is capped at 2.

2 / 3

Trigger Term Quality

The description field itself contains no natural keywords a user would say; the trigger terms ('刷文档', '更新文档', 'doc audit') live in the separate 'trigger' field, not in the evaluated description text, so it falls to the 'no natural keywords' anchor.

1 / 3

Distinctiveness Conflict Risk

The source-of-truth + multilingual-alignment niche is somewhat specific, but '更新项目文档' could overlap with general editing/writing skills and the description carries no distinct trigger phrases, fitting the 'somewhat specific but could still overlap' anchor.

2 / 3

Total

8

/

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

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
XiaoLuoLYG/GOD
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.