angular-migration

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

Quality

65%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/angular-migration/SKILL.md

The canonical home for this skill is angular-migration in rmyndharis/antigravity-skills

Quality

Content

65%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 highly actionable with comprehensive executable code, but it suffers from inlined content that duplicates advertised (yet missing) reference files and lacks explicit validation feedback loops for a risky migration workflow.

Suggestions

Move the detailed pattern sections (hybrid setup, component/DI/routing/forms migration) into the advertised reference files and keep SKILL.md as a concise overview pointing to them.

Add explicit validation checkpoints with commands — e.g. run the test suite after each feature migration, confirm hybrid compatibility before cutover — as a validate→fix→retry loop.

Remove the duplicate description line at the top of the body and create the missing references/ assets/ scripts/ files so the Resources links resolve.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean code with little concept-padding, but it inlines detailed pattern coverage (hybrid, components, DI, routing, forms) that is simultaneously advertised as separate reference files, and repeats the frontmatter description verbatim at line 11 — so it could be meaningfully tightened.	3 / 5
Actionability	Fully executable, copy-paste-ready TypeScript/JavaScript examples cover the common cases — bootstrap, controller→component, directive→component, service, DI downgrade/upgrade, routing, and forms — with complete imports and syntax.	5 / 5
Workflow Clarity	A sequenced Instructions list and Migration Timeline exist, but validation is generic ('Validate with tests', 'Test thoroughly') rather than explicit validate→fix→retry checkpoints; because migration is a high-risk batch/destructive operation, the rubric caps this at 3.	3 / 5
Progressive Disclosure	Section structure is clear and a Resources section signals one-level-deep references, but the referenced files (references/.md, assets/.ts, scripts/*.sh) do not exist in the bundle and the content that should live in them is inlined here, leaving the split incomplete.	3 / 5
	Total	14 / 20 Passed

Description

66%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 and distinct, listing four concrete migration areas, but it lacks any explicit trigger ('Use when...') clause, which caps completeness and slightly weakens distinctiveness.

Suggestions

Add an explicit trigger clause, e.g. 'Use when migrating AngularJS (1.x) apps to Angular (2+), running hybrid ngUpgrade apps, or converting directives/controllers to components.'

Surface additional natural keywords users say — ngUpgrade, directives-to-components, TypeScript migration, 1.x to 2+ — to improve trigger-term coverage.

Reflect forms and service migration in the description to close the coverage gap with the body content.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete sub-areas — 'hybrid apps, component conversion, dependency injection changes, and routing migration' — but gaps remain (forms, services, testing covered in the body are absent here), so it stops short of comprehensive coverage.	4 / 5
Completeness	It states a clear 'what' (master AngularJS→Angular migration across named areas) but provides no 'Use when...' clause or explicit trigger guidance, capping completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	Includes natural terms a user would say ('AngularJS to Angular migration', 'hybrid apps', 'component conversion', 'dependency injection', 'routing migration'), but misses common synonyms such as ngUpgrade, directives, TypeScript, and '1.x to 2+'.	4 / 5
Distinctiveness Conflict Risk	'Master AngularJS to Angular migration' carves a clear, specific niche with low conflict risk, but without an explicit 'when' the boundary against general Angular-development skills is slightly fuzzy, leaving minor overlap risk.	4 / 5
	Total	15 / 20 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/angular-migration/SKILL.md
Commit: 900c504

Reviewed: 4 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.