CtrlK
BlogDocsLog inGet started
Tessl Logo

flows-code-review

Run the technical (code) review step of Flows app certification in a local git app. Loads flows-review-checks for the actual bar, then writes artifacts under reviews/code-review/feedback-round-<N>/. Use when the user asks for a Flows code review, technical review, pre-submit review, app certification code review, or "run flows-code-review". Re-run until 0 open Must Fix items remain before moving on to flows-design-review.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

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.

A tightly written orchestrator body with strong executable commands, a clear sequenced workflow, validation checkpoints, and a re-run feedback loop. The only weak spots are minor redundancy in the summary block and the absence of local bundle files to demonstrate file-level progressive disclosure.

DimensionReasoningScore

Conciseness

Lean and assumes Claude's competence (no padding about what code review is), but the Must/Should/Nice-Fix-open summary block is duplicated across Step 2 and Step 3 and 'When to stop' restates the Step 3 loop condition — minor trim opportunities that keep it just below the 'every token earns its place' 5-anchor.

4 / 5

Actionability

Provides fully executable, copy-paste-ready commands (git rev-parse, npx @cognite/cli apps skills pull x2, curl fallback x2, Glob path) plus a concrete output-file table and report template, covering the runner's common cases; not 4 because there are no real gaps in the executable guidance.

5 / 5

Workflow Clarity

Clear Pre-checks -> Step 1 -> Step 2 -> Step 3 -> When-to-stop sequence with an explicit Step 3 verify checklist, a re-run feedback loop until 'Must Fix open: 0', and a curl error-recovery fallback; the destructive/batch 3-cap does not apply since the skill explicitly forbids applying fixes.

5 / 5

Progressive Disclosure

Well-sectioned overview that delegates the detailed bar one level deep to flows-review-checks, clearly signaled via pull commands and a Glob path, with content appropriately split between runner and bar; held at 4 rather than 5 because no local bundle structure exists and the summary block is duplicated, leaving minor organization gaps.

4 / 5

Total

18

/

20

Passed

Description

100%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, third-person description that pairs concrete runner actions and an exact output path with an explicit multi-trigger 'Use when' clause and a well-scoped niche. It assumes no verbosity penalty since every clause carries information.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions ('Run the technical (code) review step', 'Loads flows-review-checks', 'writes artifacts under reviews/code-review/feedback-round-<N>/', 'Re-run until 0 open Must Fix items remain') with a concrete output path, matching the comprehensive-coverage 5-anchor rather than the 4-anchor which requires minor gaps.

5 / 5

Completeness

Explicitly answers both what (run review step, load the bar, write artifacts to a named path, re-run) and when (concrete 'Use when the user asks for…' trigger phrases), matching the 5-anchor pattern exactly; not 4 because 'when' is already concrete, not merely present.

5 / 5

Trigger Term Quality

The 'Use when' clause enumerates five natural phrasings — 'Flows code review, technical review, pre-submit review, app certification code review, or "run flows-code-review"' — giving comprehensive coverage of how a user would actually request this skill.

5 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (Flows app certification technical review), is explicitly distinguished from flows-design-review, and every trigger carries 'Flows'/'certification', so conflict with generic code-review skills is minimal.

5 / 5

Total

20

/

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.