CtrlK
BlogDocsLog inGet started
Tessl Logo

column-ordering

Control TanStack Table v9 leaf columnOrder with stable IDs while accounting for pinning regions, visibility, and groupedColumnMode precedence. Load for drag-and-drop columns or rendered order that differs from state.

70

Quality

86%

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.

A tight, well-organized reference skill with executable code, concrete wrong/correct mistake pairs, and source citations. The main weakness is the Core Patterns snippet's undefined variables and the absence of any validation checkpoint for the reorder operation.

Suggestions

Define or contextualize `activeId`/`overId` in the Core Patterns snippet so the reorder code is fully self-contained and copy-paste ready.

Add a brief validation note for the reorder operation (e.g., verify the resulting columnOrder array contains all expected leaf IDs after setColumnOrder) to strengthen workflow clarity.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what TanStack Table or column ordering is conceptually, and every line (setup, pattern, wrong/correct pairs, source pointers) earns its place.

5 / 5

Actionability

Setup and Common Mistakes give copy-paste-ready TypeScript, and API Discovery points to a concrete path, but the Core Patterns snippet references undefined `activeId`/`overId`, a minor execution gap.

4 / 5

Workflow Clarity

The content is logically organized (Setup → Core Patterns → Common Mistakes → API Discovery) and the reorder operation is sequenced (filter → splice → setColumnOrder), but it is presented as a reference of patterns rather than a validated workflow, with no explicit checkpoints.

4 / 5

Progressive Disclosure

The body is under 50 lines with no bundle files present and no need for external references, yet is cleanly divided into well-signaled sections, meeting the simple-skill exception for full marks.

5 / 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.

A precise, well-targeted description that clearly states what the skill does and when to load it, with concrete trigger phrases and minimal conflict risk. The only gap is modest keyword synonym coverage in the trigger terms.

DimensionReasoningScore

Specificity

Names the domain ('TanStack Table v9 leaf columnOrder') and several concrete concerns (stable IDs, pinning regions, visibility, groupedColumnMode precedence), but it is a single feature area rather than multiple distinct actions, so it falls just short of comprehensive coverage.

4 / 5

Completeness

The 'what' is detailed ('Control... columnOrder with stable IDs while accounting for pinning regions, visibility, and groupedColumnMode precedence') and the 'when' is explicit and concrete ('Load for drag-and-drop columns or rendered order that differs from state'), satisfying both halves with concrete trigger phrases.

5 / 5

Trigger Term Quality

'drag-and-drop columns' and 'rendered order that differs from state' are natural trigger phrases a user might say, but common synonyms like 'reorder columns', 'move columns', or 'column order' are missing.

4 / 5

Distinctiveness Conflict Risk

It targets a narrow, well-defined niche (TanStack Table v9 leaf column ordering) with distinct triggers, making conflict with unrelated skills very unlikely.

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.