CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

getting-started

Create and render Table v9 with the ember adapter. Route reusable createTableHook defaults, and framework setup; use table-state for reactive ownership.

Quality

77%

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

Fix and improve this skill with Tessl

tessl review fix ./packages/ember-table/skills/getting-started/SKILL.md
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 exemplary getting-started skill: a complete executable example followed by dense, non-obvious version-specific guidance and well-signaled one-level-deep references. The only minor gap is the absence of explicit validation checkpoints, though the skill's rendering task carries little risk requiring them.

DimensionReasoningScore

Conciseness

The body is lean with no padding and no explanation of concepts Claude already knows; every line carries v9/Ember-specific knowledge (receiver-dependent prototype methods, thunk reactivity, owner binding, the Embroider/ember-auto-import requirement) — matches anchor 5, every token earns its place.

5 / 5

Actionability

The Setup section is a complete, copy-paste-ready .gts component covering the common case, and the construction guidance is concrete ("pass `this` as the owner", "Register `columnVisibilityFeature` before switching to `row.getVisibleCells()`") with inspectable .d.ts paths — matches anchor 5.

5 / 5

Workflow Clarity

The sequence is clear and well-ordered (prerequisites → setup → construction rules → conditional further reading → API discovery) and the single task is unambiguous, but there are no explicit validation checkpoints and the body exceeds the under-50-line simple-skill threshold — between anchors 4 and 5, closer to 4.

4 / 5

Progressive Disclosure

The single reference (references/create-table-hook.md) exists, is one level deep with real content (verified), and is clearly signaled with its purpose ("When tables share features, defaults, or reusable UI, read [create-table-hook]…"), while the body keeps reference-level material out — matches anchor 5.

5 / 5

Total

19

/

20

Passed

Description

53%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 names a distinct niche and several concrete capabilities, but it lacks any explicit "when to use" trigger guidance and omits the natural library names (TanStack) users would say. Phrasing like "Route reusable createTableHook defaults, and framework setup" is muddled and partially generic. It sits at the midpoint of the rubric.

Suggestions

Add a "Use when…" clause with concrete triggers, e.g. "Use when building a TanStack Table v9 data table in an Ember app, or when the user mentions @tanstack/ember-table, ember-table, or Table v9."

Include the natural library name and synonyms ("TanStack Table", "@tanstack/ember-table", "data table") so trigger matching works on the phrases users actually say.

Rewrite "Route reusable createTableHook defaults, and framework setup" into parallel concrete verbs, e.g. "Share features and defaults across tables with createTableHook; set up the Ember adapter with .gts components and Glint."

DimensionReasoningScore

Specificity

Names the domain and a few concrete actions ("Create and render Table v9 with the ember adapter", "Route reusable createTableHook defaults", "use table-state for reactive ownership"), but "framework setup" is generic, the routing clause is muddled, and coverage of table capabilities (columns, features, sorting) is incomplete — between anchors 3 and 4, closer to 3.

3 / 5

Completeness

The "what" is clear (create, render, route reusable defaults, use table-state), but there is no "Use when…" clause or equivalent explicit trigger guidance, which caps completeness at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

"Table v9" and "ember adapter" are relevant keywords, but the description omits the library names users would naturally say ("TanStack", "@tanstack/ember-table") and common synonyms ("data table"), while "createTableHook" and "reactive ownership" lean technical jargon — matches anchor 3 (some relevant keywords, missing common variations).

3 / 5

Distinctiveness Conflict Risk

"Table v9 with the ember adapter", "createTableHook", and "table-state" carve a distinct niche; only minor overlap risk with closely related sibling skills (other framework adapters, the table-state skill) — matches anchor 4, not 5 since it does not state distinguishing trigger phrases.

4 / 5

Total

13

/

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: 1 suspicious

Warning

Total

13

/

16

Passed

Repository

TanStack/table

Path

packages/ember-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.