angular-migration

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

57%

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 before/after code across all major migration areas, but it is presented as a monolithic inline wall and lacks validation checkpoints for a risky operation. Critically, the referenced bundle files (references/, assets/, scripts/) do not exist, breaking progressive disclosure.

Suggestions

Create the referenced bundle files (references/*.md, assets/hybrid-bootstrap.ts, assets/migration-timeline.md, scripts/analyze-angular-app.sh) or remove the broken references from the Resources section.

Move the large before/after code galleries into the corresponding reference files and keep SKILL.md as a concise overview pointing one level deep to them.

Add explicit validation checkpoints to the Instructions and Migration Timeline (e.g., 'run the test suite and confirm hybrid bootstrap compiles before moving to the next phase') with a validate-fix-retry loop.

Dimension	Reasoning	Score
Conciseness	The body is largely efficient with concrete before/after code blocks, but it includes concept-level explanation Claude already knows (restating what each migration pattern does) and long inline examples that could be offloaded to references, so it is mostly rather than fully lean.	2 / 3
Actionability	Provides complete, copy-paste-ready before/after code for controllers, directives, services, DI upgrades/downgrades, routing, and forms — fully executable and specific rather than pseudocode.	3 / 3
Workflow Clarity	A numbered Instructions sequence and a phased Migration Timeline exist, but for a migration (a destructive, batch-style operation) there are no explicit validation checkpoints or validate-fix-retry feedback loops beyond the generic Safety and 'Test Continuously' notes, capping workflow clarity at 2.	2 / 3
Progressive Disclosure	The Resources section references references/, assets/, and scripts/ files, but none of these bundle directories exist on disk — the references are broken/missing — and the body itself is a monolithic 400+ line wall of inline code, so navigation and structure are poor.	1 / 3
	Total	8 / 12 Passed

Description

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 is specific and clearly defines a distinctive migration niche, but it lacks an explicit 'Use when...' trigger clause, leaving the 'when to use' guidance implicit. Adding explicit trigger conditions would raise completeness and trigger term quality.

Suggestions

Append an explicit 'Use when...' clause naming natural user phrasing, e.g. 'Use when migrating an AngularJS (1.x) app to modern Angular (2+), running hybrid ngUpgrade apps, or converting directives/controllers to components.'

Add common trigger variations such as 'AngularJS 1.x', 'ngUpgrade', 'hybrid Angular', and 'directive to component' so users' natural phrasing matches.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'hybrid apps, component conversion, dependency injection changes, and routing migration' — naming several distinct migration activities.	3 / 3
Completeness	Clearly states what the skill does, but has no explicit 'Use when...' trigger clause; the 'when' is only implied, which caps completeness at 2 per the rubric.	2 / 3
Trigger Term Quality	Contains relevant domain terms ('AngularJS', 'Angular', 'hybrid apps', 'component conversion', 'dependency injection', 'routing') but lacks the natural variations a user would commonly say, and omits version cues like '1.x' or '2+' that aid triggering.	2 / 3
Distinctiveness Conflict Risk	The AngularJS-to-Angular migration niche is distinctive and unlikely to trigger for unrelated skills, with clear domain-specific triggers.	3 / 3
	Total	10 / 12 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: boisenoise/skills-collections
Commit: 56fd61a

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