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.
80
75%
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 ./tests/ext_conformance/artifacts/agents-wshobson/framework-migration/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 strong skill description that clearly identifies a specific migration domain (AngularJS to Angular), lists concrete techniques involved, and provides explicit 'Use when' triggers with natural language terms users would employ. It follows third-person voice and is concise without unnecessary padding.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'hybrid mode', 'incremental component rewriting', and 'dependency injection updates' are all concrete migration techniques, not vague abstractions. | 3 / 3 |
Completeness | Clearly answers both what ('Migrate from AngularJS to Angular using hybrid mode, incremental component rewriting, and dependency injection updates') and when ('Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'AngularJS', 'Angular', 'migrate', 'upgrading', 'framework migrations', 'modernizing', 'legacy Angular code'. These cover common variations of how users would describe this need. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche — specifically targets AngularJS-to-Angular migration, which is a very specific domain unlikely to conflict with general coding skills or other framework-related skills. The mention of 'hybrid mode' and 'AngularJS' creates a clear, narrow trigger. | 3 / 3 |
Total | 12 / 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.
This skill provides comprehensive, executable migration examples but is far too verbose for a SKILL.md — most of the content is standard Angular knowledge that Claude already knows. The inline code examples should be moved to the referenced files, with the main skill serving as a concise overview with navigation. The workflow lacks explicit validation checkpoints critical for a migration process.
Suggestions
Move the detailed before/after code examples into the referenced files (e.g., references/component-migration.md) and keep only a single concise example in SKILL.md as a quick reference.
Add explicit validation checkpoints to the migration workflow (e.g., 'Run ng build after each component migration', 'Verify hybrid bootstrap loads both frameworks before proceeding').
Remove the 'When to Use This Skill' list, migration strategies overview, best practices, and common pitfalls — these are generic knowledge Claude already has. Focus on project-specific patterns and gotchas.
Trim the SKILL.md to under 80 lines: a brief overview, one representative code example, and well-signaled links to the reference files for each migration topic.
| 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. The migration strategies section, timeline, best practices, and common pitfalls are all generic knowledge Claude already possesses. Most of the code examples are standard Angular patterns that don't need to be spelled out in full. | 1 / 3 |
Actionability | The code examples are fully executable and concrete — hybrid bootstrap setup, component migration, service migration, DI downgrade/upgrade, routing, and forms all have complete, copy-paste-ready TypeScript/JavaScript. The before/after pattern makes conversions very clear. | 3 / 3 |
Workflow Clarity | The migration timeline provides a phased sequence, and the strategies section outlines approaches, but there are no explicit validation checkpoints or feedback loops. For a migration involving destructive changes to a codebase, there should be verification steps (e.g., 'run tests after each component migration', 'validate hybrid bootstrap before proceeding'). | 2 / 3 |
Progressive Disclosure | The Resources section references external files (references/, assets/, scripts/) which is good progressive disclosure, but the main file itself contains massive inline code blocks that should be in those referenced files instead. The SKILL.md should be a concise overview pointing to the detailed migration guides, not contain all the code inline. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- Dicklesworthstone/pi_agent_rust
- Commit
47823e3
- 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.