CtrlK
BlogDocsLog inGet started
Tessl Logo

handle-startup-state

MUST be used when a Flows/Fusion app needs to read state it was launched with — a deep link, a shareable URL, or startup/bootstrap arguments set by a host embedding the app (e.g. a Flows dashboard widget). Triggers: initialState, connectToHostApp initialState, startup arguments, bootstrap state, initial state, deep link, restore state on mount, syncInternalState, customAppInternalState.

72

Quality

90%

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

86%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 well-structured, executable skill body with complete code and tests and clear sequencing. The only meaningful gap is the absence of an explicit validation/verification feedback loop in the workflow, though the closing checklist partly compensates.

DimensionReasoningScore

Conciseness

Lean and assumes competence (React/TypeScript, app-sdk), with nearly every line earning its place; a few prose passages such as 'Your app never needs to know how it got there' could be trimmed, keeping it just below a 5.

4 / 5

Actionability

Provides fully executable, copy-paste-ready TSX/TS for parsing, the hook, the UI wiring, the sync-back, and a complete vitest test file covering the common cases.

5 / 5

Workflow Clarity

A clear 5-step sequence with a closing checklist and defensive validation (try/catch, .catch), but it lacks an explicit validate-then-fix feedback loop, leaving a minor checkpoint gap.

4 / 5

Progressive Disclosure

Self-contained, well-sectioned SKILL.md with well-signaled one-level-deep references (peer skills and the public CDF docs guide) and no nested/inline bulk that belongs elsewhere.

5 / 5

Total

18

/

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.

A strong, explicit description that clearly states what the skill does and when to use it, with a rich natural-language trigger list. The only minor weakness is that the core action ('read state') is single-purpose even though several concrete scenarios are enumerated.

DimensionReasoningScore

Specificity

Names the domain (Flows/Fusion app reading launch state) and enumerates concrete scenarios — 'a deep link, a shareable URL, or startup/bootstrap arguments' — giving several specific capability contexts with only minor gaps.

4 / 5

Completeness

Explicitly answers both 'what' ('read state it was launched with') and 'when' ('MUST be used when...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

An explicit 'Triggers:' list covers natural phrases ('deep link', 'initial state', 'startup arguments', 'bootstrap state') plus synonyms and technical identifiers, giving comprehensive coverage.

5 / 5

Distinctiveness Conflict Risk

A narrow Flows/Fusion initialState niche with specific API names (connectToHostApp, syncInternalState) gives a clear trigger surface with minimal overlap 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

relative_links

Relative link issues: 3 suspicious

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.