CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

67

Quality

84%

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

SKILL.md
Quality
Evals
Security

Quality

Content

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

An exemplary orchestration-hub skill: every section is dense, actionable, and validated, with details correctly pushed into 9 conditionally-loaded reference files and 2 executable scripts. The only notable costs are some cross-section repetition of authorization/re-read rules and sibling references cited from other reference files.

Suggestions

Consolidate the authorization-scope rules stated in both the Outcome Contract and Autofix Routing into one canonical section referenced from the other, trimming the duplicated sentences.

Have mode files reference the shared procedure sections by the SKILL.md anchor (e.g. "the Hard Stops in the parent") rather than citing sibling reference files directly, keeping reference chains strictly one level deep.

DimensionReasoningScore

Conciseness

Dense imperative rules throughout with zero explanation of concepts Claude already knows, assuming competence. However, authorization scope is stated in both the Outcome Contract and Autofix Routing, re-read rules appear in both Hard Rules and Get the Diff, and some run-on rule sentences could be trimmed — anchor 4 (efficient, minor instances that could be trimmed).

4 / 5

Actionability

Copy-paste-ready commands throughout (git status --short --branch -uall, gh run view <id> --json status,conclusion, git fetch origin pull/<n>/head:refs/tmp/pr-<n>, git merge-tree, bash <skill-base-dir>/scripts/run-tests.sh, the git worktree add --detach isolation recipe) plus concrete thresholds, routing-class tables, and a complete sign-off template with exact field values. Fully executable guidance covering the common cases.

5 / 5

Workflow Clarity

A clear sequence (worktree safety preflight, mode picker, context extraction, baseline freeze, scope, checks, verification, sign-off) with explicit validation checkpoints and feedback loops: verdict expiry and re-read rules after fixes, re-run the exposing check, regression-test-before-fix, isolated verification in a clean worktree, and CI state confirmation before merge. Anchor 5: explicit validation steps, feedback loops, and checklists for a complex process.

5 / 5

Progressive Disclosure

Conditional mode loading via an intent table, and all ten cited bundle paths (9 references + scripts/run-tests.sh) resolve to real files with flat, non-nested content. Minor gap: mode files cross-cite sibling references (mode-ship.md points to project-context.md, mode-triage.md to public-reply.md), creating a mild second hop that keeps it below anchor 5's clean one-level-deep picture.

4 / 5

Total

18

/

20

Passed

Description

75%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 two-sentence description that answers both what and when, in third person, with a useful negative boundary and no fluff. Its main gap is a thin trigger vocabulary in the when clause relative to the breadth the skill body actually covers.

Suggestions

Widen the when clause with natural synonyms the body already supports, e.g. "Use when asked to review a diff or PR, run a code review, audit the project, decide whether to release, or push/publish follow-through".

Consider naming the audit/scorecard surface in the description (the body routes project-wide audits to mode-audit), since "audit" and "scorecard" are natural user terms absent from the description.

DimensionReasoningScore

Specificity

"Reviews diffs, PRs, release readiness, and publishing follow-through" names several concrete action areas. It matches anchor 4 (several specific actions, minor gaps) better than 5 because the actions are compressed into objects of one generic verb rather than a comprehensive multi-verb enumeration.

4 / 5

Completeness

Both what ("Reviews diffs, PRs, release readiness, and publishing follow-through") and when ("Use when asked to review, triage issues or PRs, or ship") are explicit, plus a negative boundary ("Not for debugging root causes or prose"). The when clause is sparser than the anchor-5 example's fuller trigger enumeration, so anchor 4's "when could be more explicit" applies.

4 / 5

Trigger Term Quality

"Use when asked to review, triage issues or PRs, or ship" provides natural trigger phrases (review, triage, ship, PRs), but common variations the skill body supports (code review, audit, release, before merge) appear only in when_to_use, not in the description. Anchor 4: good keyword coverage with a few natural terms missing.

4 / 5

Distinctiveness Conflict Risk

Clear niche (review-before-ship gating) with an explicit exclusion clause fencing off confusable neighbors (debugging, prose review). However "review" and "PRs" are broadly shared triggers among development skills, so anchor 4 (mostly distinct, minor overlap risk with closely related skills) fits better than 5.

4 / 5

Total

16

/

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