Name: table-state
Rating: 60.8 (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

72%

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

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 body is a tight, highly actionable reference with concrete code and Wrong/Correct guardrails, well organized into logical sections. Its only weak spot is the absence of explicit validation checkpoints and any split-out reference files, though neither is strictly required for this pattern-oriented skill.

Dimension	Reasoning	Score
Conciseness	Lean and efficient throughout — it assumes Vue/TanStack competence and every sentence earns its place (e.g. "Without initialState, atoms, state, or on[State]Change, the table owns every registered slice") with no general-knowledge padding.	5 / 5
Actionability	Fully executable, copy-paste-ready code for setup, controlled-state with updater handling, Subscribe JSX, and resets, plus concrete Wrong/Correct pairs that cover the common cases.	5 / 5
Workflow Clarity	Logically sequenced from mental model to setup, patterns, ownership decisions, init/update/reset, and common mistakes with decision guardrails ("Use exactly one owner per slice"); no destructive/batch operation requires validation, but explicit checkpoints are absent.	4 / 5
Progressive Disclosure	Single well-sectioned file with clear headers and an API Discovery section that points out to installed .d.ts files; no bundle reference files exist, so all content is inline with minor organization gaps.	4 / 5
	Total	18 / 20 Passed

Description

55%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 highly distinct, but it is written almost entirely in API jargon and omits any explicit "Use when…" trigger guidance. Adding natural trigger phrases would substantially raise its completeness and trigger-term quality.

Suggestions

Append a "Use when…" clause naming natural triggers, e.g. "Use when managing TanStack table state in Vue, controlling slices like pagination/sorting, or wiring table.atoms to refs/computed."

Replace some API jargon with user-facing synonyms ("controlled table state", "external state ownership", "pagination/sorting state") so the description matches phrases users actually say.

Mention the common slice names (pagination, sorting, visibility, selection) to broaden keyword coverage and improve trigger matching.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "Read Vue-backed table.atoms/store", "own slices with refs/computed or external Vue Store atoms", "apply updater callbacks while preserving reactive option shapes" — though coverage is narrow to this one domain.	4 / 5
Completeness	It clearly states what the skill does but provides no "Use when…" clause or equivalent trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	The terms present ("table.atoms/store", "table.Subscribe", "Vue Store atoms", "updater callbacks", "reactive option shapes") are API jargon; the natural phrases a user would actually say ("manage TanStack table state", "controlled state", "pagination state") are missing.	2 / 5
Distinctiveness Conflict Risk	Tightly scoped to TanStack Vue table state ownership with distinct API triggers (table.atoms/store, table.Subscribe), giving it a clear niche with minimal conflict risk.	5 / 5
	Total	14 / 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: 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.