CtrlK
BlogDocsLog inGet started
Tessl Logo

table-state

Use TableController-selected table.state, table.atoms/store, stable table.subscribe selectors, controlled reactive properties plus on*Change, and external TanStack Store atoms. Load when Lit state appears stale, host updates are too broad, or table state must be shared outside the element.

70

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 well-structured, actionable reference skill with complete executable examples and clear decision guidance. The main gaps are minor: a few trimmable prose passages and the absence of explicit validation checkpoints for state mutations.

Suggestions

Tighten the prose in 'State Mental Model' and 'Choose State Ownership' to bullet essentials, removing sentences that restate what the code already shows.

Add an explicit validate/verify step after state-mutating operations (e.g., confirm table.state reflects the expected slice after a reset or external-atom write).

Consider extracting the Common Mistakes catalog or detailed API discovery notes into a reference file to keep SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

The body is dense and domain-specific (state coordinator, baseAtoms, store precedence) and assumes Lit/TanStack competence without padding basic concepts, but a few explanatory sentences in 'State Mental Model' and 'Choose State Ownership' could be trimmed.

4 / 5

Actionability

The Setup section provides a complete, copy-paste-ready LitElement with TableController wiring, supplemented by executable snippets (table.subscribe island, reset calls) and concrete wrong/correct guidance in Common Mistakes.

5 / 5

Workflow Clarity

Decision rules are clear ('Use exactly one owner per slice', ownership precedence) and Common Mistakes act as error-prevention guidance, but there is no explicit validate/verify checkpoint for the state-mutating operations.

4 / 5

Progressive Disclosure

No bundle files exist; the single SKILL.md is well-organized into focused sections (Setup, Core Patterns, Choose State Ownership, Common Mistakes, API Discovery) with clear headers, though at ~135 lines some material could plausibly live in separate reference files.

4 / 5

Total

17

/

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 strong, specific description that concretely names its capabilities and provides an explicit load trigger in third-person imperative voice. The only minor weakness is trigger-term breadth, which is solid but somewhat technical.

DimensionReasoningScore

Specificity

Lists multiple concrete capabilities — 'TableController-selected table.state', 'table.atoms/store', 'stable table.subscribe selectors', 'controlled reactive properties plus on*Change', and 'external TanStack Store atoms' — giving comprehensive, specific coverage rather than vague language.

5 / 5

Completeness

It explicitly answers both 'what' (the table.state/atoms/store/subscribe/on*Change capabilities) and 'when' via the explicit 'Load when...' trigger phrase with concrete conditions.

5 / 5

Trigger Term Quality

The 'Load when Lit state appears stale, host updates are too broad, or table state must be shared outside the element' clause gives good natural triggers a Lit developer would voice, though coverage leans technical and misses a few common synonyms.

4 / 5

Distinctiveness Conflict Risk

The scope is tightly bound to TanStack Lit table-state coordination, a clear niche with distinctive triggers and minimal overlap risk with other skills.

5 / 5

Total

19

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.