CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

migrate-v8-to-v9

Migrate angular Table v8 to v9. Audit framework construction, rendering, state, and app hooks, with shared API changes in the core migration skill.

Quality

76%

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/angular-table/skills/migrate-v8-to-v9/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

86%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 lean migration checklist: correctly sequenced (core skill first, prerequisites, adapter checklist, mappings, final checks) with symbol-level actionable items and disciplined one-level-deep reference delegation. Its only weakness is the absence of a minimal before/after code example for the central injectTable change and any post-migration verification feedback loop.

DimensionReasoningScore

Conciseness

The body is entirely lean — terse checklists, a single load command, and node_modules inspection paths with zero padding or explanation of concepts Claude already knows. Every token instructs and assumes competence, matching the 'lean and efficient' anchor.

5 / 5

Actionability

Gives concrete, symbol-level guidance — "Replace `createAngularTable` with `injectTable` in a valid Angular injection context", "Import current FlexRender directives", and exact inspection paths under node_modules — with only minor gaps. Not 5 because there is no before/after code snippet for the central construction change, leaving the executor to assemble the shape from the reference file.

4 / 5

Workflow Clarity

Clear sequence: load the core skill first and audit its checklist, check framework prerequisites, work the Angular checklist, apply affected mappings, then verify via the "Final checks" section, which acts as a validation checkpoint list. Not 5 because there is no error-recovery or verification feedback loop (e.g. re-running type checks after each migration step).

4 / 5

Progressive Disclosure

The SKILL.md is a concise overview that delegates detail to a real, one-level-deep reference (references/adapter-migration.md, verified to exist) with clearly signaled scope — "Read [adapter-migration](references/adapter-migration.md) when changing construction, rendering, state, or app hooks" — plus well-scoped cross-skill pointers for examples and state repairs. Matches the 'clear overview with well-signaled one-level-deep references' anchor.

5 / 5

Total

18

/

20

Passed

Description

58%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 states a clear, specific what — migrating the Angular Table adapter from v8 to v9 and auditing its construction, rendering, state, and app hooks — but provides no explicit when-to-use trigger guidance and misses natural keywords like "TanStack", "upgrade", and the package name. It is specific but incomplete as a trigger surface.

Suggestions

Add a 'Use when...' clause, e.g. 'Use when migrating a TanStack Angular Table app from v8 to v9 or upgrading @tanstack/angular-table to v9.x'.

Include natural trigger terms users would actually say — "TanStack Table", "@tanstack/angular-table", "upgrade", "Angular 19" — rather than only "angular Table v8 to v9".

Name one or two concrete API-level changes (e.g. "createAngularTable → injectTable") to push specificity from several audit areas toward comprehensive coverage.

DimensionReasoningScore

Specificity

Names the domain ("Migrate angular Table v8 to v9") and several concrete action areas ("Audit framework construction, rendering, state, and app hooks"), matching the 'several specific actions; minor gaps' anchor. Not 5 because the actions stay at the audit-area level without listing concrete transformations or API-level changes.

4 / 5

Completeness

The 'what' is clear (migrate the angular Table adapter from v8 to v9 and audit construction, rendering, state, and app hooks), but there is no 'Use when...' clause or equivalent explicit trigger guidance, which caps this dimension at 3 per the judging guidelines.

3 / 5

Trigger Term Quality

Includes natural terms like "Migrate", "angular Table", and "v8 to v9", but misses common variations a user would say — "TanStack", "upgrade", or the package name "@tanstack/angular-table" (which appears only in metadata, not the description). Matches 'some relevant keywords but missing common variations or synonyms'.

3 / 5

Distinctiveness Conflict Risk

"angular Table v8 to v9" carves a fairly distinct niche with version-specific triggers, but it could overlap with sibling framework-adapter migration skills and the core migration skill it references. Matches 'mostly distinct; minor overlap risk with closely related skills'.

4 / 5

Total

14

/

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/angular-table/skills/migrate-v8-to-v9/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.