table-state

Read and own Preact Table v9 state with useTable selectors, selected table.state, table.Subscribe, table.atoms/store, controlled slices, and external Preact Store atoms. Load for snapshot-versus-subscription bugs or state render tuning.

Quality

91%

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

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.

A tight, highly actionable reference with executable code and Wrong/Correct mistake patterns that assume Claude's competence. Workflow clarity and progressive disclosure are strong but stop just short of explicit validation loops or external bundle splits.

Dimension	Reasoning	Score
Conciseness	Lean and dense throughout — assumes Claude knows Preact/React and table concepts, with every line earning its place (e.g. 'Only registered features contribute state and types. If pagination is absent... add rowPaginationFeature').	5 / 5
Actionability	Copy-paste executable TSX examples cover the common cases (selector setup, Subscribe, external atoms, resets) and Wrong/Correct pairs give directly applicable fixes.	5 / 5
Workflow Clarity	Clear sectioned structure (Setup, Core Patterns, Choose State Ownership, Initialize/Update/Reset, Common Mistakes) with Wrong/Correct checkpoints, but there is no explicit multi-step validation loop — acceptable here since the operations are not destructive or batch.	4 / 5
Progressive Disclosure	A single well-organized file with clear section headers and one-level-deep pointers ('Inspect node_modules/@tanstack/preact-table/dist/useTable.d.ts'), though a dedicated API-reference bundle could offload the discovery section.	4 / 5
	Total	18 / 20 Passed

Description

92%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 highly specific, third-person description that clearly states both capability and trigger conditions for a narrow Preact Table v9 niche. Trigger term quality is strong but slightly technical, leaving room for more colloquial synonyms.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'useTable selectors, selected table.state, table.Subscribe, table.atoms/store, controlled slices, and external Preact Store atoms' — giving comprehensive, specific coverage rather than vague language.	5 / 5
Completeness	Explicitly answers what ('Read and own Preact Table v9 state with...') and when ('Load for snapshot-versus-subscription bugs or state render tuning') with a concrete trigger clause equivalent to 'Use when'.	5 / 5
Trigger Term Quality	'Load for snapshot-versus-subscription bugs or state render tuning' provides good natural trigger phrases, but the terms are fairly technical and miss common synonyms a user might say (e.g. 'table state bug', 'Preact table not updating').	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to 'Preact Table v9' with framework-native hooks, creating a clear niche with minimal overlap risk against React or generic table skills.	5 / 5
	Total	19 / 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/preact-table/skills/table-state/SKILL.md
Commit: 9e523bc

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.