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.
53
Quality
42%
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
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
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 serves primarily as a navigation hub to sub-skills, which is appropriate for progressive disclosure. However, the main content lacks actionable guidance—no code examples, specific commands, or concrete migration steps. The instructions are too abstract to be useful without consulting the sub-skills.
Suggestions
Add at least one concrete code example showing ngUpgrade bootstrap setup or a simple component conversion pattern
Replace abstract instructions ('Assess the codebase') with specific commands or checklists (e.g., 'Run `ng update` to check compatibility, review package.json for AngularJS dependencies')
Add a validation checkpoint in the workflow, such as 'Run hybrid app tests before proceeding to next module migration'
| 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 section is 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. For a migration involving destructive changes, the absence of explicit validation steps is a gap. | 2 / 3 |
Progressive Disclosure | Clear overview structure with well-organized one-level-deep references to sub-skills. The navigation to detailed materials (7 sub-skill files) is clearly signaled and appropriately split. | 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
3395991
- 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.