angular-migration
Master AngularJS to Angular migration, including hybrid apps, component conversion, dependency injection changes, and routing migration.
66
58%
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 ./skills/antigravity-angular-migration/SKILL.mdQuality
Discovery
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 effectively communicates specific migration capabilities in a well-defined niche (AngularJS to Angular), listing concrete tasks like component conversion and routing migration. Its main weaknesses are the lack of an explicit 'Use when...' trigger clause and missing some natural user terms like 'upgrade' or 'ng-upgrade'. The word 'Master' at the beginning is slightly informal but the rest uses appropriate third-person imperative voice.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about upgrading or migrating an AngularJS (1.x) application to modern Angular.'
Include additional natural trigger terms users might say, such as 'upgrade', 'ng-upgrade', 'AngularJS 1.x', 'Angular 2+', or 'legacy Angular'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: hybrid apps, component conversion, dependency injection changes, and routing migration. These are distinct, identifiable migration tasks. | 3 / 3 |
Completeness | Clearly answers 'what' (migration tasks including hybrid apps, component conversion, DI changes, routing migration) but lacks an explicit 'Use when...' clause specifying when Claude should select this skill. | 2 / 3 |
Trigger Term Quality | Includes good terms like 'AngularJS', 'Angular', 'migration', 'hybrid apps', 'component conversion', but misses common user phrases like 'upgrade', 'ng-upgrade', 'AngularJS to Angular 2+', or file extensions. Users might say 'upgrade my AngularJS app' rather than 'migrate'. | 2 / 3 |
Distinctiveness Conflict Risk | Very specific niche: AngularJS-to-Angular migration is a distinct domain unlikely to conflict with general Angular development skills or other framework migration skills. The combination of 'AngularJS to Angular' clearly delineates the scope. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent concrete, executable code examples covering all major migration scenarios, but is far too verbose for a SKILL.md file—most of the before/after code patterns are things Claude can generate without instruction. The workflow lacks explicit validation checkpoints critical for a complex migration process, and the bulk of the content should be moved to referenced files rather than inlined.
Suggestions
Drastically reduce inline code examples to 1-2 key patterns (e.g., hybrid bootstrap setup and one component migration), moving the rest to referenced files like references/component-migration.md
Remove generic advice sections (Best Practices, Common Pitfalls, 'Use this skill when') that Claude already knows or can infer
Add explicit validation checkpoints to the workflow: e.g., 'After hybrid bootstrap, verify both frameworks load by checking console for errors' and 'Run ng test + karma after each component migration'
Trim the Migration Strategies section to a decision table rather than prose descriptions
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines, with extensive before/after code examples that Claude could generate on its own. Sections like 'Use this skill when', 'Do not use this skill when', migration strategies descriptions, and the migration timeline are largely unnecessary padding. The best practices and common pitfalls sections are generic advice Claude already knows. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready. Before/after patterns for controllers, directives, services, routing, forms, and DI are all fully executable TypeScript/JavaScript with clear transformations shown. | 3 / 3 |
Workflow Clarity | The Instructions section provides a 4-step high-level workflow and the Migration Timeline gives phases, but there are no explicit validation checkpoints or feedback loops. For a migration involving destructive changes and hybrid app complexity, the lack of verification steps (e.g., 'run tests after each component migration', 'validate hybrid bootstrap before proceeding') is a gap. | 2 / 3 |
Progressive Disclosure | The Resources section references external files (references/, assets/, scripts/) which is good progressive disclosure, but the main file itself is monolithic with extensive inline code that could be split into referenced files. The component migration, service migration, forms migration, and DI sections could each be separate reference documents with only summaries in the main skill. | 2 / 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
- boisenoise/skills-collections
- Commit
636b862
- 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.