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.
81
71%
Does it follow best practices?
Impact
100%
1.06xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/framework-migration/skills/angular-migration/SKILL.mdQuality
Discovery
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.
This is a strong skill description that clearly identifies a specific migration path (AngularJS to Angular), lists concrete techniques used, and provides explicit trigger guidance via a 'Use when' clause. It uses proper third-person voice and includes natural keywords that users would employ when seeking this kind of help. The description is concise yet comprehensive.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'hybrid mode', 'incremental component rewriting', and 'dependency injection updates'. These are concrete migration techniques, not vague abstractions. | 3 / 3 |
Completeness | Clearly answers both 'what' (migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates) and 'when' (explicit 'Use when' clause covering upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'AngularJS', 'Angular', 'migrate', 'upgrading', 'framework migrations', 'modernizing', 'legacy Angular code'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: specifically AngularJS-to-Angular migration. The combination of 'AngularJS', 'Angular', 'hybrid mode', and 'migration' creates a very specific trigger profile unlikely to conflict with general frontend or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides comprehensive, executable code examples for AngularJS-to-Angular migration but suffers from extreme verbosity and poor organization. It reads more like a tutorial or reference guide than a concise skill file, dumping all content inline without progressive disclosure. It also lacks validation checkpoints critical for a complex multi-phase migration process.
Suggestions
Drastically reduce the main SKILL.md to a concise overview with the hybrid bootstrap setup and one component migration example, moving detailed before/after examples for services, routing, forms, and DI into separate referenced files (e.g., COMPONENTS.md, SERVICES.md, ROUTING.md).
Add explicit validation/verification steps to the workflow, such as 'Run ng build after each component migration to verify no compilation errors' and 'Test hybrid interop with ng e2e before proceeding to next feature'.
Remove the 'When to Use This Skill' section (redundant with frontmatter description) and the generic migration timeline with week estimates, which Claude doesn't need.
Add a quick-reference checklist summarizing the key conversion patterns (e.g., '$scope.x → class property', '$http → HttpClient', 'ng-model → [(ngModel)]') instead of lengthy before/after blocks.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose with extensive before/after code examples that Claude already knows how to produce. The 'When to Use This Skill' section restates the description, the migration strategies section explains basic concepts, and the migration timeline with generic week estimates adds little value. Much of this is reference material Claude already has knowledge of. | 1 / 3 |
Actionability | The code examples are fully executable and copy-paste ready, covering hybrid app setup, component migration, service migration, DI bridging, routing, and forms. Each before/after pair is concrete and complete enough to act on directly. | 3 / 3 |
Workflow Clarity | The migration timeline provides a phased sequence, and the strategies section outlines approaches, but there are no validation checkpoints, no verification steps after each migration phase, and no feedback loops for catching errors during the hybrid setup or component conversion process. | 2 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files. At ~250+ lines of inline code examples covering 7+ distinct topics (hybrid setup, components, services, DI, routing, forms, timeline), much of this content should be split into separate reference files with a concise overview in the main skill. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- wshobson/agents
- Commit
91fe43e
- Reviewed
Table of Contents
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.