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.

1.06x

Quality

78%

Does it follow best practices?

Impact

100%

1.06x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./tests/ext_conformance/artifacts/agents-wshobson/framework-migration/skills/angular-migration/SKILL.md

The canonical home for this skill is angular-migration in wshobson/agents

Quality

Content

72%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

Highly actionable with comprehensive executable code examples, but the migration workflow lacks explicit validation checkpoints for a destructive operation, and the progressive-disclosure structure is undermined by missing referenced bundle files and inlined detail that should live in those references.

Suggestions

Add explicit validation checkpoints to the Migration Timeline (e.g., 'Validate hybrid app boots before migrating any component', 'Run the AngularJS test suite after each feature migration; fix and re-run before proceeding') so the destructive migration workflow earns a higher workflow_clarity score.

Create the referenced bundle files (references/hybrid-mode.md, component-migration.md, dependency-injection.md, routing.md; assets/hybrid-bootstrap.ts, migration-timeline.md; scripts/analyze-angular-app.sh) or remove the Resources list, so navigation is not broken.

Move the detailed component/service/DI/routing/forms migration code into those reference files and keep SKILL.md as a concise overview pointing to them, reducing duplication between the inline examples and the listed references.

Dimension	Reasoning	Score
Conciseness	The body is code-heavy and largely assumes Angular competence, but the 'When to Use This Skill' list duplicates the frontmatter and the generic 'Best Practices'/'Common Pitfalls' bullets add padding Claude already knows; not a 5 because of that trimmable material.	4 / 5
Actionability	Provides copy-paste-ready TypeScript/JavaScript covering hybrid bootstrap, component/service/DI/routing/forms migration across before/after pairs, with the common cases explicitly addressed.	5 / 5
Workflow Clarity	The Migration Timeline gives a phased Phase 1-4 sequence, but migration is a destructive/batch operation and there are no explicit validate-then-proceed checkpoints or fix-retry loops ('Test thoroughly', 'Final testing' are implicit); the destructive-operation cap locks this at 3.	3 / 5
Progressive Disclosure	Section headers and a Resources list give some structure, but the referenced bundle files (references/.md, assets/, scripts/*) do not exist on disk, and detailed component/service/DI/routing/forms content that the Resources section implies belongs in separate files is inlined in SKILL.md.	3 / 5
	Total	15 / 20 Passed

Description

83%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, concrete description that clearly states both capability and trigger conditions in third person. Minor gaps in action coverage and slight overlap risk with broader migration skills keep specificity and distinctiveness at 4 rather than 5.

Dimension	Reasoning	Score
Specificity	Names the domain and three concrete actions ('hybrid mode', 'incremental component rewriting', 'dependency injection updates'); not a 5 because routing/forms migration are absent from the description.	4 / 5
Completeness	Explicitly answers both what ('Migrate from AngularJS to Angular using...') and when ('Use when upgrading AngularJS applications, planning framework migrations, or modernizing legacy Angular code') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural terms like 'upgrading AngularJS applications', 'framework migrations', and 'modernizing legacy Angular code' map to what users would say; not a 5 because no version synonyms or file/extension variants are present.	4 / 5
Distinctiveness Conflict Risk	The AngularJS-to-Angular niche is clear and distinct, but 'planning framework migrations' and 'modernizing legacy Angular code' leave minor overlap risk with general modernization skills.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	15 / 16 Passed

Repository: Dicklesworthstone/pi_agent_rust
Path: tests/ext_conformance/artifacts/agents-wshobson/framework-migration/skills/angular-migration/SKILL.md
Commit: 6453c0b

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.