CtrlK
BlogDocsLog inGet started
Tessl Logo

tanstack-table

Apply TanStack Table UI-state patterns for Svelte data tables, including columns, rendering, sorting, filtering, pagination, and row identity. Use when building or reviewing data-table UI, not Epicenter workspace storage tables.

72

Quality

91%

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

85%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 tight, well-structured rules skill: lean imperative guidance organized in a natural construction-to-rendering order, with concrete API-level directives. The main gaps are the absence of a complete code example and a couple of trimmable meta sections.

Suggestions

Add one short, complete createSvelteTable example showing options, state, and FlexRender together to close the actionability gap.

Trim the 'Reference Repositories' section and the boundary sentence that duplicates the description's disambiguation to save tokens.

Clarify which row models to import (e.g., getSortedRowModel, getFilteredRowModel, getPaginationRowModel) so the 'include only row models the UI uses' rule is directly executable.

DimensionReasoningScore

Conciseness

The body is lean and imperative with no explanations of concepts Claude already knows ('Always set getRowId...', 'Key rows by row.id'), but the 'Reference Repositories' link list and the boundary sentence that repeats the description's disambiguation are minor instances that could be trimmed — anchor 4, not 5.

4 / 5

Actionability

Rules are concrete and checkable (e.g., 'Define columns with satisfies ColumnDef<Row>[]', 'If an onXChange handler is present, the matching state.get x() must also be present') plus a real import baseline, but there is no complete table-construction example — mostly executable with minor gaps, anchor 4.

4 / 5

Workflow Clarity

This is a simple single-purpose skill under 50 lines; sections follow the natural build order (Table Construction Rules, Controlled State, Rendering) and each directive is unambiguous, so the simple-skill exception applies; no destructive or batch operations require validation checkpoints.

5 / 5

Progressive Disclosure

Under 50 lines with no need for external references and no bundle files present; the well-organized section headers satisfy the simple-skill guideline for a top score.

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.

A strong description: concrete capability enumeration, an explicit use-when trigger, and an explicit negative boundary against a sibling skill. The only weakness is slightly incomplete synonym coverage for trigger terms.

Suggestions

Add common user synonyms such as 'grid' or 'data grid' to the trigger phrasing to broaden natural-language matching.

DimensionReasoningScore

Specificity

Enumerates six concrete capability areas — 'columns, rendering, sorting, filtering, pagination, and row identity' — giving comprehensive coverage of the domain, matching the anchor for multiple specific concrete actions; it is not score 4 because coverage within its stated scope is complete rather than having minor gaps.

5 / 5

Completeness

Explicitly answers what ('Apply TanStack Table UI-state patterns for Svelte data tables, including...') and when ('Use when building or reviewing data-table UI') with concrete trigger phrases, matching the top anchor exactly.

5 / 5

Trigger Term Quality

Natural phrases users would say include 'data tables', 'data-table UI', 'sorting', 'filtering', 'pagination', 'Svelte', and 'TanStack Table', which is good keyword coverage; it falls short of 5 because common synonyms such as 'grid' or 'datagrid' are absent.

4 / 5

Distinctiveness Conflict Risk

The clause 'not Epicenter workspace storage tables' explicitly disambiguates from the closest competing skill, and the Svelte/TanStack niche is distinct, giving minimal conflict risk; no neighboring anchor fits better.

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.

Validation — 16 / 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.