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.

68

Quality

85%

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

82%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, well-organized feature guide with executable code and useful guardrails via Common Mistakes. It is concise and actionable, with only minor gaps in snippet self-containment and explicit workflow sequencing.

Suggestions

Make the Core Patterns snippet self-contained by showing how activeId, overId, and the table/columnOrder variables are obtained, so it is copy-paste ready.

Add a brief explicit sequence (register feature -> set initialState -> apply reorder pattern -> render via getAllLeafColumns/getVisibleLeafColumns) to strengthen workflow clarity.

Consider extracting the API Discovery detail into a short referenced section so the overview stays a clear pointer rather than an inline inspection hint.

DimensionReasoningScore

Conciseness

Lean and efficient; assumes Claude's competence with React/TanStack and avoids explaining basic concepts, with every line serving as guidance or executable code.

5 / 5

Actionability

Provides concrete, executable TypeScript (setup imports, filter/splice/setColumnOrder, wrong/correct pairs) but some snippets depend on undefined context (activeId, overId, table) rather than being fully self-contained copy-paste.

4 / 5

Workflow Clarity

Well-organized into Setup, Core Patterns, Common Mistakes, and API Discovery with a clear setup-to-use flow, but lacks explicit sequencing or checkpoints characteristic of a 5.

4 / 5

Progressive Disclosure

Well-structured with clear section headers and no content wrongly inlined, but at ~55 lines with only a node_modules discovery hint rather than bundled one-level-deep reference files, it stops short of the clear-reference-navigation bar for a 5.

4 / 5

Total

17

/

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 is specific and distinct, clearly stating both the capability and the load-time trigger conditions. It uses concise third-person/imperative voice without over-claiming.

DimensionReasoningScore

Specificity

Names several specific capabilities ("Control... leaf columnOrder with stable IDs", "accounting for pinning regions, visibility, and groupedColumnMode precedence") but centers on one verb with sub-concerns rather than multiple distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

Explicitly answers what (control leaf columnOrder accounting for pinning/visibility/groupedColumnMode) and when ("Load for drag-and-drop columns or rendered order that differs from state"), with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural trigger phrases ("Load for drag-and-drop columns or rendered order that differs from state") but leans on library jargon (columnOrder, groupedColumnMode) and omits some common synonyms.

4 / 5

Distinctiveness Conflict Risk

A clear niche (TanStack Table v9 leaf columnOrder with specific plugin interactions) with distinct triggers and minimal risk of firing for the wrong skill.

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.