angular-migration

Master AngularJS to Angular migration, including hybrid apps, component conversion, dependency injection changes, and routing migration.

Quality

58%

Does it follow best practices?

Impact

Pending

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/antigravity-angular-migration/SKILL.md

Quality

Discovery

67%

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 does well at specifying concrete migration tasks and occupying a clear niche (AngularJS-to-Angular migration). However, it lacks an explicit 'Use when...' clause, which limits its completeness score, and could benefit from additional natural trigger terms users might employ when seeking migration help.

Suggestions

Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about upgrading AngularJS to Angular, migrating legacy Angular 1.x apps, or using ngUpgrade.'

Include additional natural trigger terms like 'upgrade AngularJS', 'ngUpgrade', 'Angular 1.x', 'legacy Angular', and 'Angular 2+ migration' to improve keyword coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions: hybrid apps, component conversion, dependency injection changes, and routing migration. These are distinct, identifiable migration tasks.	3 / 3
Completeness	Clearly answers 'what does this do' (migration tasks including hybrid apps, component conversion, DI changes, routing migration), but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. The rubric caps completeness at 2 when this is missing.	2 / 3
Trigger Term Quality	Includes good terms like 'AngularJS', 'Angular', 'migration', 'hybrid apps', 'component conversion', but misses common user phrases like 'upgrade AngularJS', 'ng-upgrade', 'AngularJS to Angular 2+', or file extensions and module names users might reference.	2 / 3
Distinctiveness Conflict Risk	The combination of 'AngularJS to Angular migration' is a very specific niche. It's unlikely to conflict with general Angular development skills or other framework migration skills due to the explicit AngularJS-to-Angular scope.	3 / 3
	Total	10 / 12 Passed

Implementation

50%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill provides excellent concrete code examples for AngularJS-to-Angular migration patterns, but is far too verbose for a SKILL.md file—most of the before/after examples and general advice are things Claude already knows. The workflow lacks validation checkpoints critical for migration operations, and the bulk of the content should be moved to referenced files to keep the overview lean.

Suggestions

Move the extensive before/after code examples (component, service, forms, routing migration) into referenced files and keep only a single concise example in SKILL.md as a pattern illustration.

Remove sections that explain concepts Claude already knows, such as the Migration Strategies descriptions, Best Practices list, Common Pitfalls list, and Migration Timeline—or condense them to 2-3 lines each.

Add explicit validation checkpoints to the workflow, e.g., 'After setting up hybrid bootstrap, verify both AngularJS and Angular modules load correctly by running tests before proceeding to component migration.'

Trim the 'Use this skill when' / 'Do not use this skill when' sections significantly—Claude can infer most of these from the skill title and description.

Dimension	Reasoning	Score
Conciseness	The skill is extremely verbose at ~300+ lines, with extensive before/after code examples that Claude could generate on its own. Sections like 'Migration Strategies' describe well-known patterns, 'Migration Timeline' is generic project management advice, and 'Best Practices'/'Common Pitfalls' list things Claude already knows. The 'Use this skill when' and 'Do not use this skill when' sections add little value.	1 / 3
Actionability	The code examples are concrete, executable, and copy-paste ready. The hybrid bootstrap setup, component migration before/after examples, service migration, DI downgrade/upgrade patterns, and routing migration all provide specific, working TypeScript/JavaScript code that can be directly used.	3 / 3
Workflow Clarity	The Instructions section provides a 4-step high-level workflow, and the Migration Timeline gives phases, but there are no explicit validation checkpoints or feedback loops. For a migration involving destructive changes and complex interop, the lack of 'validate then proceed' steps is a significant gap.	2 / 3
Progressive Disclosure	The Resources section references external files (references/hybrid-mode.md, scripts/analyze-angular-app.sh, etc.), which is good progressive disclosure. However, the main file itself is monolithic with extensive inline code examples that could be split into referenced files, making the overview much leaner.	2 / 3
	Total	8 / 12 Passed

Validation

90%

Warnings & errors only

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

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: boisenoise/skills-collections
Commit: 431bfad

Reviewed: 2 days ago

Table of Contents

Discovery Implementation Validation

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.