CtrlK
BlogDocsLog inGet started
Tessl Logo

verify-changes

Verify code changes by running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean. Use after editing any source file.

72

Quality

88%

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

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

The content is excellent: concise, actionable, with a well-sequenced verification workflow and an explicit feedback loop. The only minor gap is that some command templates rely on placeholders that require substitution before running.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what a compiler or linter is, and the single framing sentence ('Editing a file is only half a step') earns its place by motivating the loop.

5 / 5

Actionability

Provides concrete, executable commands per ecosystem (npx tsc --noEmit, ruff check, mvn -q -pl, ./gradlew) and concrete flags (NO_COLOR=1), but detection requires substitution placeholders like <changed files> and some judgment, keeping it just short of fully copy-paste ready.

4 / 5

Workflow Clarity

A clear numbered sequence with an explicit fix-and-re-run feedback loop ('Fix the root cause, then re-run the SAME command. Repeat until it passes.') and a validation checkpoint ('Only mark a todo completed once its verification command passes').

5 / 5

Progressive Disclosure

A simple, under-50-line single-purpose skill cleanly split into 'Procedure' and 'Rules' sections with no external references needed; structure is appropriate and complete for its scope.

5 / 5

Total

19

/

20

Passed

Description

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

The description is strong: it states concrete actions, covers both what and when explicitly, and uses natural trigger terms. Its main weakness is distinctiveness, since 'use after editing any source file' is a near-universal coding trigger that risks overlap with other skills.

Suggestions

Tighten the trigger to reduce conflict risk, e.g. 'Use after editing source files when you need to confirm changes are clean before marking work done or opening a PR.'

Add a couple of natural synonyms (e.g. 'verify', 'run checks', 'CI') to broaden trigger-term coverage.

Consider scoping the trigger to concrete moments (e.g. 'before marking a task complete or opening a PR') so it is distinguishable from general coding skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'running the project's typecheck, build, lint, and targeted tests, then fix and re-run until clean' — giving comprehensive coverage of the verification loop with no real gaps.

5 / 5

Completeness

Explicitly answers both what ('Verify code changes by running... typecheck, build, lint, and targeted tests, then fix and re-run until clean') and when ('Use after editing any source file') with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('typecheck', 'build', 'lint', 'tests', 'code changes', 'edit a source file') but misses some common synonyms like 'verify', 'CI', or 'diagnostics' that would round out coverage.

4 / 5

Distinctiveness Conflict Risk

The 'verify after edits' niche is identifiable, but the trigger fires after essentially every source edit, so it overlaps heavily with most coding skills rather than being a clearly isolated niche.

3 / 5

Total

17

/

20

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
agentscope-ai/agentscope-java
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.