CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

65

Quality

80%

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

Quality

Content

76%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 compact, well-structured sub-skill that is token-efficient and gives concrete executable guidance with helpful Wrong/Correct mistake callouts. It is a reference guide rather than a workflow, so it lacks explicit sequencing and validation checkpoints.

Suggestions

Add a short end-to-end runnable example that wires features and options into a createTable call so the Setup fragment becomes copy-paste complete (raises actionability).

For the pagination-placement mistake, include a one-line verification step (e.g., how to confirm descendantsStayWithParent behavior) to add an explicit checkpoint for the most error-prone option (raises workflow_clarity).

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: short orienting sentences, tight code blocks, and Wrong/Correct snippets with one-line rationales, every token earning its place with no padding or restatement of known concepts.

5 / 5

Actionability

Provides concrete, executable snippets (tableFeatures setup, getSubRows, getRowCanExpand, getIsExpanded) and Wrong/Correct fixes, but the examples are fragments rather than a complete copy-paste-runnable end-to-end table, leaving minor gaps.

4 / 5

Workflow Clarity

Sections follow a logical order (Setup, Core Patterns, Common Mistakes, API Discovery) but this is reference material rather than a sequenced workflow, and there are no explicit validation checkpoints; it is above a 2 because the Common Mistakes Wrong/Correct pairs act as implicit correctness checks.

3 / 5

Progressive Disclosure

Well-organized into clearly signaled sections with no nested references and a one-level-deep API Discovery pointer to node_modules source, but all content is inline with no bundle files, so it falls short of the ideal split-content anchor at 5.

4 / 5

Total

16

/

20

Passed

Description

83%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, third-person, and supplies an explicit use-when trigger tied to a concrete debugging scenario, giving it strong completeness and distinctiveness. Its main limitation is API-jargon weighting in the action list and a few missing natural synonyms.

DimensionReasoningScore

Specificity

Names the domain and several concrete actions ('Expand hierarchical subrows or custom detail panels') with specific feature APIs (rowExpandingFeature, getSubRows, paginateExpandedRows), but the actions are API-name heavy rather than a comprehensive set of user-facing capabilities, so it sits below a 5.

4 / 5

Completeness

Explicitly answers both 'what' (expand subrows/detail panels with the listed features) and 'when' (the concrete 'Load when expansion state changes but no UI appears' trigger clause), matching the anchor that requires concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes a natural trigger clause ('Load when expansion state changes but no UI appears') plus relevant terms (expand, subrows, detail panels), giving good keyword coverage, though common synonyms like 'expand/collapse' or 'tree rows' are missing — not a 5.

4 / 5

Distinctiveness Conflict Risk

A clear, version-pinned niche (TanStack table-core 9.2.4 row expanding) with distinct triggers and minimal conflict risk, but it overlaps slightly with sibling table-core sub-skills, so it is not a clean 5.

4 / 5

Total

17

/

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.