CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

review

Use when the user asks to review CURRENT uncommitted changes (staged, unstaged, branch diff) before committing, or to synthesize JiT tests against the diff — QA + lead-engineer verdict on quality, architecture, cleanup. Needs a diff, not old commits.

Quality

79%

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

Quality

Content

62%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 an exceptionally well-sequenced and validated workflow with concrete commands at nearly every step, but it is severely bloated: rules are restated multiple times with long narrative justifications, and no progressive disclosure exists — everything, including large subsystem details (JiT test synthesis, FR coverage, per-stack commands), is inlined in a single dense file. Half the length with reference files for the subsystems would preserve all the signal.

Suggestions

Deduplicate the repeated themes: state each rule once and reference it by number elsewhere — the review-never-edits constraint appears in Rule 12 and again in two long paragraphs under step 10, and the session-snapshot rule appears in both Rule 8 and step 1.

Split subsystems into reference files: move the JiT test synthesis taxonomy (steps 8a/8b), the FR coverage audit (step 4a), and the per-stack manifest-to-command mappings (step 2) into references/ and link them from a shorter SKILL.md, so the main file is a navigable overview.

Replace narrative anti-pattern essays (e.g. 'a review that ran the checks inline and wrote Parallel delegation unavailable...') with one-line imperatives, and add a single concrete example of a synthesized catching test to ground the skill's most novel operation.

DimensionReasoningScore

Conciseness

Noticeably verbose with pervasive redundancy: the review-never-edits rule is restated across Rule 12 and two more long paragraphs under step 10 ('This holds for production files, for tests, for the requirement documents...'), the snapshot rule appears in both Rule 8 and step 1, and the delegation section embeds narrative anti-pattern essays ('a review that ran the checks inline and wrote Parallel delegation unavailable... reported a fact that was false'). Not 1 because it never explains basic concepts Claude already knows; not 3 because the padding is pervasive rather than occasional — the file could lose roughly half its tokens without losing actionable information.

2 / 5

Actionability

Highly concrete and executable: exact commands ('git diff --stat', 'git worktree add <SCRATCH>/jit-parent-<sid> <parent-sha>'), manifest-to-command mappings ('deno.json → deno task check/test'), grep pattern lists, and a full report template. Not 5 because the skill's novel core operation — synthesizing a catching test — provides only mutation categories ('comparator flip, removed guard, inverted return') with no concrete example test, and a few directives remain judgment-level ('flag tight coupling').

4 / 5

Workflow Clarity

Eleven clearly sequenced steps with explicit validation checkpoints throughout: the empty-diff guard checks three exact commands, failing tests are classified against a parent baseline, the JiT dual-run filters pass-on-parent/fail-on-diff with a 3x flaky rerun, and a verification checklist plus a first-match-wins verdict ordering close the loop. Matches the 5 anchor (explicit validation, feedback loops, checklists).

5 / 5

Progressive Disclosure

No bundle files exist at all — references/, scripts/, and assets/ are absent — so the entire ~190-line rule set is inlined in one monolithic file. There is real structure (headings, numbered rules, steps) that enables navigation, matching the 'some structure but content that should be separate is inline' anchor: the JiT synthesis details, FR coverage audit, and per-stack command mappings clearly belong in separate reference files. Not 4 because nothing is split out; not 2 because structure is present rather than minimal.

3 / 5

Total

14

/

20

Passed

Description

87%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: it opens with an explicit 'Use when' trigger covering staged, unstaged, and branch-diff variations, states concrete capabilities, and explicitly distinguishes itself from old-commit review. The only weaknesses are the internal jargon ('JiT tests', 'lead-engineer verdict') that a user would never say verbatim.

DimensionReasoningScore

Specificity

Names several concrete actions — 'review CURRENT uncommitted changes (staged, unstaged, branch diff)', 'synthesize JiT tests against the diff', 'QA + lead-engineer verdict on quality, architecture, cleanup' — which matches the 'several specific actions with minor gaps' anchor. Not 5 because the compressed phrasing ('QA + lead-engineer verdict', 'JiT tests') is not fully comprehensive or self-explanatory; not 3 because it goes well beyond 1-2 actions.

4 / 5

Completeness

Explicitly answers both: 'Use when the user asks to review CURRENT uncommitted changes... before committing' is a concrete when-clause, and 'QA + lead-engineer verdict on quality, architecture, cleanup' plus 'synthesize JiT tests against the diff' states the what. Matches the 5 anchor (both what and when explicit with concrete trigger phrases), not 4, since the when is specific rather than merely present.

5 / 5

Trigger Term Quality

Good natural-term coverage with synonyms users would actually say: 'review', 'uncommitted changes', 'staged', 'unstaged', 'branch diff', 'before committing'. Falls short of 5 because 'JiT tests' is internal jargon users will not say, and common variants like 'pre-commit review' or 'look over my diff' are missing.

4 / 5

Distinctiveness Conflict Risk

'Needs a diff, not old commits' explicitly excludes the nearest neighboring skill (commit-history review), and the trigger is scoped to current uncommitted changes plus JiT test synthesis — a clear niche with minimal conflict risk.

5 / 5

Total

18

/

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

referenced_paths_exist

Referenced path issues: 2 missing

Warning

Total

15

/

16

Passed

Repository

korchasa/flowai-plugins

Path

plugins/flowai/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.