CtrlK
BlogDocsLog inGet started
Tessl Logo

aggregation

Aggregate TanStack Table columns independently of grouping, including grand totals, caller-selected row totals, multiple keyed aggregations, custom context-based definitions, grouped merges, manual values, and worker constraints.

62

Quality

74%

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

Quality

Content

90%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 an exemplar of lean, executable, library-specific guidance that assumes competence and avoids restating basics; its only soft spots are the absence of an explicit verification checkpoint for aggregation results and a slightly informal API-discovery pointer.

DimensionReasoningScore

Conciseness

The body is lean and dense with API specifics (caching behavior, maxDepth semantics, structured-clone constraints); it assumes Claude's competence and every line earns its place with no padding or restated basics.

5 / 5

Actionability

Code blocks are copy-paste ready and cover the common cases (setup, grand/selected totals, multiple aggregations, custom definitions, manual values), with specific typed signatures and concrete option objects rather than pseudocode.

5 / 5

Workflow Clarity

Patterns are clearly organized into setup, core patterns, and common mistakes with explicit wrong/correct contrasts; this is not a destructive batch workflow, so it does not require validate-fix-retry loops, though an explicit verification/check step for aggregation output would push it to 5.

4 / 5

Progressive Disclosure

Well-organized sections with an inline API Discovery pointer to node_modules paths and guide docs; no bundle files exist, and the body is short enough that inlining is appropriate, but the discovery pointer is prose rather than a clearly signaled reference link.

4 / 5

Total

18

/

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 highly specific about capabilities and well-differentiated, but it omits any explicit 'when to use this' trigger guidance and lacks natural user-facing phrasing, capping completeness and trigger-term quality.

Suggestions

Add a 'Use when...' clause with concrete natural-language triggers, e.g. 'Use when totaling table columns, computing grand totals, or combining aggregation with grouping in TanStack Table'.

Include more user-facing synonyms such as 'totals', 'summary values', and 'rollups' alongside the technical term 'aggregation'.

Lead with the primary use case (computing column totals) before the long list of feature variations.

DimensionReasoningScore

Specificity

Lists several specific actions (grand totals, caller-selected row totals, multiple keyed aggregations, custom context-based definitions, grouped merges, manual values, worker constraints); minor gaps in coverage such as aggregation function registration keep it just below a 5.

4 / 5

Completeness

The 'what' is clearly and comprehensively stated, but there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Domain keywords like 'aggregation', 'grand totals', and 'row totals' are present, but natural user-facing synonyms and phrasings a user would actually say are thin and the wording leans technical.

3 / 5

Distinctiveness Conflict Risk

It carves a clear niche (aggregation independent of grouping) and names TanStack Table specifically, leaving only minor overlap risk with a sibling grouping skill.

4 / 5

Total

14

/

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.