CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

sy-review

Review the completed slice for correctness, risk, evidence gaps, and next-stage blockers. Use when the user asks for review, PR readiness, risk assessment, blocker identification, or post-work verification.

Quality

82%

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

71%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-organized, token-efficient overview with exemplary progressive disclosure and a clear fail-fast workflow. The main weakness is actionability: validation and handoff guidance stays abstract ("smallest relevant local check", unnamed "plugin validation and SDK proof commands") with no concrete example of the stage-result artifact or handoff the skill must emit.

Suggestions

Name the exact commands to run for validation (e.g., the specific plugin validation and SDK proof commands invoked via the repository wrapper) instead of deferring to 'the smallest relevant local check'.

Include a short example stage-result artifact showing the required fields (schema_version, stage, status, evidence_refs, blocked_by, next_stage) so the deliverable is copy-paste concrete.

Add one example handoff line to eval-report and one example blocker with 'the smallest recovery step' to make step 5 of the Procedure executable rather than descriptive.

DimensionReasoningScore

Conciseness

The body is lean and directive with no explanations of concepts Claude already knows; every section ("Required inputs", "Deliverables", "Procedure") carries operational content, matching anchor 4 ('minor instances of over-explanation that could be trimmed'). It is not a 5 because the "When to use" section duplicates the frontmatter description verbatim and a few phrases ("Perform only the work owned by review") are abstract filler, but it is well above anchor 3's 'some unnecessary explanation'.

4 / 5

Actionability

Guidance is partially concrete — exact enums ("pass, fail, blocked, or not_checked") and named output fields ("schema_version, stage, status, evidence_refs, blocked_by, and next_stage") — but the actual checks are deferred to judgment ("Run the smallest relevant local check"; "run plugin validation and SDK proof commands from the repository wrapper" without naming the commands), and no example stage-result artifact or handoff is shown. This matches anchor 3 ('Some concrete guidance but incomplete... missing key details') rather than anchor 4's 'mostly executable guidance', since no concrete command or example is given anywhere in the body.

3 / 5

Workflow Clarity

The five-step "Procedure" is clearly sequenced, and the "Validation" section supplies an explicit fail-fast checkpoint ("stop at the first failed required gate... do not proceed to downstream stages until the failure is resolved or explicitly waived") plus recovery routing in "Failure modes". This matches anchor 4 ('Clear sequence with most checkpoints present; minor validation gaps'); it stops short of anchor 5 because the validation commands themselves are not explicit (no concrete command invocations or artifact example).

4 / 5

Progressive Disclosure

The body is a concise overview (~55 lines) with a well-signaled, one-level-deep References section — "Stage contract: [contract](./references/contract.yaml)", "Eval cases", "Task profile", "Source context" — and all four referenced files exist in ./references/ with no nested instruction references (source-context.yaml's upstream paths are provenance metadata, not chained references). This matches anchor 5: clear overview, appropriately split content, easy navigation.

5 / 5

Total

16

/

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.

A strong description that clearly states what the skill does and gives an explicit, well-phrased 'Use when' clause with multiple natural trigger terms. The only weaknesses are minor: the broad 'review' trigger creates some overlap risk with generic review skills, and a few common user phrasings are not covered.

DimensionReasoningScore

Specificity

"Review the completed slice for correctness, risk, evidence gaps, and next-stage blockers" names several specific review dimensions (correctness, risk, evidence gaps, blockers), matching the anchor 'Lists several specific actions; minor gaps in coverage'. It is not a 5 because it names one action verb (review) with focus areas rather than multiple distinct concrete actions with comprehensive coverage, and it stays above 3 because the enumerated review targets go well beyond 1-2 generic actions.

4 / 5

Completeness

The description explicitly answers both questions: what ("Review the completed slice for correctness, risk, evidence gaps, and next-stage blockers") and when ("Use when the user asks for review, PR readiness, risk assessment, blocker identification, or post-work verification") with concrete trigger phrases. This directly matches anchor 5's pattern of a clear what plus an explicit 'Use when' clause with concrete triggers.

5 / 5

Trigger Term Quality

"Use when the user asks for review, PR readiness, risk assessment, blocker identification, or post-work verification" offers good natural keyword coverage with several phrasings users would actually say, matching anchor 4 ('Good keyword coverage; a few natural terms missing'). It falls short of anchor 5's comprehensive synonyms (e.g. missing 'check my work', 'QA', 'is this ready to merge') but clearly exceeds anchor 3, which expects missing common variations.

4 / 5

Distinctiveness Conflict Risk

The niche (post-slice staged review with "evidence gaps" and "next-stage blockers") is mostly distinct from general skills, matching anchor 4's 'minor overlap risk with closely related skills'. It is not a 5 because the bare trigger term "review" and "PR readiness" overlap with generic code-review skills, but it is well above anchor 3 since the staged-lifecycle vocabulary (completed slice, next-stage blockers) pins it to a specific pipeline context.

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

jscraik/Agent-Skills

Path

Plugins/synaipse-harness/skills/sy-review/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.