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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 complete executable code examples and a clear, real reference file, but it is verbose for an overview and lacks a sequenced migration workflow with validation checkpoints. Tightening the inline catalog and adding an ordered, verify-at-each-step process would lift the weaker dimensions.

Suggestions

Add an ordered, step-by-step migration workflow (e.g. bootstrap hybrid → migrate one component → verify it boots → migrate dependencies) with explicit validation/verification checkpoints, since migration is destructive and the rubric caps such workflows at 2 without them.

Trim the inline before/after catalog and move secondary patterns into references/details.md so SKILL.md reads as a lean overview, improving conciseness and progressive disclosure.

Remove the redundant intro sentence and the 'When to Use This Skill' list that duplicate the frontmatter description to recover token budget.

Dimension	Reasoning	Score
Conciseness	The body is ~309 lines of inline before/after code across eight scenarios plus a redundant intro line and a 'When to Use' list that duplicates the description; efficient and free of concept-explaining fluff, but not lean enough for a 3.	2 / 3
Actionability	Provides fully executable, copy-paste-ready TypeScript and JavaScript before/after examples for controllers, directives, services, DI, routing, and hybrid bootstrap, matching the score-3 fully-executable anchor.	3 / 3
Workflow Clarity	Content is a pattern catalog rather than a sequenced migration workflow, with no validation or verification checkpoints for a destructive/risky migration; the rubric caps such workflows at 2.	2 / 3
Progressive Disclosure	A well-signaled one-level reference to references/details.md exists (verified real), but the main body is a heavy inline code catalog rather than a lean overview pointing out to detail files, so structure is only partially split.	2 / 3
	Total	9 / 12 Passed

Description

100%

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 concise, specific, and clearly answers both what the skill does and when to use it with natural trigger terms, all in third person. It is a strong, well-scoped description with no notable weaknesses.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'hybrid mode, incremental component rewriting, and dependency injection updates' — matching the score-3 anchor of several specific concrete actions rather than the vague score-1 or partial score-2.	3 / 3
Completeness	Explicitly states what ('Migrate from AngularJS to Angular using...') and when ('Use when upgrading AngularJS applications...'), matching the score-3 anchor that answers both with an explicit trigger.	3 / 3
Trigger Term Quality	'upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code' are natural phrases a user would say, giving good coverage rather than only some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	AngularJS-to-Angular migration is a clear niche with distinct triggers unlikely to fire for unrelated skills, matching the score-3 clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: wshobson/agents
Commit: 5cc2549

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