CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

getting-started

Create and render Table v9 with the svelte adapter. Route reusable createTableHook components, Query and Virtual integration, and framework setup; use table-state for reactive ownership.

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

93%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 an exemplary overview: a complete executable setup example, dense non-obvious constraints, and precise task-based routing to verified reference files. The only minor gap is the absence of validation or troubleshooting checkpoints for the setup workflow.

DimensionReasoningScore

Conciseness

The body is lean with zero filler: every sentence in "Essential constraints" carries non-obvious, version-specific rules ("`data` captured once cannot follow reassignment", "Put row-model slots after their prerequisite features") and it never explains concepts Claude already knows.

5 / 5

Actionability

Fully executable, copy-paste-ready Svelte component (imports, typed columns, `$state`, getter-based `createTable`, complete markup) plus concrete commands (`intent load @tanstack/table-core#core`) and specific inspection paths (`node_modules/@tanstack/svelte-table/dist/index.d.ts`).

5 / 5

Workflow Clarity

A clear sequence is present (load core intent first, then setup, then task-based routing, then API discovery) with an unambiguous primary action, but there are no validation or error-recovery checkpoints for setup failures such as version mismatches.

4 / 5

Progressive Disclosure

The "Load by task" section gives well-signaled, one-level-deep references to three real bundle files (create-table-hook.md, with-tanstack-query.md, with-tanstack-virtual.md), each matched to concrete task triggers, with setup and constraints appropriately inline and integration detail correctly split out.

5 / 5

Total

19

/

20

Passed

Description

66%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 specific and distinct, naming concrete actions and domain artifacts, but it completely lacks a "Use when..." trigger clause, which caps its completeness and weakens discoverability. Trigger term coverage is good but misses common variations like "TanStack" and "svelte-table".

Suggestions

Add an explicit "Use when..." clause, e.g. "Use when setting up or rendering TanStack Table v9 in Svelte 5 apps, or integrating Query or Virtual with a Svelte table."

Include common trigger variations such as "TanStack Table", "svelte-table", "@tanstack/svelte-table", and "virtualized rows" so users' natural phrasing matches.

Clarify that reactive-state and migration concerns route to sibling skills (e.g. "for v8 code or reactive state ownership, see the migration and table-state skills") to reduce overlap with those skills' triggers.

DimensionReasoningScore

Specificity

Lists several concrete actions with named artifacts ("Create and render Table v9 with the svelte adapter", "Route reusable createTableHook components, Query and Virtual integration"), though "framework setup" is slightly generic, leaving minor gaps in coverage.

4 / 5

Completeness

The "what" is clear (create, render, route, integrate), but there is no "Use when..." clause or equivalent explicit trigger guidance; "use table-state for reactive ownership" is a routing instruction rather than a usage trigger, capping completeness at 3.

3 / 5

Trigger Term Quality

Good keyword coverage including natural terms users would say ("Table v9", "svelte adapter", "createTableHook", "Query", "Virtual", "table-state", "reactive"), but common variations like "TanStack", "svelte-table", and "virtualized rows" are missing.

4 / 5

Distinctiveness Conflict Risk

Clearly scoped to the Svelte adapter for Table v9 with specific artifacts (createTableHook, Query, Virtual, table-state), but it explicitly names sibling-skill territory (table-state, reactive ownership), creating minor overlap risk with closely related skills.

4 / 5

Total

15

/

20

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

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

relative_links

Relative link issues: 2 suspicious

Warning

Total

13

/

16

Passed

Repository

TanStack/table

Path

packages/svelte-table/skills/getting-started/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.