setup-flows-auth

MUST be used when migrating an existing React app to Flows, or when no Flows auth is wired up. Detects classic vs Apps API flow from `app.json` `infra` field, installs the right packages, and wires up the entry file. No-op when a valid auth setup is already in place. Triggers: migrate to Flows, add Flows auth, DuneAuthProvider, AppSdkAuthProvider, connectToHostApp, useDune, Flows setup, setup auth, missing auth provider, CDF authentication, Fusion iframe auth.

Quality

85%

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

82%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 high-quality, executable wiring recipe with a clear decision point and sequenced steps; code is copy-paste ready for both the Classic and Apps API flows. The main improvement would be adding a final verification step (e.g., run the dev server / confirm auth) to close the workflow-clarity gap.

Suggestions

Add a final verification step to the workflow (e.g., run the dev server and confirm a successful Fusion auth handshake) to turn the validation gap into an explicit checkpoint.

Trim the per-plugin rationale bullets in Step 3 or move them to a collapsible aside to push conciseness toward a lean 5.

Consider a one-line 'Quick start' overview at the top that points to the two flows, giving a clearer overview-to-detail structure for progressive disclosure.

Dimension	Reasoning	Score
Conciseness	Dense and technical, assuming Claude knows React/Vite; a few rationale asides like 'the Fusion parent is HTTPS' and the plugin bullets are useful but slightly trimmable, keeping it just under a lean 5.	4 / 5
Actionability	Fully executable, copy-paste-ready code for both flows (vite.config, main.tsx, App.tsx, useDune/useCogniteSdk) plus explicit package tables and detected package-manager install commands, covering the common cases concretely.	5 / 5
Workflow Clarity	A clearly sequenced 5-step process opens with a validation gate (Step 1 'decide whether to act' with explicit no-op conditions) and guards the destructive cleanup ('If unsure, leave it and flag'), but lacks a final build/run verification checkpoint, leaving a minor validation gap.	4 / 5
Progressive Disclosure	Well-organized into a decision table plus Steps 1-5 with shallow, single-level structure and no nested references, and no bundle files exist; for a focused wiring recipe the inline code is appropriately placed, though there is no overview-to-detail split.	4 / 5
	Total	17 / 20 Passed

Description

87%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 strong: it states concrete capabilities, gives an explicit use-when clause plus a dedicated trigger list, and occupies a distinctive niche. It sits just below top marks only on specificity and trigger breadth, where a touch more coverage would close the gap.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'Detects classic vs Apps API flow from `app.json` `infra` field, installs the right packages, and wires up the entry file' plus a no-op guard — giving broad coverage of the task, with only minor gaps (vite config and cleanup not mentioned).	4 / 5
Completeness	Explicitly answers both what (detect flow, install packages, wire entry file, no-op) and when ('MUST be used when migrating an existing React app to Flows, or when no Flows auth is wired up' plus a concrete 'Triggers:' list).	5 / 5
Trigger Term Quality	Good keyword coverage spanning natural phrases ('migrate to Flows', 'add Flows auth', 'setup auth', 'missing auth provider') and technical component names users would paste when debugging, though not the textbook comprehensive-plus-extension set that anchors a 5.	4 / 5
Distinctiveness Conflict Risk	A clear narrow niche (Flows auth wiring for React apps in Fusion/CDF) with highly distinctive triggers like 'DuneAuthProvider', 'connectToHostApp', and 'useDune' that few other skills would claim, yielding minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

87%

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 — 14 / 16 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	14 / 16 Passed

Repository: cognitedata/builder-skills
Path: skills/setup-flows-auth/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.