CtrlK
BlogDocsLog inGet started
Tessl Logo

core

Use TanStack Table v9 as a headless data-grid state and row-processing engine. Load for first-table architecture, stable data and columns, row numbering with getDisplayIndex, semantic rendering, framework adapter choice, or deciding what Table owns versus the renderer.

71

Quality

88%

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

90%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 tight, highly actionable reference with executable code and well-chosen Wrong/Correct mistake patterns that convey non-obvious V9 specifics. Structure is clear; the only slight weakness is the absence of explicit validation checkpoints, which is acceptable given no destructive operations are involved.

DimensionReasoningScore

Conciseness

Lean and efficient throughout: every section pairs executable code with a single domain-specific line of explanation, assuming Claude's competence without padding or restating basics.

5 / 5

Actionability

Fully executable, copy-paste-ready TypeScript in Setup, Core Patterns, and the Wrong/Correct Common Mistakes, plus a concrete node_modules path for API discovery covering the common cases.

5 / 5

Workflow Clarity

A clear Setup → Core Patterns → Common Mistakes → API Discovery progression, but as a patterns/reference skill it lacks explicit validation checkpoints or feedback loops (none are required since there are no destructive or batch operations).

4 / 5

Progressive Disclosure

Well-organized with clear section headers and a self-contained single-file structure (no bundle files present, no nested references); minor gap is that Common Mistakes/Core Patterns could optionally split into reference files at this length.

4 / 5

Total

18

/

20

Passed

Description

87%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 cleanly answers both what the skill does and when to load it, with a distinct, low-conflict niche around TanStack Table v9 core. It is strong overall, with only minor room to add more natural user-side phrasings alongside the technical terms.

DimensionReasoningScore

Specificity

Lists the core action ("Use TanStack Table v9 as a headless data-grid state and row-processing engine") plus several concrete scenarios, but the scenarios read more as trigger contexts than distinct performed actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly states both what ("Use TanStack Table v9 as a headless data-grid state and row-processing engine") and when ("Load for first-table architecture, stable data and columns, row numbering with getDisplayIndex...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Good coverage of relevant keywords ("TanStack Table v9", "data-grid", "row numbering", "getDisplayIndex", "framework adapter"), though several lean technical/jargon and a few natural user phrasings are missing.

4 / 5

Distinctiveness Conflict Risk

A clearly defined TanStack Table v9 core niche with distinct triggers (getDisplayIndex, framework adapter choice, what Table owns versus the renderer) and minimal overlap risk with other skills.

5 / 5

Total

18

/

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.