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.
76
71%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./.agent/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 well-crafted skill description that excels across all dimensions. It uses third person voice, lists specific migration techniques, includes natural trigger terms developers would use, and has an explicit 'Use when...' clause. The focus on AngularJS-to-Angular migration creates a clear, distinct niche.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'hybrid mode', 'incremental component rewriting', and 'dependency injection updates' - these are concrete migration techniques rather than vague language. | 3 / 3 |
Completeness | Clearly answers both what (migrate using hybrid mode, incremental component rewriting, dependency injection updates) AND when (explicit 'Use when...' clause covering upgrading AngularJS, planning migrations, modernizing legacy code). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'AngularJS', 'Angular', 'upgrading', 'framework migrations', 'modernizing', 'legacy Angular code' - good coverage of terms developers would use when seeking migration help. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting AngularJS-to-Angular migration specifically; unlikely to conflict with general coding skills or other framework migration skills due to explicit framework naming. | 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.
This skill has good structural organization with clear progressive disclosure to sub-skills, but the main content lacks actionable guidance. The instructions are too abstract without concrete code examples, specific commands, or ngUpgrade setup snippets. For a complex migration process, the workflow needs explicit validation checkpoints and feedback loops.
Suggestions
Add concrete ngUpgrade setup code in the Instructions section showing how to bootstrap a hybrid app
Include a specific validation checklist or command (e.g., 'Run ng build --configuration=hybrid && npm test') after each migration step
Replace abstract instructions like 'Assess the AngularJS codebase' with specific commands or checklists (e.g., 'Run npx ngcc to check compatibility')
Remove the 'Use this skill when' and 'Do not use this skill when' sections as they add little value for Claude
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes some unnecessary sections like 'Use this skill when' and 'Do not use this skill when' which explain obvious context Claude can infer. The instructions are appropriately terse. | 2 / 3 |
Actionability | The instructions are vague and abstract ('Assess the codebase', 'Choose a migration strategy') with no concrete code, commands, or executable examples. It describes what to do rather than showing how to do it. | 1 / 3 |
Workflow Clarity | Steps are listed in sequence (1-4) but lack validation checkpoints, specific commands, or feedback loops. The 'Validate with tests' step is too vague for a complex migration process that involves destructive changes. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-organized one-level-deep references to sub-skills. The knowledge modules are clearly signaled and appropriately split into separate files for detailed content. | 3 / 3 |
Total | 8 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- Dokhacgiakhoa/antigravity-ide
- Commit
332e58b
- 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.