CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

verify-module

模块完整性校验关卡。扫描目录结构、检测缺失文档、验证代码与文档同步。当用户提到模块校验、文档检查、结构完整性、README检查、DESIGN检查时使用。在新建模块完成时自动触发。

Quality

82%

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

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

A well-structured, mostly executable verification skill: real scanner script with flags, concrete checklists, and a defined report format. Main gaps are the unspecified method for the code-documentation consistency check and the lack of an integrated fix-and-revalidate loop.

Suggestions

Specify how to perform step 5 (code-documentation consistency check) — e.g., a scanner flag like --sync-check or a concrete manual procedure — since it is a headline capability mentioned in the description but has no implementation in the body.

Integrate the fix path into the 校验流程 as an explicit feedback loop (e.g., '7. If 未通过: run /gen-docs <模块路径>, then re-run the scanner to confirm 通过').

Consider moving the detection-item tables or the report format template into a references/ file to slim the main body and improve progressive disclosure.

DimensionReasoningScore

Conciseness

The body is composed of lean tables, checklists, and copy-paste commands with no explanation of concepts Claude already knows; only the decorative creed block ('缺一不可,残缺即异端') and the 自动触发时机 table duplicating frontmatter trigger info could be trimmed.

4 / 5

Actionability

Concrete executable commands are provided ('node scripts/module_scanner.js <模块路径> -v / --json', verified to exist in the bundle) plus itemized README/DESIGN checklists and a report template, but workflow step 5 '检查代码与文档描述是否一致' gives no method or command for how to actually verify consistency.

4 / 5

Workflow Clarity

The 校验流程 lists a clear 6-step sequence with validation inherent to the skill (scanner run, ✓/✗ report format) and a fix path (快速修复 → /gen-docs), but the fix path is a separate section rather than an integrated re-check loop, and the consistency-check step lacks a checkpoint.

4 / 5

Progressive Disclosure

Sections are well-organized and the single bundle file (scripts/module_scanner.js) is referenced one level deep and verified to exist; however, all ~115 lines of detection tables and report templates are inlined in SKILL.md with no reference split, which is acceptable but not optimally structured.

4 / 5

Total

16

/

20

Passed

Description

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

A strong description: third-person, concise, with three concrete capabilities, five natural trigger phrases, and an explicit use-when clause plus auto-trigger timing. Its only weaknesses are a missing mention of the README/DESIGN content-completeness checks and a couple of absent trigger synonyms.

DimensionReasoningScore

Specificity

The description lists three concrete actions ('扫描目录结构、检测缺失文档、验证代码与文档同步') but omits the README/DESIGN content-completeness checking that forms the bulk of the skill's checklists — a minor coverage gap that keeps it below comprehensive.

4 / 5

Completeness

Both what ('扫描目录结构、检测缺失文档、验证代码与文档同步') and when ('当用户提到…时使用' plus '在新建模块完成时自动触发') are explicitly and concretely stated with trigger phrases, matching the top anchor.

5 / 5

Trigger Term Quality

Five natural trigger phrases are given ('模块校验、文档检查、结构完整性、README检查、DESIGN检查') including file-name triggers, but natural variations for the sync-verification capability (e.g., '文档同步'、'代码文档一致性') are missing.

4 / 5

Distinctiveness Conflict Risk

README检查 and DESIGN检查 are distinctive triggers tied to this repo's module convention, but the broader term 文档检查 could overlap with general documentation-related skills, so overlap risk is minor rather than minimal.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository

fengshao1227/ccg-workflow

Path

templates/skills/tools/verify-module/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.