Name: sorting
Rating: 55.2 (1 reviews)
Author: TanStack

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.

Quality

63%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/table-core/skills/sorting/SKILL.md

Quality

Content

68%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 content is concise, actionable, and well-structured, with concrete executable code and high-value wrong/correct mistake patterns grounded in source paths. As a reference/configuration skill it lacks a sequenced workflow with validation checkpoints, which limits workflow clarity.

Suggestions

Add a brief ordered workflow (register features → configure options → verify sort behavior) with a validation checkpoint such as inspecting the sorted row model at runtime.

Consolidate the opening framing line into the section structure to tighten conciseness further.

Provide one end-to-end runnable example integrating feature registration, column config, and manual/server sorting to close the actionability gap.

Dimension	Reasoning	Score
Conciseness	The body is lean with executable code and value-dense 'Common Mistakes' entries that capture non-obvious behavior; only the opening framing line and a couple of setup notes could be trimmed, matching the 'efficient; minor over-explanation' anchor rather than the fully lean anchor 5.	4 / 5
Actionability	Setup, Core Patterns, and Common Mistakes all provide concrete, copy-paste-ready TS code with explicit wrong/correct pairs and source pointers, covering the common cases with only minor gaps (no single end-to-end runnable example).	4 / 5
Workflow Clarity	Content is section-ordered (Setup → Core Patterns → Mistakes → API Discovery) but is a reference/configuration skill with no multi-step sequenced workflow or validation checkpoints; this matches the 'sequence present but checkpoints missing or implicit' anchor.	3 / 5
Progressive Disclosure	The body is well-organized into clearly headed sections and is appropriately self-contained for a ~50-line skill with no bundle files, but it does not demonstrate the explicit one-level-deep reference signaling of the top anchor.	4 / 5
	Total	15 / 20 Passed

Description

58%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 clearly scoped to TanStack table-core sorting, naming concrete features and load scenarios. Its main weakness is the absence of an explicit 'Use when...' trigger clause and heavy reliance on API identifiers over natural user phrasing.

Suggestions

Add an explicit 'Use when...' clause naming natural triggers, e.g. 'Use when sorting TanStack table rows by column, multi-sorting, or configuring server-side sort order.'

Reduce reliance on raw API identifiers in favor of natural terms users actually say ('sort rows', 'sort by column', 'multi-column sort').

Clarify when to load this skill versus sibling sub-skills like filtering or grouping to further reduce overlap risk.

Dimension	Reasoning	Score
Specificity	Lists several concrete capabilities (rowSortingFeature, sortedRowModel, sortFns, multi-sort and removal, sortUndefined, manualSorting) plus concrete load scenarios, so it sits at 'several specific actions; minor gaps' rather than the fully comprehensive anchor 5.	4 / 5
Completeness	It states clearly what the skill does ('Sort with...'), but there is no 'Use when...' clause or equivalent explicit trigger guidance, and the 'Load for...' clause only weakly implies when — per the guidelines this caps completeness at 3.	3 / 5
Trigger Term Quality	'Sort' and 'multi-sort' are natural user terms, but the description is dominated by API identifiers (rowSortingFeature, sortedRowModel, sortUndefined) and misses common natural phrasings like 'sort the table by column', matching the 'some relevant keywords but missing variations' anchor.	3 / 5
Distinctiveness Conflict Risk	It carves a clear table-core sorting niche with distinct triggers and minimal conflict risk, but 'sort' could overlap with sibling table-core sub-skills (filtering, grouping), placing it just below the minimal-conflict anchor 5.	4 / 5
	Total	14 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: packages/table-core/skills/sorting/SKILL.md
Commit: d01c01b

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.