CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

check

Reviews diffs, PRs, release readiness, and publishing follow-through. Use when asked to review, triage issues or PRs, or ship. Not for debugging root causes or prose.

Quality

86%

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

The canonical home for this skill is check in tw93/Waza

SKILL.md
Quality
Evals
Security

Quality

Content

85%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 body is an exceptionally actionable and well-structured review workflow: concrete commands, explicit validation checkpoints, feedback loops on stale verdicts, and clean one-level conditional disclosure into a real bundle. Its one weakness is token efficiency — authorization and report-only rules are stated three times and several Hard Stops bullets are long run-ons that could be compressed into the existing table style.

Suggestions

Consolidate the authorization and report-only rules currently restated in the Outcome Contract, Worktree Safety Preflight, and Autofix Routing sections into a single canonical section referenced from the others.

Break the longest run-on policy sentences (e.g., the Hard Stops 'Source and distribution out of sync' bullet and the Authorization bullet) into short table rows or checklists matching the Gotchas/Autofix table style.

Deduplicate the completion-ledger and sign-off requirements stated in Outcome Contract, Specialist Review, and Sign-off into one canonical checklist, keeping the sign-off template as the single reference.

DimensionReasoningScore

Conciseness

The body is dense and free of background padding, but at ~230 lines it restates authorization and report-only rules across Outcome Contract ("may not edit files, apply autofixes, commit, push, publish"), Worktree Safety Preflight ("must not move, hide, overwrite, clean, or discard"), and Autofix Routing ("In report-only mode, do not modify the worktree"), and many multi-clause sentences could be tightened. Not 2 because nothing explains concepts Claude already knows and no section is padded; not 4 because the repetition and run-on policy sentences are more than minor.

3 / 5

Actionability

Copy-paste-ready commands appear throughout ("git status --short --branch -uall", "gh run view <id> --json status,conclusion", "bash <skill-base-dir>/scripts/run-tests.sh", "git worktree add --detach <known-good-commit>"), backed by concrete decision tables (mode picker, depth, autofix routing) and a fill-in sign-off template. As an instruction-only skill, the guidance is fully executable.

5 / 5

Workflow Clarity

The pipeline is clearly sequenced (preflight → mode pick → context extraction → diff → scope → review passes → verification → sign-off) with explicit validation checkpoints and feedback loops: "the old verdict expires: re-read HEAD, status, and the full resolved diff", and "Re-freeze the baseline, re-run the check that exposed the finding". The verification section also defines failure diagnosis and evidence limits.

5 / 5

Progressive Disclosure

All ten references/ files and the scripts are directly linked from the body with explicit conditional load signals ("Load a mode file only when its row matches", "load references/review-patterns.md" only for matching diff shapes), each verified present in the bundle and one level deep. The SKILL.md stays an overview while mode, pattern, and catalog detail lives in the bundle.

5 / 5

Total

18

/

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.

The description is strong: concrete capabilities, an explicit use-when clause with natural trigger phrases, and a negative scope boundary that prevents mis-triggering. Its main gap is that the description field itself omits several natural trigger terms (code review, audit, release) that are relegated to the separate when_to_use field, and the audit/scorecard capability is not represented.

DimensionReasoningScore

Specificity

"Reviews diffs, PRs, release readiness, and publishing follow-through" lists several concrete capabilities with clear objects. Not 5 because the audit/scorecard surface (present in when_to_use and the body) is absent from the description; not 3 because more than 1-2 specific actions are named.

4 / 5

Completeness

Both questions are answered explicitly: what = "Reviews diffs, PRs, release readiness, and publishing follow-through"; when = "Use when asked to review, triage issues or PRs, or ship" with concrete trigger phrases, plus a negative boundary ("Not for debugging root causes or prose").

5 / 5

Trigger Term Quality

"Use when asked to review, triage issues or PRs, or ship" supplies natural phrases users would say. Not 5 because common variants like "code review", "audit", and "release" appear only in the separate when_to_use field, not in the description itself.

4 / 5

Distinctiveness Conflict Risk

A clear pre-ship review niche with explicit exclusions ("Not for debugging root causes or prose") reduces conflict risk, but bare triggers like "review" and "ship" keep minor overlap with closely related code-review skills. Not 3 since the named artifacts (diffs, PRs, release readiness, publishing) are far more specific than generic domain claims.

4 / 5

Total

17

/

20

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.

Validation — 15 / 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

tw93/Waza

Path

plugins/waza/skills/check/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.