angular-migration
Master AngularJS to Angular migration, including hybrid apps, component conversion, dependency injection changes, and routing migration.
41
41%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/antigravity-awesome-skills-claude/skills/angular-migration/SKILL.mdQuality
Discovery
32%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 identifies a clear domain (AngularJS to Angular migration) and lists relevant sub-topics, but it reads more like a topic list than an actionable skill description. It lacks a 'Use when...' clause, uses an imperative voice ('Master') rather than describing what the skill does, and misses common user trigger terms and phrasings that would help Claude select it appropriately.
Suggestions
Add an explicit 'Use when...' clause, e.g., 'Use when the user asks about upgrading AngularJS 1.x apps to Angular 2+, ngUpgrade, or migrating $scope-based code.'
Replace the imperative 'Master' with concrete action verbs in third person, e.g., 'Guides AngularJS to Angular migration by converting controllers to components, rewriting $scope to TypeScript classes, and configuring ngUpgrade for hybrid apps.'
Include additional natural trigger terms users might say, such as 'upgrade AngularJS', 'ng-upgrade', 'AngularJS 1.x', 'Angular 2+', '$scope migration', and 'angular.module conversion'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (AngularJS to Angular migration) and lists several specific areas (hybrid apps, component conversion, dependency injection changes, routing migration), but these are more like topic areas than concrete actions. It doesn't describe what it actually does (e.g., 'converts AngularJS controllers to Angular components', 'rewrites $scope-based code to use TypeScript classes'). | 2 / 3 |
Completeness | The description addresses 'what' at a high level (migration-related tasks) but completely lacks a 'Use when...' clause or any explicit trigger guidance for when Claude should select this skill. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also somewhat weak, so a score of 1 is appropriate. | 1 / 3 |
Trigger Term Quality | Includes relevant terms like 'AngularJS', 'Angular', 'migration', 'hybrid apps', 'component conversion', 'dependency injection', and 'routing migration'. However, it misses common user phrasings like 'upgrade AngularJS', 'ng-upgrade', 'AngularJS 1.x to Angular 2+', '$scope', 'angular.module', or 'ngUpgrade'. | 2 / 3 |
Distinctiveness Conflict Risk | The AngularJS-to-Angular migration niche is fairly specific and unlikely to conflict with most other skills. However, it could overlap with general Angular development skills or broader JavaScript framework migration skills. The lack of explicit trigger boundaries increases conflict risk slightly. | 2 / 3 |
Total | 7 / 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 code examples covering all major migration scenarios (components, services, DI, routing, forms), making it highly actionable. However, it is excessively verbose—much of the content (migration strategies overview, best practices, common pitfalls, timeline) is generic knowledge that Claude already possesses. The workflow lacks explicit validation checkpoints critical for a complex migration process, and the referenced bundle files don't exist.
Suggestions
Cut the content by 50%+: remove the migration strategies overview, best practices, common pitfalls, and migration timeline sections—these are generic knowledge Claude already has. Focus only on the concrete code patterns.
Add explicit validation checkpoints to the workflow: e.g., 'After hybrid bootstrap setup, verify both frameworks load by checking console for errors' and 'After each component migration, run ng test and verify no regressions'.
Either provide the referenced bundle files (references/hybrid-mode.md, scripts/analyze-angular-app.sh, etc.) or remove the dead references from the Resources section.
Move the extensive before/after code examples into referenced files (e.g., references/component-migration.md) and keep only one representative example inline to demonstrate the pattern.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is extremely verbose at ~300+ lines. It explains basic concepts Claude already knows (what AngularJS directives are, what services are, what routing is). The migration timeline with generic advice ('Install Angular CLI', 'Test thoroughly') and the best practices/common pitfalls sections are padded with obvious guidance that adds no unique value. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples for every migration scenario: hybrid bootstrap, component conversion, service migration, DI downgrade/upgrade, routing, and forms. Before/after patterns are concrete and complete. | 3 / 3 |
Workflow Clarity | The Instructions section lists 4 high-level steps and there's a migration timeline with phases, but there are no explicit validation checkpoints or feedback loops. For a destructive migration process, the lack of 'validate before proceeding' gates and error recovery steps is a significant gap. | 2 / 3 |
Progressive Disclosure | The Resources section references multiple supporting files (references/, assets/, scripts/) suggesting good structure, but no bundle files are actually provided, making these dead references. The main file itself is monolithic with all code examples inline rather than appropriately split into referenced files. | 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
- sickn33/antigravity-awesome-skills
- Commit
22710e9
- 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.