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.
76
96%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is an excellent skill description that clearly defines its purpose, lists concrete actions, and provides explicit trigger guidance with natural user phrases. It uses proper third-person voice throughout and carves out a very distinct niche that would be easy for Claude to match against user requests. The description is comprehensive without being unnecessarily verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: audits current state, updates app.json to appsApi infra, delegates auth wiring to setup-flows-auth, creates/updates manifest.json network permissions, and updates deploy scripts to @cognite/cli. | 3 / 3 |
Completeness | Clearly answers both 'what' (audits state, updates app.json, delegates auth wiring, creates manifest.json, updates deploy scripts) and 'when' (explicit 'Use this whenever...' clause with multiple trigger phrases and a general condition). | 3 / 3 |
Trigger Term Quality | Includes excellent natural trigger terms users would say: 'migrate to Flows', 'migrate to new infra', 'move from dune to flows', 'migrate legacy app', plus domain-specific terms like 'Dune', 'Flows', 'app hosting'. These are realistic phrases a user would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a very specific niche: migrating legacy Dune apps to Flows infrastructure. The domain-specific terminology (Dune, Flows, appsApi, manifest.json, @cognite/cli) makes it extremely unlikely to conflict with other skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
92%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted migration skill with excellent workflow structure: it audits before changing, provides concrete JSON and command examples at every step, includes skip conditions, and verifies completion. The content is concise and respects Claude's intelligence throughout. The only minor weakness is that all content lives in a single file, though the skill's length makes this a minor concern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every section is lean and purposeful. No unnecessary explanations of what Dune or Flows are, no padding about why migration matters. The audit summary format, JSON snippets, and grep commands all earn their place. | 3 / 3 |
Actionability | Provides fully concrete, executable guidance: exact JSON structures for app.json and manifest.json, specific grep commands for scanning, exact deploy script replacements, and clear delegation to setup-flows-auth. Copy-paste ready throughout. | 3 / 3 |
Workflow Clarity | Clear 6-step sequence with an upfront audit (Step 1) before any changes, skip conditions (e.g., 'if infra is already appsApi, skip'), a final verification step (Step 6) with grep to catch remaining legacy references, and a completion checklist. The feedback loop of audit → migrate → verify is well-structured. | 3 / 3 |
Progressive Disclosure | The skill appropriately delegates auth setup to the setup-flows-auth skill, but all other content is inline in a single file. The manifest.json rules section and deploy scripts could potentially be separated, though for a skill of this length (~100 lines) it's borderline acceptable. No bundle files are provided to reference, which limits the score slightly. | 2 / 3 |
Total | 11 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata.version' is missing | Warning |
Total | 9 / 11 Passed | |
- Repository
- cognitedata/builder-skills
- Commit
d6af887
- 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.