CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-app-to-flows

MUST be used when migrating a legacy Dune app to the new Flows app hosting infrastructure. Orchestrates the full migration: audits current state, updates app.json to appsApi infra, delegates auth wiring to setup-flows-auth, creates or updates manifest.json network permissions, and updates deploy scripts to @cognite/cli. Use this whenever a user says 'migrate to Flows', 'migrate to new infra', 'move from dune to flows', 'migrate legacy app', or wants to move their existing app to the new Flows app hosting.

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

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

The body is a tight, executable migration runbook with a well-sequenced workflow, validation checkpoints, and a clear final checklist. Minor conciseness gains are possible in the manifest rules and audit examples.

DimensionReasoningScore

Conciseness

The body is mostly efficient with concrete code/JSON blocks and minimal concept explanation, though the manifest network rules list and the duplicated audit examples add some length that could be trimmed slightly without losing clarity.

4 / 5

Actionability

It provides fully executable, copy-paste-ready JSON snippets, specific grep commands, and concrete deploy-script replacements covering the common migration cases.

5 / 5

Workflow Clarity

It lays out a clear six-step sequence with an upfront audit checkpoint, explicit skip-if-already-correct guards, a final verification grep, and a closing checklist plus next steps, satisfying the validation-checkpoint requirement for a config-mutating workflow.

5 / 5

Progressive Disclosure

For a self-contained skill with no bundle files, the content is well-organized into clearly signaled sections that fit comfortably inline, so progressive disclosure is appropriate without external references.

5 / 5

Total

19

/

20

Passed

Description

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

The description is excellent: specific, comprehensive on triggers, and clearly distinguishes a niche with low conflict risk. The only minor weakness is a degree of length from listing every migration area, which edges toward verbosity for a trigger description.

DimensionReasoningScore

Specificity

The description lists several specific concrete actions ("audits current state", "updates app.json to appsApi infra", "delegates auth wiring to setup-flows-auth", "creates or updates manifest.json network permissions", "updates deploy scripts to @cognite/cli"), giving comprehensive coverage; held below 5 only because the enumerated list reads more as a feature inventory than vivid, distinct action verbs.

4 / 5

Completeness

It explicitly answers both what the skill does (orchestrates the full migration across five enumerated areas) and when to use it, with concrete quoted trigger phrases in a "Use this whenever..." clause.

5 / 5

Trigger Term Quality

It includes comprehensive natural phrases a user would actually say ("migrate to Flows", "migrate to new infra", "move from dune to flows", "migrate legacy app") covering multiple synonyms and phrasings of the trigger.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (Dune-to-Flows app migration) with distinct trigger phrases unlikely to overlap with other skills, minimizing conflict risk.

5 / 5

Total

19

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

metadata_version

'metadata.version' is missing

Warning

Total

14

/

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.