CtrlK
BlogDocsLog inGet started
Tessl Logo

check

Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits. Use when users ask in any language for code review, issue or PR triage, release gates, publishing follow-through, or project audits. Not for debugging root causes or prose review.

76

Quality

96%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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

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.

A well-architected, highly actionable review skill body with strong workflow sequencing, validation feedback loops, and clean progressive disclosure through real one-level-deep reference files. Its only weakness is moderate verbosity in a few prose-heavy safety sections.

Suggestions

Tighten the Hard Stops and Dependency-changes prose into terser rule statements to reduce token load without losing the safety content (conciseness).

Consider moving the long Hard Stops / lockfile-consistency detail into a reference file referenced from the body, keeping the main flow leaner (conciseness, progressive_disclosure).

DimensionReasoningScore

Conciseness

The body is dense and operational with no padding about concepts Claude already knows, but at ~300 lines some sections (e.g. Hard Stops) use elaborate prose that could be tightened, placing it just below the lean/efficient top anchor.

4 / 5

Actionability

It provides many copy-paste-ready commands ("git status --short --branch -uall", "gh run view <id> --json status,conclusion", "git worktree add --detach <known-good-commit>", "cargo tree -i <pkg> --target all") and concrete templates covering the common cases.

5 / 5

Workflow Clarity

Multi-step processes are explicitly sequenced with validation checkpoints and feedback loops (re-read HEAD before commit/push, validate-then-fix-then-rebuild, verify in isolation), plus a sign-off ledger checklist for complex processes.

5 / 5

Progressive Disclosure

A mode-picker table routes to one-level-deep, well-signaled reference files (references/mode-*.md, project-context.md, review-patterns.md, etc.), all of which exist as real bundle files, with the SKILL.md acting as a clear overview.

5 / 5

Total

19

/

20

Passed

Description

100%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, third-person description that concisely states concrete capabilities, explicit trigger conditions, and clear exclusions. It fully satisfies the what/when contract with natural trigger language and low conflict risk.

DimensionReasoningScore

Specificity

The description lists a comprehensive set of concrete review surfaces and actions — "Reviews code diffs, PRs, issue queues, release readiness, commits, pushes, publishing, and project audits" — matching the anchor for multiple specific concrete actions with comprehensive coverage.

5 / 5

Completeness

It explicitly answers both what ("Reviews code diffs, PRs, issue queues...") and when ("Use when users ask in any language for code review...") with concrete trigger phrases, and adds a "Not for" exclusion clause, satisfying the top anchor.

5 / 5

Trigger Term Quality

The "Use when" clause covers natural phrases users would actually say ("code review, issue or PR triage, release gates, publishing follow-through, or project audits") with good synonym coverage across the domain, matching the comprehensive-coverage anchor.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (review/audit/ship/publish) and explicitly excludes adjacent skills ("Not for debugging root causes or prose review"), giving distinct triggers with minimal conflict risk.

5 / 5

Total

20

/

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.

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
tw93/Waza
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.