CtrlK
BlogDocsLog inGet started
Tessl Logo

grouping

Group rows with columnGroupingFeature, groupedRowModel, groupedColumnMode, and manualGrouping. Load for grouped or placeholder cells and grouping interactions with expansion or pagination.

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/grouping/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 tight, code-centric skill body with strong token efficiency and concrete wrong/correct patterns. Its main weakness is the absence of an explicit checkpointed workflow, which suits its reference nature but leaves workflow_clarity mid-range.

Suggestions

Add a short numbered 'How to apply grouping' workflow (configure features -> detect cell mode -> render -> verify) with a validation checkpoint to raise workflow_clarity above 3.

Make the countLeafRows example fully runnable by defining groupRow (e.g. table.getRowModel().rows[0]) so the snippet is copy-paste ready.

Consider moving the longer Common Mistakes wrong/correct pairs into a references/ file and linking from the body to improve progressive_disclosure now that the body approaches 80 lines.

DimensionReasoningScore

Conciseness

Lean, code-first body that assumes Claude's competence — minimal prose, no library primer, every line (Setup, Core Patterns, Common Mistakes, API Discovery) earns its place.

5 / 5

Actionability

Provides executable setup imports, cell-mode detection, and wrong/correct pairs; the recursive countLeafRows example references a groupRow that is not fully wired into a runnable context, a minor gap keeping it below 5.

4 / 5

Workflow Clarity

Sections imply a loose flow (Setup -> Core Patterns -> Common Mistakes -> API Discovery) but there is no sequenced multi-step workflow with validation checkpoints; this is a patterns/mistakes reference rather than a checkpointed process.

3 / 5

Progressive Disclosure

Well-organized sections with clearly signaled one-level-deep references (Load the separate 'aggregation' skill, source paths); no bundle files exist to split, and structure is good but the body is somewhat long for a skill with no external file references, so below 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.

A focused, third-person description that states concrete capabilities and gives explicit load-trigger guidance with concrete cell-mode and interaction triggers. It is specific and well-scoped to TanStack table grouping with minimal conflict risk.

DimensionReasoningScore

Specificity

Names the concrete action 'Group rows' plus specific config tokens (columnGroupingFeature, groupedRowModel, groupedColumnMode, manualGrouping) and concrete cell modes (grouped/placeholder); not quite comprehensive coverage of all grouping actions, so below 5.

4 / 5

Completeness

Explicitly answers what ('Group rows with columnGroupingFeature, groupedRowModel...') and when via the equivalent trigger clause 'Load for grouped or placeholder cells and grouping interactions with expansion or pagination', with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural terms a TanStack user would say ('group rows', 'grouping', 'expansion', 'pagination', 'placeholder cells') with good coverage, but lacks synonyms or file-extension-style variants that would push it to 5.

4 / 5

Distinctiveness Conflict Risk

Clear niche (TanStack table row grouping) with distinct triggers and an explicit hand-off to the separate aggregation skill; minor overlap risk with aggregation/grouping-adjacent skills keeps it just below 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.