CtrlK
BlogDocsLog inGet started
Tessl Logo

tanstack-table

TanStack Table UI state patterns for @tanstack/svelte-table, @tanstack/table-core, createTable, ColumnDef, FlexRender, renderComponent, sorting, filtering, pagination, row identity, and local table markup composition. Use when building or reviewing Svelte data tables, not Epicenter workspace storage tables.

72

Quality

89%

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

86%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 a concise, well-organized rule set that assumes Claude's competence and surfaces the right APIs and ownership boundaries. Adding one complete worked table example would lift actionability from strong to fully copy-paste ready.

Suggestions

Add a minimal end-to-end table construction example (createTable + ColumnDef + FlexRender render loop) so the rules have a concrete executable anchor.

Optionally include a short review checklist sequence ('check getRowId → data stability → state pairing → keyboard behavior') to make the reviewing use case a clear workflow.

DimensionReasoningScore

Conciseness

The body is lean declarative rules with no padding — it does not explain what TanStack Table or Svelte is, and every section (construction, controlled state, rendering) earns its tokens.

5 / 5

Actionability

Gives concrete, executable rules ('Always set getRowId', 'satisfies ColumnDef<Row>[]', a copy-paste import block) but lacks a complete worked example of constructing a table end-to-end.

4 / 5

Workflow Clarity

Content is organized into clear topical sections that guide application, but as a declarative ruleset it has no explicit multi-step sequence or review checklist; no validation checkpoints are needed since the skill is non-destructive.

4 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files and is organized into well-signaled sections (Reference Repositories, Upstream Grounding, Table Construction Rules, Controlled State, Rendering), satisfying the simple-skill exception for progressive disclosure.

5 / 5

Total

18

/

20

Passed

Description

92%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, well-triggered, and explicitly disambiguated from sibling skills. Its only weakness is a jargon-leaning trigger surface that could include more natural phrasings.

Suggestions

Add a couple of natural-language synonyms (e.g. 'Svelte data grid', 'sort/filter a table') so the trigger matches how users phrase the request rather than only API names.

Consider including the package name '@tanstack/svelte-table' as an explicit trigger token for users who name the dependency directly.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — createTable, ColumnDef, FlexRender, renderComponent, sorting, filtering, pagination, row identity, and markup composition — giving comprehensive coverage of the skill's technical surface.

5 / 5

Completeness

Clearly states what the skill covers ('TanStack Table UI state patterns for …') and an explicit when ('Use when building or reviewing Svelte data tables'), satisfying both halves with a concrete trigger phrase.

5 / 5

Trigger Term Quality

Includes natural terms users would say ('Svelte data tables', 'sorting', 'filtering', 'pagination') alongside technical API names, but is jargon-heavy and omits some common phrasings or package-name synonyms.

4 / 5

Distinctiveness Conflict Risk

Narrows to a clear niche (@tanstack/svelte-table Svelte data tables) and explicitly disambiguates with 'not Epicenter workspace storage tables', minimizing conflict with adjacent skills.

5 / 5

Total

19

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
EpicenterHQ/epicenter
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.