CtrlK
BlogDocsLog inGet started
Tessl Logo

angular-migration

Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code.

68

Quality

81%

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

76%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 highly actionable with comprehensive executable before/after examples and good progressive disclosure via a real one-level reference. Its main weakness is workflow clarity: migration is a destructive, multi-step process but the body offers no sequenced steps with validation checkpoints.

Suggestions

Add an explicit numbered migration workflow (e.g. set up hybrid app -> migrate services -> migrate components feature-by-feature -> remove AngularJS) with validation checkpoints such as 'run the test suite and confirm hybrid boot succeeds before proceeding'.

Include a verify/retry feedback loop for destructive steps — for example, after downgrading or upgrading a service, validate that the hybrid app still compiles and the migrated route loads before moving on.

Trim or relocate some of the inline before/after examples (e.g. forms, additional DI patterns already in references/details.md) to keep SKILL.md a leaner overview that points to the reference.

DimensionReasoningScore

Conciseness

The body is mostly efficient with tight bulleted sections and minimal prose around executable code, though it is fairly long overall; a few sections could be trimmed or pushed to references.

4 / 5

Actionability

Provides fully executable, copy-paste-ready before/after code for controllers, directives, services, dependency injection, and routing, covering the common migration cases concretely.

5 / 5

Workflow Clarity

Migration strategies are presented as labeled options with 'Best for' guidance, but the main body lacks an explicit step-by-step migration sequence with validation checkpoints, and destructive/batch migration work has no validate/verify feedback loop.

3 / 5

Progressive Disclosure

Clear section structure with a well-signaled one-level-deep reference to references/details.md that exists as a real file; minor gaps in that substantial pattern content remains inline rather than split out.

4 / 5

Total

16

/

20

Passed

Description

87%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 strong: it states concrete migration actions, provides explicit 'Use when' triggers covering multiple natural phrasings, and occupies a distinct niche. Minor specificity and synonym coverage gaps keep two dimensions at 4 rather than 5.

DimensionReasoningScore

Specificity

Names the domain (AngularJS to Angular) and lists several concrete actions including 'hybrid mode, incremental component rewriting, and dependency injection updates', with only minor coverage gaps.

4 / 5

Completeness

Explicitly answers both 'what' (Migrate from AngularJS to Angular using...) and 'when' (Use when upgrading AngularJS applications, planning framework migrations...) with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would say ('upgrading AngularJS applications, planning framework migrations, modernizing legacy Angular code') with good keyword coverage, though a few synonyms are missing.

4 / 5

Distinctiveness Conflict Risk

Targets a clear niche (AngularJS to Angular migration) with distinct triggers and minimal overlap risk with unrelated skills.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
wshobson/agents
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.