Tessl • The management layer for AI agent skills

SkillPublic

getting-started

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

Quality

83%

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 exemplary getting-started skill: fully executable setup code, dense v9-specific guidance with no padding, and a clean task-conditioned routing section to real bundle references. The only gap is the absence of an explicit render-verification checkpoint in the workflow.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes competence: no library intro or generic concept explanation, and every sentence carries v9-specific facts like "V9 takes only the host in its constructor; pass current options to controller.table(...) during every render", matching the lean-and-efficient 5 anchor with nothing to trim for the 4 anchor's minor over-explanation.	5 / 5
Actionability	The Setup block is a complete, copy-paste-ready Lit component with imports, decorators, repeat/FlexRender usage, and typed data, plus concrete API inspection paths ("Inspect node_modules/@tanstack/lit-table/dist/index.d.ts"), matching the fully-executable 5 anchor.	5 / 5
Workflow Clarity	A clear sequence is present ("Load intent load @tanstack/table-core#core first", keep one TableController, keep features/columns/data stable, then route to per-task references), but there is no explicit verification checkpoint such as confirming the rendered table, matching the 4 anchor's minor validation gaps rather than the 5 anchor's explicit validation steps.	4 / 5
Progressive Disclosure	The "Read for the task" section maps each condition to a well-signaled, one-level-deep reference (references/create-table-hook.md and references/with-tanstack-virtual.md, both verified to exist with matching content), plus sibling-skill routing, matching the clear-overview 5 anchor.	5 / 5
	Total	19 / 20 Passed

Description

70%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 clearly delineated within the TanStack Table skill family, with concrete v9/lit terminology throughout. Its main weakness is the missing "Use when..." trigger clause, which caps completeness and leaves invocation conditions implicit.

Suggestions

Add an explicit trigger clause, e.g. "Use when building tables with @tanstack/lit-table in Lit components, integrating TanStack Virtual, or sharing table setup via createTableHook."

Include natural synonyms users would say — "TanStack Table", "lit table", "virtual rows/scrolling" — so the description matches how the need is actually phrased.

State the migration boundary in the description (e.g. "For v8 upgrades, use migrate-v8-to-v9") to further reduce overlap risk with the sibling migration skill.

Dimension	Reasoning	Score
Specificity	Names several concrete actions — "Create and render Table v9 with the lit adapter", "Route reusable createTableHook components, Virtual integration, and framework setup" — with only minor coverage gaps, matching the 'several specific actions' anchor rather than the 1-2 actions of the 3 anchor or the comprehensive coverage of the 5 anchor.	4 / 5
Completeness	The 'what' is clear (create/render/route components for the lit adapter), but there is no "Use when..." clause or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 3; it is not 4 because 'when' is entirely absent rather than merely imprecise.	3 / 5
Trigger Term Quality	"lit adapter", "Table v9", "Virtual integration", "createTableHook", and "table-state" are terms users of this stack would naturally say, giving good keyword coverage; it falls short of the 5 anchor because common variations like "TanStack", "virtual rows", or "virtual scrolling" are missing.	4 / 5
Distinctiveness Conflict Risk	"lit adapter" for Table v9 carves a clear niche, and explicitly delegating "use table-state for reactive ownership" delineates the boundary from sibling skills, giving minimal conflict risk per the 5 anchor rather than the minor-overlap 4 anchor.	5 / 5
	Total	16 / 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: 3 suspicious	Warning

	Total	13 / 16 Passed

Repository: TanStack/table
Path: packages/lit-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?