CtrlK
BlogDocsLog inGet started
Tessl Logo

table-state

Use Svelte 5 rune-aware table atoms and stores, $derived projections, reactive option getters, controlled $state or createTableState slices, external atoms, and auto-reset behavior without broad invalidation or snapshot mismatches.

60

Quality

71%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/svelte-table/skills/table-state/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

83%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 content is a tight, code-first reference that assumes Claude's competence and supplies executable, wrong/correct-pattern guidance for the real failure modes. Its only real weaknesses are minor: an occasional small over-explanation and the absence of explicit validation feedback loops (which are not strictly required for this read-mostly coordination skill).

DimensionReasoningScore

Conciseness

The body is lean and assumes competence — it never explains what Svelte runes or TanStack Table are — with almost every token earning its place; the one mild tangent ('For better or worse, this resembles a small React useState hook') is informative but is the kind of over-explanation that keeps it just short of a 5.

4 / 5

Actionability

Code blocks are complete, typed, and copy-paste ready, and the wrong/correct pairs in Common Mistakes concretely cover the common cases (removed selectors, missing write-back, snapshotting outside tracking, dual owners, auto-reset), fully executable.

5 / 5

Workflow Clarity

The body follows a clear sequence (mental model → setup → core patterns → ownership → init/update/reset → mistakes → API discovery) and the destructive/batch validation cap does not apply to read-mostly table-state coordination, but there are no explicit validate→fix→retry checkpoints, keeping it just below a 5.

4 / 5

Progressive Disclosure

No bundle files exist, so the skill is self-contained with well-organized section headers and clearly signaled external pointers (node_modules .d.ts files, migration/pagination doc paths); it sits just short of a 5 because some sections (e.g. the full Common Mistakes catalog) could conceptually live in a reference file, though keeping them inline is defensible for a focused skill.

4 / 5

Total

17

/

20

Passed

Description

58%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 well-scoped to Svelte 5 table state mechanics, but it is missing an explicit 'Use when...' trigger clause and leans on technical jargon over natural user phrasing. Completeness is capped at 3 by the missing when-guidance.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when managing table state with @tanstack/svelte-table in Svelte 5, controlling pagination/sorting/visibility slices, or migrating off removed adapter selectors.'

Soften the jargon slightly by including everyday synonyms users would say ('Svelte table state', 'controlled svelte-table slices') alongside 'runes', 'atoms', and '$derived'.

Consider whether the trailing constraint ('without broad invalidation or snapshot mismatches') is better placed in the body; replacing it with one more concrete action would lift specificity.

DimensionReasoningScore

Specificity

Names several concrete mechanisms — 'rune-aware table atoms and stores', '$derived projections', 'reactive option getters', 'controlled $state or createTableState slices', 'external atoms', 'auto-reset behavior' — but the trailing 'without broad invalidation or snapshot mismatches' is a constraint rather than a named action, leaving minor coverage gaps short of a 5.

4 / 5

Completeness

It gives a clear 'what' (the state mechanisms the skill uses) but provides no 'Use when...' or equivalent explicit trigger clause, which per the guidelines caps completeness at 3.

3 / 5

Trigger Term Quality

Terms like 'Svelte 5 runes', 'table atoms', '$derived', 'createTableState' are relevant but lean technical; it omits the natural phrases a user would say ('svelte table state', 'tanstack svelte table', 'controlled table state') and their common variations.

3 / 5

Distinctiveness Conflict Risk

The trigger is tightly scoped to Svelte 5 / @tanstack/svelte-table state management, making it mostly distinct from other skills with only minor overlap risk against a sibling svelte-table skill.

4 / 5

Total

14

/

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

metadata_version

'metadata.version' is missing

Warning

frontmatter_unknown_keys

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

Warning

Total

14

/

16

Passed

Repository
TanStack/table
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.