Flows External App Submit

The final checkpoint before you ship a Flows app to Cognite's certification team. It verifies that your App-Brief.md exists and is complete, that your latest code review shows zero Must Fix issues, and that your design review scored at least 3.8, then runs the CLI submit command to package everything via git archive. The air-hatch feature is pragmatic: if you haven't run the full reviews yet, it offers to write SKIPPED stub reports so you can submit now and let the reviewer request real reviews later, saving you 40+ minutes of upfront tooling if you just want to get the process moving. Certification artifacts must be committed or the archiver silently drops them, so it blocks on that.

skills.sh installs: 1.1K
GitHub stars: 6
last updated: Aug 21, 2026

View on GitHub

Install

$ npx -y skills add cognitedata/builder-skills --skill flows-external-app-submit --agent claude-code

Installs into .claude/skills of the current project.

Files

Flows External App Submit

This is step 4 (final) of the Flows app certification flow:

flows-app-brief  →  build  →  flows-code-review  →  flows-design-review  →  flows-external-app-submit (this skill)

This skill does not rerun any review. It verifies the artifacts from the prior three steps and only then invokes the CLI submit command.

Preconditions (show these to the user first)

Before doing anything, print this checklist so the user knows exactly what is being verified:

App-Brief.md exists at repo root and all required frontmatter fields are populated.
The latest reviews/code-review/feedback-round-<N>/code-review-report.md is committed to git and reports Must Fix open: 0.
The latest reviews/design-review/feedback-round-<N>/design-review-report.md is committed to git and reports Average score: X.X with X.X ≥ 3.8.
Certification artifacts are committed — apps submit uses git archive HEAD and silently excludes uncommitted files.
A deploy bundle exists in .cognite-bundles/ and is not older than HEAD.