CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

74

Quality

93%

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 strong, lean runner skill: fully executable commands with fallbacks, a clearly sequenced workflow with explicit verification and a re-run feedback loop, and correct delegation of the review bar to an external skill. The only deductions are minor repetition of the do-not-score warnings and an inline report template that slightly bloats the single-file body.

Suggestions

Collapse the repeated do-not-score warnings (intro and Step 1) into one statement to trim redundancy.

Move the verbatim code-review-report.md template block into a references/ file (e.g. references/report-template.md) and keep only the required-sections summary inline.

State the fallback ordering once (CLI pull → curl from main) and drop the duplicated 'if the CLI pull fails' framing to shorten Step 1.

DimensionReasoningScore

Conciseness

The body is dense and imperative with zero concept explanation ("Checks and scoring live in flows-review-checks. Do not copy them here."), but the do-not-score warnings repeat across the intro and Step 1 ("Do not score from memory" vs "Do not score from whatever is already in the app's skills/ folder"), leaving minor trimmable redundancy. It fits the efficient-with-minor-trimming 4 anchor rather than every-token-earns-its-place 5.

4 / 5

Actionability

Everything is executable: exact pull commands ("npx @cognite/cli@latest apps skills pull --skill flows-review-checks"), curl fallbacks with full URLs, a concrete Glob pattern, exact output filenames, and a copy-paste report template with required labels. This matches the fully-executable 5 anchor; it is not 4 because no key detail is missing for the runner's portion of the work.

5 / 5

Workflow Clarity

The sequence is explicit (pre-checks → pull checks → write artifacts → runner verify → stop condition) with a 3-item verification checklist and a real feedback loop: "Re-run this skill until Must Fix open: 0". Validation checkpoints are present, so the missing-validation cap does not apply; this fits the 5 anchor with an explicit error-recovery loop.

5 / 5

Progressive Disclosure

No bundle files exist (references/, scripts/, assets/ are absent), and the body appropriately delegates all check/scoring detail to the external flows-review-checks skill at one level with clear signaling. Sections are well organized, but the ~100-line body inlines the full report markdown template verbatim — good structure with a minor organization gap, fitting the 4 anchor rather than the cleanly-split 5 anchor.

4 / 5

Total

18

/

20

Passed

Description

96%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.

An excellent description: concrete actions with exact artifact paths, an explicit and multi-synonym 'Use when' trigger clause, and a clear pipeline position with a stop condition. The only weakness is that a couple of trigger phrasings ("technical review", "pre-submit review") are generically worded and could overlap with unrelated review requests.

Suggestions

Qualify the generic trigger phrasings, e.g. "Flows technical review" and "Flows pre-submit review", to reduce overlap with non-Flows review requests.

Optionally name the upstream/downstream boundary in the when-clause ("before flows-design-review") so a user asking for the design review step routes to the right skill.

DimensionReasoningScore

Specificity

Quotes like "Loads flows-review-checks for the actual bar, then writes artifacts under reviews/code-review/feedback-round-<N>/" and "Re-run until 0 open Must Fix items remain" list multiple concrete actions with exact paths; coverage of the skill's scope is complete, matching the comprehensive-actions anchor rather than the minor-gaps anchor at 4.

5 / 5

Completeness

Both questions are explicitly answered: the what ("Run the technical (code) review step of Flows app certification… writes artifacts under reviews/code-review/feedback-round-<N>/") and the when ("Use when the user asks for a Flows code review…"). This matches the 5 anchor exactly; it is not 4 because the when-clause is already fully explicit.

5 / 5

Trigger Term Quality

"Use when the user asks for a Flows code review, technical review, pre-submit review, app certification code review, or \"run flows-code-review\"" covers the natural synonyms a user would say plus the literal invocation string, matching the comprehensive-synonyms anchor.

5 / 5

Distinctiveness Conflict Risk

The Flows-certification framing creates a clear niche, but the bare trigger phrases "technical review" and "pre-submit review" could plausibly fire for non-Flows review requests — minor overlap risk, fitting the 4 anchor rather than the minimal-conflict 5 anchor.

4 / 5

Total

19

/

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

cognitedata/builder-skills

Path

skills/flows-code-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.