CtrlK
BlogDocsLog inGet started
Tessl Logo

create-table-hook

Define a Svelte createAppTable/createAppColumnHelper using the adapter's rune-capable createTableHook implementation, shared features/defaults, reactive per-table getters, optional App component registries, and typed table/cell/header context hooks.

61

Quality

73%

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/create-table-hook/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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 lean and highly actionable with concrete code and Wrong/Correct pairs, well-structured into clear sections. Its main gap is the absence of explicit validation/feedback checkpoints, which keeps workflow clarity in the mid range for this pattern-reference skill.

Suggestions

Add a brief validation step where a table is actually built — e.g. 'Confirm the table re-renders when $state data mutates' — to give the workflow an explicit checkpoint.

Consider splitting the Common Mistakes detail or the component-registry contract into a referenced file (e.g. COMPONENTS.md) with a one-level-deep link, which would let progressive disclosure reach a 5.

Tighten the prose after each Correct block to a single rationale line, removing the multi-clause explanations that slightly pad the conciseness.

DimensionReasoningScore

Conciseness

The body is efficient: it uses tight Wrong/Correct code pairs and avoids tutorials on what tables or Svelte are, with only a few explanatory sentences (e.g. 'The shipped implementation supplies Svelte rune reactivity...') that could be trimmed slightly.

4 / 5

Actionability

It provides copy-paste-ready imports, createTableHook usage, a Svelte component example, context-hook usage, and concrete discovery paths, with Wrong/Correct pairs covering the common cases.

5 / 5

Workflow Clarity

The Setup → Core Patterns → Common Mistakes → API Discovery layout gives a logical reading order, but this is a patterns/mistakes reference rather than a sequenced operation, and it lacks explicit validation checkpoints (no destructive/batch ops, so the cap does not force lower).

3 / 5

Progressive Disclosure

Sections are well-organized and the content is appropriately sized for a single overview file with no bundle files present; it stops short of a 5 only because there are no signaled one-level-deep references to split out, which the skill does not strictly need.

4 / 5

Total

16

/

20

Passed

Description

70%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 clearly scoped to a distinct Svelte composable-tables niche, but it lacks an explicit 'Use when...' trigger clause, capping its completeness. Adding when-to-use guidance would meaningfully raise the score.

Suggestions

Append an explicit 'Use when...' clause, e.g. 'Use when multiple Svelte tables share conventions, columns, features, or component registries; keep one-off tables on createTable.'

Lead with the core action (e.g. 'Define shared Svelte table conventions via createAppTable/createAppColumnHelper') before listing the supporting capabilities, to read as a concrete multi-action description.

Add a natural user-facing trigger phrase (e.g. 'shared table setup' or 'app-wide table conventions') alongside the API names to broaden keyword coverage.

DimensionReasoningScore

Specificity

The description enumerates several concrete capabilities ('rune-capable createTableHook implementation, shared features/defaults, reactive per-table getters, optional App component registries, and typed table/cell/header context hooks'), but they are packed into a single 'Define X using...' clause rather than a crisp multi-action list, so it sits just below a 5.

4 / 5

Completeness

It clearly states the 'what' (defining an app table/column helper via the adapter hook) but includes no 'Use when...' trigger clause, which the rubric caps at 3 for missing explicit trigger guidance.

3 / 5

Trigger Term Quality

It surfaces API-level keywords a developer would naturally name ('Svelte', 'createAppTable', 'createAppColumnHelper', 'createTableHook', 'context hooks') with good coverage, though a few natural phrasings/synonyms a user might say are absent.

4 / 5

Distinctiveness Conflict Risk

The niche is highly specific — Svelte composable tables built on createTableHook — with distinct, framework/library-scoped triggers and minimal overlap risk with other skills.

5 / 5

Total

16

/

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.