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.

78

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

100%

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 well-structured, actionable migration runbook: executable commands and JSON snippets, a sequenced six-step workflow with audit and verification checkpoints, and clean section organization. It stays concise by including only Flows/Dune-specific knowledge Claude lacks.

DimensionReasoningScore

Conciseness

The body is lean and action-oriented; its explanatory prose (e.g. CSP enforcement, the deployment/deployments key rename) conveys domain-specific Flows/Dune knowledge Claude does not already have, so every token earns its place rather than padding with general concepts. It is not the level-2 case of unnecessary explanation that could be tightened.

3 / 3

Actionability

Provides copy-paste-ready, executable artifacts — concrete grep commands and complete JSON snippets for app.json, manifest.json, and deploy scripts — rather than pseudocode or abstract direction, matching the fully-executable anchor at 3.

3 / 3

Workflow Clarity

A clear six-step sequence with an upfront audit, skip-if-correct checkpoints ('If infra is already appsApi, skip this step'), and a Step 6 final verification grep that lists remaining hits for resolution — giving explicit validation steps and a feedback loop rather than the checkpoint-absent level-2 case.

3 / 3

Progressive Disclosure

No bundle files exist; the skill is a single cohesive linear migration recipe organized into clearly headed sections with no nested references, so navigation is easy and there is no monolithic-wall or deeply-nested-reference failure that would drop it to 1 or 2.

3 / 3

Total

12

/

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.

The description is strong across all dimensions: it names concrete migration actions, supplies natural user-spoken trigger phrases, and explicitly pairs the 'what' with a 'Use when...' clause in third-person voice. No vague fluff or over-claims are present.

DimensionReasoningScore

Specificity

Lists multiple 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, and updates deploy scripts to @cognite/cli' — matching the score-3 anchor of several specific concrete actions rather than the partial domain-only anchor at 2.

3 / 3

Completeness

Explicitly answers both 'what' (the orchestrated migration steps) and 'when' via 'Use this whenever a user says ...', satisfying the explicit-trigger requirement that would otherwise cap completeness at 2.

3 / 3

Trigger Term Quality

Covers natural phrasings a user would actually say — 'migrate to Flows', 'migrate to new infra', 'move from dune to flows', 'migrate legacy app' — giving good coverage of natural terms rather than jargon-only or missing-common-variations at 2.

3 / 3

Distinctiveness Conflict Risk

Targets a clear niche — 'migrating a legacy Dune app to the new Flows app hosting infrastructure' — with distinct triggers unlikely to fire for unrelated skills, matching the clear-niche anchor at 3 rather than the overlap-prone anchors at 1-2.

3 / 3

Total

12

/

12

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.