Tessl • The management layer for AI agent skills

SkillPublic

getting-started

Create and render Table v9 with the solid adapter. Route reusable createTableHook components, Query and Virtual integration, and framework setup; use table-state for reactive ownership.

Quality

82%

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 an exemplar of efficient skill writing: a complete executable quick start, dense library-specific constraints that are genuinely non-obvious, and clean task-based routing to verified one-level-deep references. The only meaningful gap is the absence of a quick verification cue in the setup workflow.

Suggestions

Add a one-line verification cue after the setup example, e.g. "Verify reactivity: update the signal and confirm the table re-renders; if rows freeze, the data was snapshotted instead of getter-wrapped."

Clarify that the `../table-state` and `../migrate-v8-to-v9` links depend on sibling skills being installed, or inline a one-sentence fallback for when they are absent.

Dimension	Reasoning	Score
Conciseness	The body is lean with zero padding: it skips concepts Claude already knows and concentrates on non-obvious constraints ("`data: data()` captures a snapshot", "Put row-model slots after their prerequisite features in `tableFeatures()`"), with every token earning its place.	5 / 5
Actionability	The setup block is complete, copy-paste-ready code with imports and a working render loop, plus a concrete prerequisite command (`intent load @tanstack/table-core#core`) and exact inspection paths (`node_modules/@tanstack/solid-table/dist/index.d.ts`), covering the common getting-started case fully.	5 / 5
Workflow Clarity	The sequence is explicit (prerequisite load → setup → constraints → task-based routing → API discovery) with an upfront "Before starting" checkpoint, but there is no verification step (e.g., confirming that changing data re-renders via the `get data()` getter), leaving a minor validation gap; the skill is non-destructive, so no destructive-operation cap applies.	4 / 5
Progressive Disclosure	The main file is a concise overview with a quick start, and each "Load by task" bullet pairs explicit task signals with a one-level-deep reference; all three bundle references (create-table-hook.md, with-tanstack-query.md, with-tanstack-virtual.md) exist, and bulk detail (feature registration, API surface) is correctly deferred to the intent system and type declarations.	5 / 5
	Total	19 / 20 Passed

Description

66%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 mostly distinct, naming concrete capabilities of the solid adapter, but it lacks an explicit "Use when..." trigger clause, which both caps completeness and weakens its value for skill selection. Adding natural trigger phrasing (e.g., "Use when setting up @tanstack/solid-table, integrating TanStack Query or Virtual, or migrating Solid tables") would resolve the main weakness.

Suggestions

Add an explicit trigger clause, e.g. "Use when building tables with @tanstack/solid-table, integrating TanStack Query or Virtual, or wiring Solid reactivity to table state."

Include natural synonyms users would say ("TanStack Table", "SolidJS", "virtualized rows/columns") alongside the current API-level terms.

Replace the generic "framework setup" with a concrete action (e.g., "initialize column helpers and tableFeatures") to close the specificity gap.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ("Create and render Table v9 with the solid adapter", "Route reusable createTableHook components, Query and Virtual integration"), but "framework setup" and the verb "Route" are comparatively generic, leaving minor gaps in coverage rather than comprehensive specificity.	4 / 5
Completeness	The "what" is clear ("Create and render Table v9 with the solid adapter"), but there is no "Use when..." clause or equivalent explicit trigger guidance; the second sentence routes sub-topics rather than stating when to invoke the skill, which caps completeness at 3 per the rubric guideline.	3 / 5
Trigger Term Quality	Terms like "solid adapter", "createTableHook", "Query", "Virtual", and "table-state" are ones a TanStack Solid user would naturally use, but common variations and synonyms ("TanStack Table", "SolidJS", "virtualize", "@tanstack/solid-table") are missing, so coverage is good rather than comprehensive.	4 / 5
Distinctiveness Conflict Risk	"solid adapter", "createTableHook", and "table-state" carve a mostly distinct niche with explicit delegation to sibling skills, but "Table v9" plus Query/Virtual overlap with other framework-adapter skills in the same family, leaving minor overlap risk.	4 / 5
	Total	15 / 20 Passed

Validation

81%

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 — 13 / 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
relative_links	Relative link issues: 2 suspicious	Warning

	Total	13 / 16 Passed

Repository: TanStack/table
Path: packages/solid-table/skills/getting-started/SKILL.md
Revision: c14e022

Reviewed: 16 days ago

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.

getting-started

Table of Contents

Is this your skill?