CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

getting-started

Create and render Table v9 with the preact adapter. Route reusable createTableHook components, Query and 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
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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 excellent example of skill content: a complete executable quick-start, dense non-redundant constraints, and precise task-based progressive disclosure to real one-level-deep reference files. The only minor gap is the lack of an explicit verification step after setup, which keeps workflow clarity just below perfect. No changes are needed for the skill's core quality.

DimensionReasoningScore

Conciseness

The body contains no background exposition — no library intro or concept explanation — and every section earns its tokens: a complete setup example, one dense constraints paragraph, task-keyed routing, and concrete .d.ts paths; the v8 mention functions as an old-pattern callout rather than version padding.

5 / 5

Actionability

The Setup block is fully executable, copy-paste-ready TSX (imports, column helper, state, complete render markup), the prerequisite "intent load @tanstack/table-core#core" is a runnable command, and "API discovery" names exact node_modules paths — fully covering the common case.

5 / 5

Workflow Clarity

The sequence is clear and correctly ordered (load core intent → setup → constraints → route by task → inspect declarations as fallback) with no risky operations requiring validation, but no explicit verification checkpoint (e.g., confirm types or render) exists and the body exceeds the under-50-line simple-skill exception, placing it just below the anchor with explicit validation steps.

4 / 5

Progressive Disclosure

The body is a lean overview with exemplary task-keyed routing in "Load by task": all three references/*.md targets exist in the bundle, match their one-line summaries, and are one level deep, with cross-skill pointers clearly signaled — an easy match for the well-signaled one-level-deep 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, domain-grounded, and clearly distinct from sibling skills, with strong natural trigger terms for the Preact Table domain. Its main weakness is the absence of any explicit "Use when..." trigger clause, which caps completeness and leaves the invocation conditions implicit. Adding an explicit when-to-use clause and fuller synonyms (TanStack Table, @tanstack/preact-table) would raise it further.

Suggestions

Add an explicit trigger clause, e.g. "Use when setting up or rendering TanStack Table v9 tables in Preact apps, or when the user mentions preact-table, useTable, or createTableHook."

Include the natural synonyms "TanStack Table" and the package name "@tanstack/preact-table" so users who type the full library or package name match the description.

Replace the generic phrase "framework setup" with a concrete action (e.g. "register features via tableFeatures()") so every listed capability is specific.

DimensionReasoningScore

Specificity

"Create and render Table v9 with the preact adapter" and "Route reusable createTableHook components, Query and Virtual integration" list several concrete, domain-specific actions, but "framework setup" is generic and "reactive ownership" is abstract, leaving minor coverage gaps that keep it below the comprehensive anchor 5.

4 / 5

Completeness

The 'what' is explicit and concrete, but there is no "Use when..." clause or equivalent trigger guidance; "use table-state for reactive ownership" routes to a sibling skill rather than stating when this skill applies, so completeness is capped at 3 per the judging guideline.

3 / 5

Trigger Term Quality

Good natural keyword coverage (preact, Table v9, Query, Virtual, table state, createTableHook), but the full "TanStack Table" name and the @tanstack/preact-table package handle — phrases users would plausibly type — are missing, so it does not reach comprehensive synonym-level coverage.

4 / 5

Distinctiveness Conflict Risk

"Table v9 with the preact adapter" carves a clear niche distinct from other framework adapters and table-core, and explicitly delegating reactive state to table-state minimizes overlap with sibling skills — a clean match for the minimal-conflict anchor.

5 / 5

Total

16

/

20

Passed

Validation

81%

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

CriteriaDescriptionResult

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/preact-table/skills/getting-started/SKILL.md

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.