flows-app-brief

Certification coach for Flows apps. Captures the app name, value case, persona, problem, and design intent through a structured conversation and writes App-Brief.md at the repo root. This is the FIRST step of the Flows app certification flow — run it immediately after `npx @cognite/cli apps create`, before building. Use when the user asks to start an app brief, run the certification coach, fill out the app brief, or run flows-app-brief.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

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 highly actionable, well-sequenced coaching skill with strong validation gates and copy-paste templates; its main weakness is mild verbosity from repeated rules and the full inlining of material that could partly live in a one-level-deep reference file.

Suggestions

Dedupe the operating rules — 'Present, do not save', 'Always confirm before saving', and 'Never invent' each appear in both the 'Operating rules' section and 'Step 0'; state them once and reference them.

Consider extracting the App-Brief.md YAML/markdown template block into a references/brief-template.md file referenced one level deep, trimming the SKILL.md overview.

Trim the per-field challenge-quote examples (good examples kept in mind) to one representative line each to tighten token budget.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient, assuming Claude's competence, but the recurring coaching-rule refrains (e.g. repeated 'Present, do not save' / 'Always confirm before saving' / 'Never invent' stated in both the rules section and Step 0) and lengthy challenge-quote examples could be trimmed without losing clarity.	4 / 5
Actionability	Guidance is fully executable: exact pre-scan file-to-field mapping tables, a literal AskQuestion option structure, copy-paste YAML/Markdown templates for App-Brief.md, and concrete challenge prompts for each coached field with good examples to keep in mind.	5 / 5
Workflow Clarity	A clearly sequenced Preflight → Step 0–5 flow with explicit validation checkpoints: the preflight skills-pull sentinel Glob, the 'do not write the file if any required field is still empty — return to coaching' gate, and feedback loops for retrying failed pulls and re-challenging vague answers.	5 / 5
Progressive Disclosure	Content is well-organized into clearly signaled sections (Preflight, Operating rules, Step 0–5) with no nested references and no bundle files to mis-link; it scores 4 rather than 5 because substantial reference material (the per-field rubric, spec-kit mapping, and the App-Brief template) is fully inlined where a one-level-deep reference file could reduce the overview's bulk.	4 / 5
	Total	18 / 20 Passed

Description

91%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, well-scoped description that names concrete actions and gives explicit, multi-variant trigger guidance aligned to the skill's invocation name. Its only soft spot is mild overlap risk with sibling certification-flow skills that share the same vocabulary.

Suggestions

Add a one-clause differentiator naming what this step does that the later build/review/submit steps do not (e.g. 'only captures intent — does not build or review code'), to sharpen distinctiveness against sibling certification-flow skills.

Dimension	Reasoning	Score
Specificity	Concrete actions are named — 'Captures the app name, value case, persona, problem, and design intent through a structured conversation and writes App-Brief.md' — covering several specific capture-and-write steps with only minor gaps (e.g. no mention of the validation/coaching challenges).	4 / 5
Completeness	It explicitly answers both 'what' (captures structured fields and writes App-Brief.md) and 'when' ('Use when the user asks to start an app brief, run the certification coach, fill out the app brief, or run flows-app-brief'), with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural trigger phrases a user would actually say are comprehensively covered — 'start an app brief', 'run the certification coach', 'fill out the app brief', 'run flows-app-brief' — including the skill's own invocation name and several phrasings.	5 / 5
Distinctiveness Conflict Risk	The Flows app certification niche is distinct and self-naming (flows-app-brief), but the broad coaching/brief framing could mildly overlap with adjacent certification-flow skills (build, review, submit) since they share the same flow vocabulary.	4 / 5
	Total	18 / 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-app-brief/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.