CtrlK
BlogDocsLog inGet started
Tessl Logo

column-filtering

Filter columns with columnFilteringFeature, filteredRowModel, filterFns, filterMeta, nested-row direction, and manualFiltering. Load for accessor compatibility, controlled filter updaters, fuzzy metadata, or client/server ownership.

68

Quality

83%

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 content is a tight, code-heavy reference that assumes Claude's competence and delivers executable setup plus concrete wrong/correct patterns for the highest-impact mistakes. Organization is clear; the only soft spot is the lack of an explicit verification loop, which is not strictly required for non-destructive filtering.

DimensionReasoningScore

Conciseness

The body is lean and code-forward with no padding about what TanStack Table or filtering is; every line provides setup, conditional guidance, or a concrete wrong/correct pair that earns its place.

5 / 5

Actionability

Provides copy-paste-ready setup code, concrete options objects, and three wrong/correct code pairs for common mistakes, all executable and covering the common cases.

5 / 5

Workflow Clarity

Sections (Setup, Core Patterns, Common Mistakes, API Discovery) give a clear loose sequence with the API Discovery step acting as a signature-verification checkpoint, though there is no explicit validate-fix-retry loop (not required since filtering is non-destructive).

4 / 5

Progressive Disclosure

No bundle files exist and the ~70-line body is appropriately kept inline with well-organized section headers and clear navigation; minor gap is that no overview-to-detail split is used, but the size does not demand one.

4 / 5

Total

18

/

20

Passed

Description

76%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 and distinctive, naming the concrete API surface and providing trigger guidance for when to load the skill. Its main weakness is trigger-term naturalness: keywords lean toward API jargon rather than phrases a user would naturally say.

Suggestions

Add an explicit 'Use when...' clause with natural user phrases (e.g., 'Use when the user wants to filter table columns, switch between client-side and server-side filtering, or set up custom filter functions').

Soften API-identifier trigger terms by pairing them with natural synonyms (e.g., 'filterFns (custom filter functions)', 'client/server filtering ownership').

DimensionReasoningScore

Specificity

Names six concrete API entities (columnFilteringFeature, filteredRowModel, filterFns, filterMeta, nested-row direction, manualFiltering), giving comprehensive coverage of the column-filtering surface with no vague language.

5 / 5

Completeness

Clearly states what ('Filter columns with...') and provides equivalent trigger guidance ('Load for accessor compatibility, controlled filter updaters, fuzzy metadata, or client/server ownership'), though the 'when' is technical rather than user-mention oriented and could be more explicit.

4 / 5

Trigger Term Quality

Relevant domain keywords appear (Filter columns, filterFns, manualFiltering, client/server), but they are presented as API identifiers rather than natural user phrases, and common variations like 'client-side vs server-side filtering' or 'column filters' are missing.

3 / 5

Distinctiveness Conflict Risk

Targets a clear, narrow niche (TanStack table-core column filtering) with distinct, feature-specific triggers, making conflict with other skills unlikely.

5 / 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.