CtrlK
BlogDocsLog inGet started
Tessl Logo

flows-code-review

Run the technical (code) review step of Flows app certification. Produces three artifacts under reviews/code-review/feedback-round-<N>/: review-files.md (per-file inventory), review-packages.md (dependency audit), and code-review-report.md (scored report with Must Fix / Should Fix / Nice Fix items). 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.

72

Quality

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-sequenced review workflow with concrete commands, templates, and explicit verification/feedback loops. Its main weakness is verbosity and a monolithic structure that inlines a large rubric and templates rather than offloading them to reference files.

Suggestions

Move the 12-criteria scoring rubric (Step 5) and the full report template (Step 6) into a reference file such as references/scoring-rubric.md, keeping SKILL.md as an overview that links one level deep.

Tighten repeated content: the Must/Should/Nice categorization is described in Step 5 and again in Step 6 — state it once and reference it.

Trim explanatory framing like 'What this review covers' inside the report template; Claude can derive that from the criteria list.

DimensionReasoningScore

Conciseness

The inlined 12-criteria rubric and DMS/Aura guidance are legitimately domain-specific, but the ~410-line body is verbose in places — categorization rules are restated between Step 5 and Step 6, and the report template restates 'What this review covers' verbiage Claude could infer.

2 / 3

Actionability

It gives exact one-shot commands ('npm outdated --json', 'npx vitest run --coverage'), concrete file paths, fully fleshed markdown templates, and per-criterion scored anchor tables that are copy-paste ready.

3 / 3

Workflow Clarity

A clear Pre-checks → Steps 1–7 → 'When to stop' sequence with an explicit Step 7 verification checklist and a re-run feedback loop ('Re-run until Must Fix open: 0') providing validation checkpoints.

3 / 3

Progressive Disclosure

No bundle files exist and the full 12-criteria scoring rubric plus large report templates are inlined directly in SKILL.md; sibling-skill reads are clearly signaled, but heavy reference content that could live in a separate file is kept inline.

2 / 3

Total

10

/

12

Passed

Description

100%

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 states concrete deliverables and gives explicit, natural-language trigger terms with a clear 'Use when' clause. It is well-scoped to a distinct certification step and unlikely to fire for the wrong skill.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions and artifacts: 'Produces three artifacts under reviews/code-review/feedback-round-<N>/: review-files.md (per-file inventory), review-packages.md (dependency audit), and code-review-report.md (scored report with Must Fix / Should Fix / Nice Fix items).'

3 / 3

Completeness

It explicitly answers both 'what' (produces three named artifacts / scored report) and 'when' via an explicit 'Use when the user asks for…' clause, so it is not merely implied.

3 / 3

Trigger Term Quality

It covers natural terms a user would say — 'Flows code review, technical review, pre-submit review, app certification code review, or "run flows-code-review"' — including the literal invocation phrase.

3 / 3

Distinctiveness Conflict Risk

It occupies a clear niche (Flows app certification technical review) and is explicitly scoped against the sibling 'flows-design-review', making conflict with unrelated skills unlikely.

3 / 3

Total

12

/

12

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.