CtrlK
BlogDocsLog inGet started
Tessl Logo

review-change

Review a proposed code change and its evidence when asked to assess implementation quality.

67

Quality

80%

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

Fix and improve this skill with Tessl

tessl review fix ./internal/adaptertest/testdata/all-agents/want/codex/files/.codex/skills/acr__example__all-agents__review-change/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

90%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 tight, single-purpose skill with an executable command, explicit output contract, and a clear validation checkpoint. The main gaps are the absence of error-recovery guidance and an orphaned reference file not surfaced in the body.

Suggestions

Add a brief feedback loop for the failure case, e.g. 'If it exits non-zero, report the failure and stop.'

Link to references/REFERENCE.md from the body (or remove it if unused) so every bundle file is clearly signaled.

DimensionReasoningScore

Conciseness

Lean and efficient: a one-line orientation, a single concrete step with its output contract, and a closing line; every token earns its place and assumes Claude's competence.

5 / 5

Actionability

Provides a fully executable command plus its exact output contract ('emits {"ok":true} on stdout and exits non-zero on failure'), copy-paste ready with no gaps.

5 / 5

Workflow Clarity

Sequence is clear with an explicit validation checkpoint (check.sh's ok/fail contract), but no error-recovery guidance is given for the failure case, leaving a minor gap.

4 / 5

Progressive Disclosure

The script path is clearly signaled one level deep and logic is appropriately split out of SKILL.md, but references/REFERENCE.md exists without being linked from the body, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

70%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 concise, third-person description that covers both what the skill does and when to invoke it, with natural trigger phrasing. It is solid but stops short of comprehensive action coverage and could sharpen its trigger conditions.

Suggestions

List the specific review actions performed (e.g. inspect diff, verify evidence files, check test coverage) to raise specificity.

Expand the 'when' clause with concrete trigger phrases users would say, such as 'Use when the user asks to assess implementation quality or verify a code change's evidence'.

DimensionReasoningScore

Specificity

Names the domain and 1-2 concrete actions ('Review a proposed code change and its evidence') but coverage is not comprehensive, matching the anchor for naming domain plus a couple actions.

3 / 5

Completeness

Explicitly answers both what ('Review a proposed code change and its evidence') and when ('when asked to assess implementation quality'); the when clause could be slightly more specific.

4 / 5

Trigger Term Quality

Includes natural user phrases ('review a proposed code change', 'assess implementation quality') with good coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

The evidence-and-implementation-quality framing is a fairly distinct niche with only minor overlap risk against generic code-review skills.

4 / 5

Total

15

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jbaruch/agentic-context-registry
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.