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.
72
57%
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 niche (AngularJS-to-Angular migration), lists concrete techniques, and includes an explicit 'Use when' clause with natural trigger terms. It covers multiple user phrasings and is highly distinguishable from other skills.
| 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, dependency injection updates) and 'when' (explicit 'Use when' clause covering upgrading AngularJS apps, 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 multiple natural phrasings a user might employ. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive — targets a very specific migration path (AngularJS to Angular) with specific techniques. Unlikely to conflict with general frontend, React, or other framework skills due to the precise AngularJS-to-Angular niche. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
14%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads more like a tutorial or reference guide than an actionable skill for Claude. It's excessively verbose, covering topics Claude already understands (Angular component syntax, DI patterns, routing), while missing the practical workflow guidance (validation steps, error handling, rollback strategies) that would actually help during a real migration. The monolithic structure makes it inefficient for context window usage.
Suggestions
Drastically reduce content to only migration-specific gotchas and decisions Claude wouldn't already know (e.g., ngUpgrade bootstrap order quirks, common pitfalls), removing standard Angular/AngularJS syntax examples.
Add explicit validation checkpoints between migration phases: e.g., 'After hybrid bootstrap, verify both frameworks render by checking [specific indicator]' and 'Run ng build --prod after each component migration to catch AOT issues early.'
Split content into separate files by concern (e.g., HYBRID_SETUP.md, COMPONENT_MIGRATION.md, DI_INTEROP.md) and keep SKILL.md as a concise overview with clear references.
Add a concrete decision tree or checklist for choosing migration strategy based on app characteristics, rather than vague 'best for' labels.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~250+ lines, with extensive before/after code examples that Claude could generate on its own. The 'When to Use This Skill' list, migration strategies overview, and migration timeline are all general knowledge that doesn't need to be spelled out. Much of this is reference material Claude already knows. | 1 / 3 |
Actionability | The code examples are concrete and mostly executable (TypeScript/JavaScript snippets showing before/after patterns), but they're more illustrative than actionable—they show patterns rather than providing a step-by-step process Claude can follow for an actual migration. Key practical details like package installation commands, Angular CLI setup, and configuration files are missing. | 2 / 3 |
Workflow Clarity | The migration timeline at the end lists phases but lacks any validation checkpoints, error recovery steps, or verification between phases. For a destructive/complex operation like framework migration, there are no testing steps, no rollback guidance, and no explicit validation after each migration step. The hybrid setup section jumps straight to code without sequencing the prerequisite steps. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no references to external files and no layered structure. All content—hybrid setup, component migration, service migration, DI changes, routing, forms, and timeline—is dumped into a single file with no navigation aids or separation of concerns. A topic this broad desperately needs content split across focused files. | 1 / 3 |
Total | 5 / 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
34632bc
- 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.