global-filtering

Apply globalFilter across eligible columns with globalFilteringFeature, columnFilteringFeature, filteredRowModel, globalFilterFn, and manual server filtering. Load when columns unexpectedly participate or a global filter changes state without changing rows.

Quality

79%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./packages/table-core/skills/global-filtering/SKILL.md

Quality

Content

80%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 conciseness and actionability — lean, executable, every mistake given a concrete fix and source. Its weakness is workflow clarity: the manual server-filtering path and feature-wiring flow lack explicit validation checkpoints or a verify/retry loop.

Suggestions

Add a verification checkpoint for manual/server-side filtering, e.g. after fetching rows confirm the displayed rows match the search term and re-query when the filter value changes.

For the setup flow, add a one-line validation step (e.g. assert the table exposes a getFilteredRowModel() populated by the global filter) so the sequence has an explicit checkpoint.

If deeper API detail exists, surface it as a one-line reference (e.g. 'See references/global-filtering-api.md for filter-fn signatures') to lift progressive disclosure toward the overview-with-references structure.

Dimension	Reasoning	Score
Conciseness	The body is lean: a setup snippet, a core-options snippet, and three compact Wrong/Correct mistake entries each with a one-line rationale and a source pointer — every token earns its place and it never explains concepts Claude already knows. Matches the lean-and-efficient anchor; no padding to trim, so not below 5.	5 / 5
Actionability	Setup and core-pattern blocks are complete, importable TypeScript, and each mistake pairs a concrete wrong snippet with a copy-paste-ready correct snippet (e.g. "tableFeatures({ columnFilteringFeature, globalFilteringFeature, filteredRowModel: createFilteredRowModel() })"), covering the common cases. Fully executable and instruction-ready, matching the top anchor.	5 / 5
Workflow Clarity	Content is organized as Setup → Core Patterns → Common Mistakes → API Discovery, a recognizable sequence, but there are no validation/checkpoint steps and the manual-server-filtering case is a single Correct line with no explicit feedback loop (verify rows match the search, re-query on param change). The mistake format gives before/after but not a sequenced procedure with checkpoints, fitting the 'steps listed but validation gaps' anchor and capped there.	3 / 5
Progressive Disclosure	Well-organized into focused sections with most content appropriately inline for a compact skill, and an 'API Discovery' pointer to on-disk feature directories for deeper inspection — a one-level-deep reference. No references/scripts/assets bundle exists, so it is not the multi-file overview structure of a 5, but it is clearly above the unstructured/inline-buried level of 3.	4 / 5
	Total	17 / 20 Passed

Description

78%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 concrete and third-person, with an explicit 'Load when...' trigger and tightly scoped fault conditions that make it highly distinct. Its main limitation is trigger breadth — a single narrow debug condition rather than the fuller range of natural phrases a user might say.

Suggestions

Broaden the 'when' clause to include positive triggers users actually say, e.g. 'Use when implementing search-across-all-columns, enabling server-side global search, or debugging why a global filter isn't matching rows.'

Consider adding the user-facing synonym 'search across all columns' alongside the technical term 'globalFilter' to improve trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (global filtering) and multiple concrete actions — "Apply globalFilter across eligible columns", wiring globalFilteringFeature/columnFilteringFeature/filteredRowModel, and manual server filtering — but the actions are framed as API mechanics rather than end-user tasks, leaving minor coverage gaps. Not a 5 because the action list is not a comprehensive set of user-facing capabilities; clearly above the 1-2-action level of a 3.	4 / 5
Completeness	It answers 'what' (apply globalFilter across eligible columns with the listed feature hooks and manual server filtering) and 'when' ("Load when columns unexpectedly participate or a global filter changes state without changing rows"), giving an explicit trigger clause; the 'when' is a single fault-condition rather than a broad set of concrete trigger phrases, so it falls short of the explicit-and-comprehensive level of 5 but clearly exceeds the what-only level of 3.	4 / 5
Trigger Term Quality	Natural phrases like "when columns unexpectedly participate", "a global filter changes state without changing rows" are genuine debug-trigger phrasings a user might say, and "global filter" is a recognizable term; missing common synonyms/variations (e.g. "search across all columns"), so not 5, but well above the generic one-keyword level of 3.	4 / 5
Distinctiveness Conflict Risk	A clear niche (TanStack table global filtering) with very specific fault triggers ("columns unexpectedly participate", "global filter changes state without changing rows") and named features that are unlikely to fire for sibling skills like column-filtering; minimal conflict risk, matching the clear-niche anchor.	5 / 5
	Total	17 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
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
Path: packages/table-core/skills/global-filtering/SKILL.md
Commit: d01c01b

Reviewed: 1 day ago

Table of Contents

Discovery Implementation Validation

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.