CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review

Review recent changes - run all validators and report status

Quality

71%

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 ./plugins/pragma/skills/review/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

81%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 a strong, highly executable workflow: concrete commands, explicit precedence and fallback handling, a stop-on-failure lint checkpoint, and a clear report format. Its main weaknesses are repetition of the no-rules fallback and a long inline report template that inflates the token budget and could be split into a reference file.

Suggestions

State the no-project-rules fallback once (e.g., only in Step 2) and drop the repetitions in the intro and the Rules section.

Move the 43-line report template to a references/report-format.md file and keep a two-line summary of the required sections inline.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete commands, but the no-rules fallback is stated three times ("Step 2 (rule injection) runs before validation. If no project rules are found...", "If no rule files are found: Log 'No project rules found...'", and the Rules section's "If no project rules exist, proceed with validator built-in rulesets"), the --diff-filter letter decode is background knowledge, and the 43-line mock report template is a large token outlay. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than the minor-trims-only bar of a 4.

3 / 5

Actionability

Guidance is fully executable throughout: the combined git-diff collection one-liner, per-language lint pipelines prefixed with 'set -o pipefail' (golangci-lint / uv run pre-commit / pnpm run lint), explicitly named validator tasks (security, state-machine, go-effective, go-proverbs, python-style, typescript-style), and a complete output template. Commands are copy-paste ready and cover the common cases, matching the top anchor.

5 / 5

Workflow Clarity

Steps 1 through 5 are clearly sequenced with an explicit precedence ladder for rules, an explicit fallback ('skip to Step 3'), a validation checkpoint with recovery direction ('If linters fail, report and stop - fix these first'), parallelized semantic validators, and severity-separated aggregation. The skill is read-only reporting, so the destructive/batch cap does not apply; this matches the 'explicit validation steps; feedback loops for error recovery' anchor.

5 / 5

Progressive Disclosure

No bundle files exist; the 161-line body is well-sectioned with clear step headers, and the '/setup-project' pointer is one level deep and clearly signaled. However, the 43-line mock report template and the per-language lint defaults are inline content that could live in a reference file, which is a minor organization gap consistent with 'good structure; most content is appropriately placed' rather than the fully split, reference-driven structure of a 5.

4 / 5

Total

17

/

20

Passed

Description

50%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 states a clear what (run all validators on recent changes and report status) in a natural, concise phrase, but omits any when-to-use trigger guidance and never specifies which validators or languages it covers. It is serviceable but generic, leaving trigger matching and distinctiveness to luck.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when the user asks to review recent changes, check a diff, or validate code before committing.'

Name the concrete coverage, e.g. '...including linting (Go, Python, TypeScript), security, state-machine, and error-handling validation.'

Include natural synonyms such as 'code review', 'check my changes', or 'diff' to improve trigger matching against generic review requests.

DimensionReasoningScore

Specificity

"run all validators" and "report status" name the change-review domain and a couple of actions, but the validators themselves are never enumerated (lint, security, state-machine, etc.), matching the 'names domain and 1-2 concrete actions, but not comprehensive' anchor. It is not a 4 because no specific capability is listed, and not a 2 because it goes beyond a bare domain label.

3 / 5

Completeness

The 'what' is stated clearly ("run all validators and report status") but there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the rubric guideline. Not a 4 because the 'when' is entirely absent rather than merely imprecise.

3 / 5

Trigger Term Quality

"Review recent changes" is a natural user phrase, but there are no synonyms ("code review", "check my changes", "lint") or file extensions, and "validators" is internal jargon users would not say. This fits 'some relevant keywords but missing common variations or synonyms'; it lacks the broader natural-term coverage of a 4.

3 / 5

Distinctiveness Conflict Risk

"Review recent changes" overlaps broadly with generic code-review/PR-review skills, though "run all validators" signals a specific validator-suite niche. This matches 'somewhat specific but could still overlap with similar skills'; the validator framing keeps it above a 2.

3 / 5

Total

12

/

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

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository

peteski22/agent-pragma

Path

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