Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates. Use when upgrading AngularJS applications, planning framework migrations, or ...
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill angular-migration88
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 migration scenario (AngularJS to Angular), lists concrete techniques, and provides explicit trigger conditions. The description uses proper third-person voice and includes natural keywords developers would use. The truncation ('or ...') is the only minor issue, but the visible content is well-structured.
| 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 using hybrid mode, component rewriting, DI updates) AND when (upgrading AngularJS applications, planning framework migrations). Has explicit 'Use when...' clause with trigger scenarios. | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'AngularJS', 'Angular', 'upgrading', 'framework migrations'. These are terms developers naturally use when discussing this migration scenario. | 3 / 3 |
Distinctiveness Conflict Risk | Very specific niche targeting AngularJS-to-Angular migration specifically. Unlikely to conflict with general JavaScript, other framework, or generic migration skills due to explicit framework naming. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid migration skill with excellent actionable code examples covering all major migration scenarios. The main weaknesses are some verbosity in meta-sections and missing explicit validation checkpoints in the workflow for what is inherently a risky, multi-step migration process.
Suggestions
Add explicit validation checkpoints to the Instructions section, e.g., 'Run tests after each component migration before proceeding' with specific commands
Remove or condense the 'Use this skill when' and 'Do not use this skill when' sections - Claude can infer appropriate usage from the content
Trim 'Best Practices' and 'Common Pitfalls' to only non-obvious, Angular-migration-specific guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is reasonably efficient but includes some unnecessary content like the 'Use this skill when' and 'Do not use this skill when' sections that Claude can infer, and the 'Best Practices' and 'Common Pitfalls' sections contain generic advice Claude already knows. | 2 / 3 |
Actionability | Excellent executable code examples throughout - hybrid app setup, component migration before/after, service migration, DI changes, routing, and forms all have complete, copy-paste ready TypeScript/JavaScript code with clear patterns. | 3 / 3 |
Workflow Clarity | The 4-step instructions and migration timeline provide sequence, but lack explicit validation checkpoints. For a migration involving destructive changes, there should be explicit 'validate before proceeding' steps rather than just 'Validate with tests' as a final step. | 2 / 3 |
Progressive Disclosure | Well-structured with clear sections, appropriate inline content for the overview, and explicit references to external files (references/hybrid-mode.md, scripts/analyze-angular-app.sh, etc.) that are one level deep and clearly signaled. | 3 / 3 |
Total | 10 / 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 | |
Table of Contents
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.