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

table-state

Read Vue-backed table.atoms/store in templates, computed, watch, or table.Subscribe; own slices with refs/computed or external Vue Store atoms; and apply updater callbacks while preserving reactive option shapes.

Quality

68%

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/vue-table/skills/table-state/SKILL.md

Quality

Content

75%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 well-structured, actionable guide with executable wrong/correct examples and a clear state-ownership decision framework, assuming framework competence throughout. It is held back from top marks by minor prose-wiring gaps in one code pattern and length that could justify splitting reference material.

Suggestions

Show the complete controlled-state useTable call inline (features, columns, data, state, onPaginationChange) instead of describing the wiring in prose.

Consider extracting the Common Mistakes catalog into a references file to shorten the main body and improve progressive disclosure.

Add a one-line validation cue after reset examples (e.g. re-read the atom in a tracked context to confirm the new value) to strengthen workflow checkpoints.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Vue/TS competence without explaining basics, and the mental-model prose covers v9-adapter internals Claude would not reliably know; it is efficient with only minor trims possible, fitting the 'efficient; minor instances of over-explanation' anchor rather than the fully lean 5.	4 / 5
Actionability	Executable code with imports and types appears throughout (Setup, controlled-slice pattern, Subscribe JSX, resets, wrong/correct pairs), but the wiring into useTable for the controlled pattern is conveyed in prose ('Pass state: controlledState and onPaginationChange to useTable') rather than a complete copy-paste block, a minor gap.	4 / 5
Workflow Clarity	The 'Choose State Ownership' section gives a clear, prioritized decision sequence (internal → initialState → atoms → state+callback) with explicit precedence rules, and Common Mistakes act as guardrails; there are no destructive/batch operations requiring validation checkpoints, so this lands at clear sequence with minor gaps.	4 / 5
Progressive Disclosure	No bundle files exist and the ~170-line body is organized into well-labeled sections (State Mental Model, Setup, Core Patterns, Choose State Ownership, Initialize/Update/Reset, Common Mistakes, API Discovery) with no nested references; it exceeds the simple-skill threshold so it sits at good structure rather than the 5 reserved for short or cleanly-split skills.	4 / 5
	Total	16 / 20 Passed

Description

62%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 to a well-defined niche and lists concrete API-level actions, but it lacks an explicit 'Use when...' trigger clause and leans on technical jargon over natural user phrasings. Adding a usage trigger and one or two plain-language synonyms would raise the trigger-term and completeness scores.

Suggestions

Append an explicit trigger clause, e.g. 'Use when managing state for @tanstack/vue-table, controlling pagination/sorting slices, or wiring external Vue Store atoms.'

Add plain-language synonyms users actually say ('vue table state', 'controlled table state', 'TanStack vue-table') alongside the API terms.

Mention reset/feature-method handling to close the minor coverage gap in specificity.

Dimension	Reasoning	Score
Specificity	Quotes several concrete actions tied to the API surface — "Read Vue-backed table.atoms/store in templates, computed, watch, or table.Subscribe", "own slices with refs/computed or external Vue Store atoms", "apply updater callbacks while preserving reactive option shapes" — but reset/feature-method coverage is absent, leaving minor gaps rather than comprehensive coverage.	4 / 5
Completeness	The 'what' is clear (read atoms, own slices, apply updater callbacks), but there is no 'Use when...' clause or equivalent explicit trigger guidance, so per the rubric guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Relevant keywords appear (table.atoms/store, table.Subscribe, Vue Store atoms, updater callbacks) but they skew toward API jargon and omit the natural phrases a user would say (e.g. "vue table state", "TanStack vue-table", "controlled state"), matching the 'some relevant keywords but missing common variations' anchor.	3 / 5
Distinctiveness Conflict Risk	The description names a narrow, API-specific niche (TanStack Vue Table v9 state ownership via table.atoms/store and table.Subscribe) with distinct triggers and minimal realistic overlap with other skills.	5 / 5
	Total	15 / 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/vue-table/skills/table-state/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.