CtrlK
BlogDocsLog inGet started
Tessl Logo

verify-changes

Verify a code change in this repo before committing or opening a PR. Use after editing collector (backend), web (frontend), shared package, or the Go agent — picks the minimal sufficient check set per touched area.

76

Quality

95%

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

An efficient, highly actionable verification skill: concrete commands per touched area, a pre-commit checklist as a validation checkpoint, and clean sectioning with one-level external references. No bundle files exist, so progressive disclosure rests on organization alone, which is strong.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: a one-line framing sentence, per-area command blocks, and a checklist with no padding or explanation of concepts Claude already knows.

3 / 3

Actionability

Every section gives fully executable, copy-paste-ready commands (e.g. 'pnpm --filter @neko-master/collector exec tsc --noEmit', 'go vet ./... && go build ./... && go test ./...'), including single-test-case invocations.

3 / 3

Workflow Clarity

Steps are sequenced by touched area and capped by a 'Checklist before commit' validation checkpoint; the operation is not destructive, so the missing-feedback-loop cap does not apply.

3 / 3

Progressive Disclosure

A single, well-organized SKILL.md with no bundle files and only one-level references to other skills (ui-conventions, db-conventions, add-stats-dimension) — no nested or deeply chained references.

3 / 3

Total

12

/

12

Passed

Description

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

A strong, third-person description with an explicit 'Use after...' trigger clause covering both what and when. The only mild gap is that it frames a single verify action rather than listing several concrete capabilities.

DimensionReasoningScore

Specificity

It names the domain ('Verify a code change in this repo before committing or opening a PR') and a concrete behavior ('picks the minimal sufficient check set per touched area'), but describes one main action rather than enumerating multiple distinct capabilities as the anchor-3 example does.

2 / 3

Completeness

It answers both 'what' ('Verify a code change... picks the minimal sufficient check set per touched area') and 'when' with an explicit trigger clause ('Use after editing collector (backend), web (frontend), shared package, or the Go agent').

3 / 3

Trigger Term Quality

Natural phrases a user would actually say appear throughout: 'before committing or opening a PR' and 'Use after editing collector... web... shared package, or the Go agent'.

3 / 3

Distinctiveness Conflict Risk

The repo-specific scope (collector, web, shared package, Go agent) and the 'before committing or opening a PR' trigger carve a clear niche unlikely to fire for unrelated skills.

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
foru17/neko-master
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.