CtrlK
BlogDocsLog inGet started
Tessl Logo

sorting

Sort with rowSortingFeature, sortedRowModel, sortFns, multi-sort and removal options, sortUndefined, and manualSorting. Load for comparator direction, incoming server order, or product-specific sorting cycles.

64

Quality

76%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/table-core/skills/sorting/SKILL.md
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 tight, actionable reference for TanStack table sorting with concrete code and a strong wrong-vs-correct pitfall section. It would benefit from one complete end-to-end column-sorting example to close the minor actionability gap.

Suggestions

Add one complete runnable example showing a column definition with a registered sortFn and enableMultiSort wired into a table, so the setup and core patterns connect end-to-end.

Show how to read runtime sort state (e.g., sorting state accessor) so users can verify the configured cycles are applied.

Optionally move the per-fn import guidance into a short reference list to keep the Setup block focused.

DimensionReasoningScore

Conciseness

Lean and efficient with no padding or explanations of concepts Claude already knows; every section (Setup, Core Patterns, Common Mistakes, API Discovery) earns its place.

5 / 5

Actionability

Provides executable, typed TS code blocks and wrong-vs-correct examples with sources, but lacks a complete runnable end-to-end example wiring a sortFn to a column definition.

4 / 5

Workflow Clarity

A feature/pattern reference rather than a destructive multi-step workflow, so no validate->fix->retry sequence is required; organization is clear and severity-tagged mistakes act as error-avoidance checkpoints, but there is no explicit workflow sequence to validate.

4 / 5

Progressive Disclosure

Compact, well-organized into clear sections with no external reference files needed; the only pointer (node_modules paths) is one level deep and clearly signaled.

5 / 5

Total

18

/

20

Passed

Description

67%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 well-scoped to TanStack table sorting but reads as a feature/API list rather than user-facing trigger language. Adding an explicit 'Use when...' clause with natural synonyms would lift completeness and trigger quality.

Suggestions

Append an explicit 'Use when...' clause naming natural user phrases (e.g., 'Use when sorting table columns, doing multi-column/multi-sort, or handling server-side/manual sorting order').

Add common synonyms users actually say (e.g., 'sort columns', 'multi-column sort', 'server-side sorting') alongside the API identifiers.

Lead with the user-facing action before enumerating API names so the trigger terms surface first.

DimensionReasoningScore

Specificity

Names the domain and many concrete features (rowSortingFeature, sortedRowModel, sortFns, multi-sort, removal, sortUndefined, manualSorting) — comprehensive coverage of the sorting surface.

5 / 5

Completeness

The 'what' is clear, but the 'when' is only weakly implied via 'Load for...' conditions with no explicit 'Use when...' trigger clause, which caps completeness at 3.

3 / 5

Trigger Term Quality

Relevant sorting keywords exist but they are mostly API identifiers rather than natural user phrases; common variations and synonyms are missing.

3 / 5

Distinctiveness Conflict Risk

Scoped to specific TanStack table-core sorting APIs, forming a clear niche with minimal overlap risk against other skills.

5 / 5

Total

16

/

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.