CtrlK
BlogDocsLog inGet started
Tessl Logo

flows-review-checks

Canonical Flows technical-review checks and scoring (hunt commands, coverage scope, package audit, public criteria, Must/Should/Nice). Loaded by flows-code-review and by any external review skill. Do not copy these checks into another skill. Do not use this skill to fix code. Use when an orchestrator says to load flows-review-checks, or when aligning two review flows on the same bar.

70

Quality

86%

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

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.

The body is a highly actionable, well-sequenced review runbook with executable commands, explicit validation checkpoints, and a complete verify checklist. Its only notable weakness is that a large single file with repeated criteria-table patterns could benefit from splitting dense reference material into a separate file.

Suggestions

Move the per-criterion scoring tables (1.1, 1.3-1.6, 2.1-2.6, 3.1) into a referenced CRITERIA.md file, keeping SKILL.md as a lean overview pointing to it.

Consolidate the repeated 'Fail this criterion (1-2) if' phrasing into a single shared scoring convention to reduce repetition.

DimensionReasoningScore

Conciseness

Mostly efficient with direct commands and terse scoring rubrics, avoiding explanation of concepts Claude already knows, but the caller-contract intro and repeated 'Fail this criterion (1-2) if' patterns across criteria tables could be tightened.

4 / 5

Actionability

Provides copy-paste-ready bash greps, exact commands ('npm outdated --json', 'npx vitest run --coverage'), table templates, and a concrete TypeScript DI example covering the common review cases.

5 / 5

Workflow Clarity

Clear numbered Steps 1-6 with explicit validation checkpoints ('If a search was not run, that check is not a pass', 'Only after Step 1.1') and a Step 6 verify checklist with feedback loops, satisfying the destructive/batch validation requirement.

5 / 5

Progressive Disclosure

Well-organized into clearly headed sections with the external code-quality reference one level deep and clearly signaled, but it is a long single file with dense criteria tables that could be offloaded to a reference file; no bundle files exist.

4 / 5

Total

18

/

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.

The description is specific, distinct, and answers both what and when, with strong anti-conflict boundary guidance. Its main weakness is that the trigger framing is orchestrator-driven rather than user-utterance-oriented, which slightly limits natural trigger-term quality.

Suggestions

Add user-oriented trigger phrases (e.g. 'Use when the user asks for a Flows technical review or to score a submission against the Flows bar') alongside the orchestrator-load trigger.

Include natural synonyms and the file/term users actually say ('code review score', 'review bar', 'submission review') to broaden trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain ('technical-review checks and scoring') and enumerates concrete components — 'hunt commands, coverage scope, package audit, public criteria, Must/Should/Nice' — giving comprehensive coverage of what the skill defines.

5 / 5

Completeness

Explicitly states both what ('Canonical Flows technical-review checks and scoring') and when ('Use when an orchestrator says to load flows-review-checks, or when aligning two review flows on the same bar'), but the 'when' is framed around orchestrator load events rather than concrete user trigger phrases.

4 / 5

Trigger Term Quality

Includes relevant triggers like 'technical-review', 'review skill', and 'aligning two review flows', but the triggers are orchestrator-oriented ('when an orchestrator says to load flows-review-checks') rather than phrases a user naturally says, and a few common synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche with explicit non-overlap guidance ('Do not copy these checks into another skill', 'Do not use this skill to fix code') and distinct triggers, minimizing conflict risk with other review skills.

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

Total

15

/

16

Passed

Repository
cognitedata/builder-skills
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.