CtrlK
BlogDocsLog inGet started
Tessl Logo

verification-loop

为 Claude Code 会话提供的全面验证系统。

47

Quality

50%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

High

Do not use without reviewing

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/verification-loop/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%Weight 40%Scale 1-3

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-structured, highly actionable verification workflow with executable commands, explicit stop-and-fix checkpoints, and a clear report template. Its only weakness is minor verbosity from a few obvious comments and redundant report fields.

DimensionReasoningScore

Conciseness

The body is mostly lean with direct bash commands and brief bullets, but a few comments restate the obvious (e.g. '# 检查项目是否能成功构建' before `npm run build`) and the report-field list repeats what the test command already prints, so it could be tightened further rather than earning the lean/efficient anchor at 3.

2 / 3

Actionability

Each phase ships concrete, copy-paste-ready commands (`npm run build`, `npx tsc --noEmit`, `npm run lint`, `npm run test -- --coverage`, grep scans, `git diff --stat`) with JS/TS and Python variants plus a filled-in report template, matching the fully-executable anchor.

3 / 3

Workflow Clarity

Six phases are clearly sequenced (阶段 1–6) with explicit validation checkpoints and feedback loops — '如果构建失败,请停止并在继续之前进行修复' and '在继续之前修复关键错误' — plus a final pass/fail report, satisfying the clear-sequence-with-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist and none are needed; the single self-contained SKILL.md is organized into well-signaled sections (何时使用, 验证阶段, 输出格式, 持续模式, 与钩子集成) with no nested references, which per the simple-skills note earns a 3 for a well-organized single-file skill.

3 / 3

Total

11

/

12

Passed

Description

15%Weight 40%Scale 1-3

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 is too vague to function as a skill trigger: it names a generic 'verification system' without concrete actions, natural trigger terms, or any 'use when' guidance, making it likely to conflict with other QA-style skills. It needs explicit capabilities and trigger conditions.

Suggestions

Replace '全面验证系统' with concrete actions, e.g. 'Runs build, type-check, lint, tests with coverage, secret scanning, and diff review before submitting a PR' to lift specificity.

Add an explicit 'Use when...' trigger clause, e.g. 'Use after completing a feature, before creating a PR, or when you need to confirm all quality gates pass', to satisfy completeness.

Include natural trigger terms users actually say — 'verify code', 'run checks before PR', 'quality gates', 'pre-commit checks' — to reduce conflict risk with other testing/review skills.

DimensionReasoningScore

Specificity

The phrase "全面验证系统" (comprehensive verification system) names a domain but lists no concrete actions — it does not say it runs builds, type checks, lint, tests, or scans, matching the vague 'Helps with documents' anchor rather than the action-listing anchor at 3.

1 / 3

Completeness

It gives only a weak 'what' (a 'verification system') and entirely omits any 'when to use it' / 'Use when...' guidance, so both halves are weak or missing per the score-1 anchor.

1 / 3

Trigger Term Quality

"验证" (verification) is a keyword a user might naturally say, but the description misses common variations users actually utter such as 'run tests', 'lint', 'check before PR', or 'quality gates', fitting the 'some relevant keywords but missing common variations' anchor.

2 / 3

Distinctiveness Conflict Risk

'Comprehensive verification system for Claude Code sessions' is generic and would overlap with many testing, linting, and code-review skills, matching the 'very generic; would conflict with many skills' anchor.

1 / 3

Total

5

/

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
xu-xiang/everything-claude-code-zh
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.