CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

svelte-flow

Build node-based editors, interactive diagrams, and flow visualizations using Svelte Flow. Use when creating workflow editors, data flow diagrams, organizational charts, mindmaps, process visualizations, DAG editors, or any interactive node-graph UI. Supports custom nodes/edges, layouts (dagre, hierarchical), animations, and advanced features like proximity connect, floating edges, and contextual zoom.

Quality

82%

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

71%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 dense, largely executable Svelte 5 reference with accurate library-specific code and minimal fluff. Its main weaknesses are the complete absence of progressive disclosure (a 630-line monolithic file with no reference split) and a few executable-code gaps (unimported symbols, a missing './utils' helper).

Suggestions

Split the advanced features (floating edges, proximity connect, edge reconnection, delete-and-reconnect) and the Common Props listing into a references/ADVANCED.md file, linked from SKILL.md with clear 'See ADVANCED.md' signals, keeping only core setup, key concepts, and custom node/edge basics inline.

Bundle or inline the getEdgeParams helper used by the floating-edge example, and add the missing MarkerType/ConnectionLineType imports so every snippet is copy-paste executable.

Trim the repeated <script> import boilerplate in the Components section (Controls, MiniMap, Background, Panel each repeat the same import block) into a single example plus a component list.

DimensionReasoningScore

Conciseness

The body is dominated by version-specific, non-obvious code (Svelte 5 runes like "$state.raw", "$derived", "$props", immutable update patterns) with almost no fluff prose. Minor trimmable instances exist: repeated <script> import boilerplate across the Controls/MiniMap/Background/Panel sections and the marginal "Store Management (Alternative)" section. Not 5 because of these minor padded spots; not 3 since virtually every example carries library-specific information Claude cannot assume.

4 / 5

Actionability

Examples are copy-paste-ready Svelte 5 code covering setup, custom nodes/edges, events, layout, and export. Minor gaps: "MarkerType.ArrowClosed" and "ConnectionLineType" are used without imports, and the floating-edge example depends on "getEdgeParams" from './utils', a helper that is not defined anywhere in the bundle. Not 5 because these gaps break executability of specific snippets.

4 / 5

Workflow Clarity

Sections progress coherently from Installation to Core Setup to customization to advanced features, and no destructive or batch operations exist that would demand validation checkpoints. Not 5 because at ~630 lines it exceeds the simple-skill scope and offers no verification guidance for the fragile custom-node/edge registration steps; not 3 because sequencing is unambiguous and nothing risky lacks handling.

4 / 5

Progressive Disclosure

Headers organize the file well, but all ~630 lines are inlined in a single SKILL.md with no bundle files at all. Content that clearly belongs in separate reference files — the advanced features (floating edges, proximity connect, edge reconnection), the Common Props dump, and the Components section — sits inline, and there are no references to signal. This matches the anchor for structure present but content that should be separate kept inline.

3 / 5

Total

15

/

20

Passed

Description

88%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.

Strong description that explicitly answers both what and when with concrete, natural trigger terms covering the domain. Only minor weaknesses: a few missing common synonyms (flowchart, org chart) and slight over-trigger risk for non-interactive diagram requests.

DimensionReasoningScore

Specificity

"Build node-based editors, interactive diagrams, and flow visualizations using Svelte Flow" plus "Supports custom nodes/edges, layouts (dagre, hierarchical), animations, and advanced features like proximity connect, floating edges, and contextual zoom" lists multiple concrete actions with comprehensive coverage of the library's surface. Not 4: coverage extends beyond core actions into customization and advanced capabilities without notable gaps, matching the comprehensive anchor.

5 / 5

Completeness

What is explicit ("Build node-based editors... using Svelte Flow") and when is explicit with concrete trigger phrases ("Use when creating workflow editors, data flow diagrams, organizational charts, mindmaps..."). Clearly and explicitly answers both; not 4 because the when-clause is fully specific, not merely present.

5 / 5

Trigger Term Quality

"workflow editors, data flow diagrams, organizational charts, mindmaps, process visualizations, DAG editors" are natural phrases users would actually say. Not 5: common synonyms like "flowchart", "org chart", and "node graph" are missing, so keyword coverage is good but not comprehensive.

4 / 5

Distinctiveness Conflict Risk

The niche (Svelte Flow, interactive node-graph UIs) is clearly distinct from generic skills. Minor overlap risk: the when-clause ("organizational charts, mindmaps") could fire for static, non-Svelte diagram requests where an interactive editor library is wrong. Not 5 because of this slight over-trigger surface; not 3 since the Svelte Flow/library framing keeps it mostly distinct.

4 / 5

Total

18

/

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.

Validation — 14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (639 lines); consider splitting into references/ and linking

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository

freightCognition/linehaulai-claude-marketplace

Path

plugins/svelte-flow/skills/svelte-flow/SKILL.md

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.