CtrlK
BlogDocsLog inGet started
Tessl Logo

migrate-v8-to-v9

Complete Angular v8-to-v9 migration reference: injectTable and injection context, explicit features and row-model slots, signal/atom state, FlexRender directives, type generics, prototype methods, sorting, sizing, selection, and logical pinning.

67

Quality

82%

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

90%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 content is a lean, highly actionable migration reference with clear sequencing, a failure-mode section, and a final checklist; its main limitation is the absence of an explicit feedback loop and any progressive disclosure via external reference files.

DimensionReasoningScore

Conciseness

The body is dense with terse migration tables and bullets and a single code snippet, assuming Angular/Table competence with no concept-explanation padding; version pins are intrinsic to a migration guide, not gratuitous.

5 / 5

Actionability

Provides complete v8-to-v9 symbol-mapping tables (exact renames for row models, pinning, sorting) and an executable injectTable/tableFeatures TypeScript snippet; the mapping tables are the copy-paste-ready artifact covering common cases.

5 / 5

Workflow Clarity

A 6-step Recommended Migration Order, severity-tagged Common Migration Failures, a Final Checklist, and an API Discovery verification step give a clear sequence with most checkpoints, though there is no explicit validate-fix-retry feedback loop.

4 / 5

Progressive Disclosure

No bundle files exist; the single self-contained ~175-line doc is well-sectioned with clear headers and no broken or deeply nested references, though the large pinning table could be externalized and the over-50-line simple-skill exception does not apply.

4 / 5

Total

18

/

20

Passed

Description

75%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, comprehensive, and clearly distinct, but it lacks an explicit "Use when..." trigger clause, which caps its completeness and leaves natural-language trigger coverage slightly short.

Suggestions

Append an explicit trigger clause, e.g. "Use when migrating an Angular app from TanStack Table v8 to v9."

Add natural-language synonyms users would say ("TanStack Table", "Angular Table") alongside the API jargon to broaden trigger coverage.

Lead with the migration trigger phrase before the enumerated API areas so the "when" is immediately visible.

DimensionReasoningScore

Specificity

Lists many concrete migration actions ("injectTable and injection context, explicit features and row-model slots, signal/atom state, FlexRender directives, type generics, prototype methods, sorting, sizing, selection, and logical pinning") with comprehensive coverage, matching the anchor for multiple specific concrete actions.

5 / 5

Completeness

The "what" is clear and comprehensive, but there is no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric guideline.

3 / 5

Trigger Term Quality

The natural trigger "Angular v8-to-v9 migration" is present, but much of the description is API jargon (injectTable, FlexRender, row-model slots) users would not naturally say; good keyword coverage with a few natural synonyms (e.g. "TanStack Table") missing.

4 / 5

Distinctiveness Conflict Risk

Highly specific niche (Angular v8-to-v9 migration of @tanstack/angular-table) with distinct triggers and minimal overlap with other skills.

5 / 5

Total

17

/

20

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 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

Total

14

/

16

Passed

Repository
TanStack/table
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.