Name: table-state
Rating: 71.2 (1 reviews)
Author: TanStack

table-state

Read Solid-backed table atoms inside JSX, createMemo, createEffect, or table.Subscribe; own slices with Solid signals or external TanStack Store atoms; and apply value-or-updater callbacks correctly. Load for Solid tracking and controlled-state bugs.

Quality

88%

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

93%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 concise, highly actionable, and well-structured with executable examples and concrete wrong/correct patterns. Its only gap is the absence of explicit validation/verify checkpoints, which keeps workflow clarity just below the top anchor.

Dimension	Reasoning	Score
Conciseness	Lean and efficient: it assumes Claude's competence and explains only non-obvious specifics (e.g. 'react only inside a tracked scope; there is no React-style selected table.state object'), with no padding about what Solid or TanStack Table is.	5 / 5
Actionability	Provides copy-paste-ready tsx snippets for setup, signal control, external atom ownership, and resets, plus concrete wrong/correct pairs that cover the common cases.	5 / 5
Workflow Clarity	Sections are clearly sequenced (model → setup → patterns → ownership → init/reset → mistakes → API discovery), but as a guidance/reference doc it lacks explicit validation or verify-checkpoint loops.	4 / 5
Progressive Disclosure	Well-organized into clear sections with one-level-deep pointers (installed .d.ts files, inline source citations) and no nested or buried references; appropriately scoped as a self-contained overview.	5 / 5
	Total	19 / 20 Passed

Description

83%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 distinct, naming concrete actions and a clear niche with low conflict risk. Its main weakness is the terse trigger clause, which leaves completeness and trigger-term coverage slightly short of fully comprehensive.

Suggestions

Expand the 'Load for ...' clause into a fuller 'Use when ...' trigger phrase listing natural variations users would say (e.g. 'SolidJS table state', 'TanStack Table controlled state in Solid').

Add common synonyms/file cues (e.g. '@tanstack/solid-table', 'SolidJS') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete, distinct actions—'Read Solid-backed table atoms inside JSX, createMemo, createEffect', 'own slices with Solid signals or external TanStack Store atoms', and 'apply value-or-updater callbacks'—giving comprehensive coverage of the skill's surface.	5 / 5
Completeness	A clear 'what' (the three concrete actions) and an explicit 'when' ('Load for Solid tracking and controlled-state bugs') are both present, though the trigger clause could be more specific and elaborated.	4 / 5
Trigger Term Quality	Strong domain keywords like 'Solid', 'Solid tracking', 'controlled-state bugs', and 'TanStack Store atoms' are present, but some natural synonyms a user might say (e.g. 'SolidJS table state') are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche (@tanstack/solid-table table-state management) with distinct, library-specific triggers and minimal overlap with other skills.	5 / 5
	Total	18 / 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/solid-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.