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.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/angular-migration/SKILL.md

Quality

Content

57%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 code-rich and actionable, with clear sections and a Resources pointer, but it is long, inlines content that the Resources section implies lives in separate files, and lacks an explicit validation feedback loop for a risky migration workflow. The biggest issue is that every referenced bundle file is missing.

Suggestions

Create the referenced bundle files (references/hybrid-mode.md, component-migration.md, dependency-injection.md, routing.md; assets/hybrid-bootstrap.ts, migration-timeline.md; scripts/analyze-angular-app.sh) or remove the broken references — currently every link in the Resources section 404s.

Add an explicit validate->fix->retry feedback loop to the Instructions workflow (e.g., 'run tests; if failing, fix and re-run; only proceed to cutover when green') so the destructive migration sequence clears the validation cap.

Move the long before/after code catalogs (component/service/DI/routing/forms migration) into the reference files and keep SKILL.md as a concise overview with one representative example, improving both conciseness and progressive disclosure.

Dimension	Reasoning	Score
Conciseness	The ~425-line body is mostly code with little concept-over-explanation, but it inlines lengthy before/after pairs across many domains and extra sections (timeline, best practices, pitfalls) that could be tightened or offloaded to reference files.	3 / 5
Actionability	Provides numerous concrete, mostly copy-paste-ready TypeScript/JavaScript before/after patterns for hybrid setup, components, services, DI, routing, and forms, with only minor gaps (placeholder APIs and 'any' types in spots).	4 / 5
Workflow Clarity	The four-step Instructions list a real sequence and mention validation ('Validate with tests') plus a Safety section, but there is no explicit validate->fix->retry feedback loop for this destructive migration operation, which caps the score.	3 / 5
Progressive Disclosure	Section structure and a dedicated Resources list are present and clearly signaled, but the referenced bundle files (references/.md, assets/, scripts/*) do not exist and the corresponding detail is inlined in the body rather than split out.	3 / 5
	Total	13 / 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 mechanisms, gives explicit 'Use when' trigger guidance, and carves out a distinct niche. The only weakness is slightly limited trigger synonym coverage and a few migration sub-domains (routing, forms) not named explicitly.

Dimension	Reasoning	Score
Specificity	Names the domain (AngularJS to Angular migration) and several concrete mechanisms — 'hybrid mode, incremental component rewriting, and dependency injection updates' — but omits routing/forms, leaving minor coverage gaps rather than the comprehensive list needed for a 5.	4 / 5
Completeness	Explicitly answers both 'what' (Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and DI updates) and 'when' (Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code) 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 coverage, but lacks synonyms like 'Angular 1.x' or 'ng1' that would warrant a 5.	4 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (AngularJS-to-Angular migration) with distinct triggers that would not fire for general Angular or unrelated skills, giving minimal conflict risk.	5 / 5
	Total	18 / 20 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	15 / 16 Passed

Repository: rmyndharis/antigravity-skills
Path: skills/angular-migration/SKILL.md
Commit: 3eff4af

Reviewed: about 23 hours 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.