flows-external-app-submit

Final gate of the Flows app certification flow for external submission. Verifies that flows-app-brief, flows-code-review, and flows-design-review have all been run and are in a passing state (App-Brief.md complete, 0 Must Fix in latest code review, design average ≥ 3.8), then runs `npx @cognite/cli apps submit` to zip the repo and pre-populate the submission form. Use when the user asks to submit a Flows app for certification, run flows-external-app-submit, or finalize an app for external review.

Quality

90%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

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 thorough, executable certification-gate workflow with strong validation checkpoints and copy-paste-ready commands and templates. The only real weakness is mild verbosity from repeated precondition/SKIPPED explanations and inlined stub templates that could be factored into a reference file.

Suggestions

Consolidate the SKIPPED-status rationale into one place and reference it from Steps 2, 3, 6, and 7 instead of re-explaining it each time, to tighten conciseness.

Move the two stub templates into a `references/stub-templates.md` file and point Step 0 at it, improving progressive disclosure and trimming the main body.

De-duplicate the Preconditions checklist against Steps 1–5 (e.g., have the steps reference the checklist rather than restating each item) to reduce token cost.

Dimension	Reasoning	Score
Conciseness	Efficient and assumes Claude's competence (no explanations of git, CLI, or basic concepts), but the precondition checklist is restated across the later steps and the SKIPPED rationale repeats in Steps 2, 3, 6, and 7 — minor trimming is possible, so it sits above the 3 anchor but below fully lean.	4 / 5
Actionability	Fully executable throughout — `git ls-files ... \| sort -V \| tail -1`, `test -f App-Brief.md`, exact regexes (`^- Must Fix open: (\d+)$`), the `npx @cognite/cli apps submit` command, and copy-paste stub templates with exact paths and content covering the common cases.	5 / 5
Workflow Clarity	Steps 0–8 are clearly sequenced with explicit PASS/FAIL/SKIPPED/WARN/BLOCK checkpoints, a final pass-fail table, hard guardrails ('stop here, do not run the CLI'), and retry guidance with the next skill to run; validation is present so the destructive/batch cap does not apply.	5 / 5
Progressive Disclosure	No bundle files exist and the single SKILL.md is well-sectioned with no nested references; however the ~40 lines of stub templates are inlined and could plausibly live in a separate reference file, leaving it just short of the cleanly-split score-5 anchor.	4 / 5
	Total	18 / 20 Passed

Description

92%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 crisply states both the verification actions and the submit action with concrete thresholds, plus an explicit 'Use when' trigger. Slightly below perfect only on trigger-term breadth, where a few natural synonyms (certify, publish) are absent.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions with precise thresholds — 'verifies that flows-app-brief, flows-code-review, and flows-design-review have all been run and are in a passing state (App-Brief.md complete, 0 Must Fix, design average ≥ 3.8), then runs `npx @cognite/cli apps submit` to zip the repo and pre-populate the submission form' — comprehensive coverage matching the score-5 anchor.	5 / 5
Completeness	Explicitly answers both what (verify three prior steps in a passing state, then run the CLI to zip and pre-populate the form) and when (concrete 'Use when...' trigger phrases), matching the score-5 anchor exactly.	5 / 5
Trigger Term Quality	'Use when the user asks to submit a Flows app for certification, run flows-external-app-submit, or finalize an app for external review' gives good natural-term coverage; a few synonyms (certify, publish) are missing, so it sits above the 3 anchor but below the comprehensive 5.	4 / 5
Distinctiveness Conflict Risk	Clear niche as the final gate of the certification flow, explicitly distinguished from the three prior review skills it depends on, with minimal conflict risk.	5 / 5
	Total	19 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: cognitedata/builder-skills
Path: skills/flows-external-app-submit/SKILL.md
Commit: c87160a

Reviewed: 5 days ago

Table of Contents

Discovery Implementation Validation

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.