CtrlK
BlogDocsLog inGet started
Tessl Logo

column-faceting

Build faceted filter UIs with columnFacetingFeature, facetedRowModel, facetedUniqueValues, and facetedMinMaxValues. Load for facet counts, numeric ranges, own-filter exclusion, or server-page facet completeness.

66

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

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, actionable skill content: executable setup, concrete patterns, and wrong/correct mistake entries with no filler. The only mild gaps are the absence of explicit validation checkpoints (not strictly needed here) and slight room to externalize the API discovery detail.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence: it opens with a one-line boundary statement, then jumps straight into executable setup code and concrete patterns with no padding or explanation of concepts Claude already knows.

5 / 5

Actionability

It provides copy-paste-ready, fully executable setup code, concrete getter calls in Core Patterns, and wrong/correct pairs for each common mistake, covering the real cases a practitioner hits.

5 / 5

Workflow Clarity

The content is clearly sequenced (Setup -> Core Patterns -> Common Mistakes -> API Discovery) and unambiguous for a single-purpose skill, but there are no explicit validation checkpoints; none are strictly required since the skill is not destructive or batch-oriented.

4 / 5

Progressive Disclosure

The body is well-organized into clearly labeled sections with no nested references and no bundled files to navigate; it is slightly above the under-50-lines simple-skill threshold and the API Discovery pointer to node_modules could conceptually be a reference file, so it stops just short of ideal.

4 / 5

Total

18

/

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.

The description is specific and well-targeted to a distinct niche, with a clear what and an explicit load-trigger when clause. It is slightly held back by technical-leaning trigger phrasing that misses more natural user terms.

Suggestions

Reframe the load condition as an explicit 'Use when ...' clause using more natural user phrasing (e.g., 'Use when adding faceted filters, facet count badges, or numeric range filters to a TanStack table').

Add common synonyms or conversational trigger terms (e.g., 'facets', 'filter value counts', 'range sliders') alongside the API names to broaden natural keyword coverage.

DimensionReasoningScore

Specificity

Names the concrete action ('Build faceted filter UIs') and enumerates the specific APIs (columnFacetingFeature, facetedRowModel, facetedUniqueValues, facetedMinMaxValues), but the supporting clauses describe load conditions rather than additional distinct actions, leaving minor coverage gaps.

4 / 5

Completeness

It states what the skill does ('Build faceted filter UIs with ...') and gives an explicit load trigger ('Load for facet counts, numeric ranges, own-filter exclusion, or server-page facet completeness'), answering both what and when, though the when could be framed more explicitly as a 'Use when' clause.

4 / 5

Trigger Term Quality

Relevant terms like 'faceted filter UIs', 'facet counts', and 'numeric ranges' appear, but the phrasing leans technical and omits common synonyms or natural variations a user might say, so coverage is partial.

3 / 5

Distinctiveness Conflict Risk

It targets a narrow TanStack table faceting niche with API-specific triggers, making it clearly distinguishable from other skills with minimal conflict risk.

5 / 5

Total

16

/

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.