CtrlK
BlogDocsLog inGet started
Tessl Logo

integrate-fusion-agent

Integrates a Flows/Dune app with the Fusion built-in PAIA agent panel using @cognite/app-sdk. Use this skill whenever a developer wants to: open the agent panel from their app, send the agent a contextual message, let the agent read app state (resources), or let the agent call actions in the app. Triggers: "fusion agent", "PAIA", "agent panel", "sendAgentMessage", "sendAgentLayoutMode", "agent server", "registerAgentServer", "connectToHostApp", "agent integration", "agent sidebar", "app-sdk agent". Always use this skill instead of manually writing agent integration code — it sets up the correct lifecycle, graceful fallback, and recommended file structure.

74

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, actionable integration guide with executable code, a well-sequenced workflow, verification checkpoints, and dense gotcha documentation. The only weakness is a hardcoded minimum SDK version that is time-sensitive and not isolated in a deprecated section.

Suggestions

Move the 'Minimum required version: 0.3.1' detail into an explicitly labeled versioning/old-patterns note so the time-sensitive number is isolated and easy to update, rather than embedded in Step 1 and the checklist.

Consider noting how to discover the current minimum version (e.g. 'check the installed @cognite/app-sdk version in package.json') instead of pinning a literal version that will go stale.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence, but it hardcodes a time-sensitive minimum version '0.3.1' (Step 1 and the checklist) outside any deprecated/old-patterns section, which the guideline says should penalize conciseness.

2 / 3

Actionability

Provides fully executable, copy-paste-ready TypeScript throughout — useHostApp hook, sendAgentLayoutMode/sendAgentMessage calls, createAgentResource/createAgentAction with Zod, the useAgentServer lifecycle, and an App.tsx wiring example.

3 / 3

Workflow Clarity

Clear Steps 0–6 sequence with a final verification checklist, explicit error handling (.catch() on register/unregister), and Symptom→Fix recovery loops in the Known pitfalls section, satisfying the explicit-validation anchor.

3 / 3

Progressive Disclosure

No bundle files exist, so scoring is on organization; the body is well-structured into clearly headed sections (Steps, Dev vs. production, Testing, Known pitfalls, Checklist) with no nested references and easy navigation.

3 / 3

Total

11

/

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.

A high-quality description: concrete capabilities, explicit 'Use when' guidance with rich trigger terms, third-person voice, and a clearly distinct niche. It cleanly satisfies every dimension without padding or over-claiming.

DimensionReasoningScore

Specificity

Lists multiple concrete actions — 'open the agent panel from their app, send the agent a contextual message, let the agent read app state (resources), or let the agent call actions' — matching the 'multiple specific concrete actions' anchor.

3 / 3

Completeness

Explicitly answers what ('Integrates a Flows/Dune app with the Fusion built-in PAIA agent panel') and when ('Use this skill whenever a developer wants to:' plus 'Always use this skill instead of manually writing agent integration code'), with explicit triggers present.

3 / 3

Trigger Term Quality

Broad natural-term coverage ('fusion agent', 'PAIA', 'agent panel', 'agent sidebar', 'agent integration') plus the exact SDK API names a developer would reference, with no major common variations missing.

3 / 3

Distinctiveness Conflict Risk

Narrow, ecosystem-specific niche (Cognite Fusion/PAIA via @cognite/app-sdk) with distinct triggers that are unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

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

Warning

Total

15

/

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.