Name: expanding
Rating: 64 (1 reviews)
Author: TanStack

expanding

Expand hierarchical subrows or custom detail panels with rowExpandingFeature, expandedRowModel, getSubRows, getRowCanExpand, manualExpanding, and paginateExpandedRows. Load when expansion state changes but no UI appears.

Quality

76%

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/expanding/SKILL.md

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.

A tight, well-structured reference skill with executable code and high-value wrong/correct mistake guidance. The only gaps are a slightly abstract detail-render instruction and an API discovery pointer to a raw filesystem path.

Dimension	Reasoning	Score
Conciseness	The body is lean throughout: a one-line framing sentence, direct setup code, tight wrong/correct mistake pairs, and a one-line API discovery pointer, with no padding or explanation of concepts Claude already knows.	5 / 5
Actionability	Setup imports, tableFeatures/options, and wrong/correct code pairs are executable and copy-paste ready, but "render an additional row/panel when isDetailOpen is true" is slightly abstract without a concrete render example.	4 / 5
Workflow Clarity	As a single-purpose configuration skill the action is unambiguous via the Setup section, and the Common Mistakes section acts as guardrails; no validation checkpoints are required since the operations are non-destructive.	4 / 5
Progressive Disclosure	Content is well-organized into Setup, Core Patterns, Common Mistakes, and API Discovery with no nested references and is self-contained, though API Discovery points to a node_modules filesystem path rather than a curated reference file and no bundle files are provided.	4 / 5
	Total	17 / 20 Passed

Description

71%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 specific, distinctive description anchored in concrete TanStack Table APIs with an explicit load trigger. Its main weakness is a narrow, diagnostic "when" clause and jargon-heavy trigger terms that a user may not naturally voice.

Suggestions

Broaden the "Load when..." clause to a general use-when trigger (e.g. "Use when adding row expansion, nested subrows, or custom detail panels to a TanStack Table") in addition to the diagnostic condition.

Soften the API-name list with a few natural synonyms users actually say ("expand rows", "nested/tree rows", "detail panel") to improve trigger-term quality.

Keep the concrete actions but consider framing them as user-facing capabilities rather than a raw enumeration of feature identifiers.

Dimension	Reasoning	Score
Specificity	"Expand hierarchical subrows or custom detail panels" names the domain with concrete actions, reinforced by six specific API symbols (rowExpandingFeature, expandedRowModel, getSubRows, getRowCanExpand, manualExpanding, paginateExpandedRows); coverage is strong but the distinct actions are essentially two (expand subrows, custom detail panels), leaving minor gaps.	4 / 5
Completeness	It states clearly what the skill does and provides an explicit "Load when expansion state changes but no UI appears" trigger, but that trigger is narrow and diagnostic rather than a general use-when clause, so it could be more explicit.	4 / 5
Trigger Term Quality	Natural terms like "expand", "subrows", and "detail panels" appear, but the description is dominated by API identifiers a user would not naturally say, and common synonyms (e.g. "expand rows", "tree rows", "nested rows") are missing.	3 / 5
Distinctiveness Conflict Risk	The combination of TanStack row-expansion API names and the "expansion state changes but no UI appears" trigger carves out a clear niche with minimal overlap risk against other skills.	5 / 5
	Total	16 / 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/expanding/SKILL.md
Commit: 9e523bc

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.