angular-migration

Master AngularJS to Angular migration, including hybrid apps, component conversion, dependency injection changes, and routing migration.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/antigravity-angular-migration/SKILL.md

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.

The skill is highly actionable with concrete before/after code for each migration area, but its workflow lacks explicit validation checkpoints for a destructive cutover and its progressive disclosure is undermined by inlined detail and missing bundle files.

Suggestions

Add explicit validation/feedback-loop steps with concrete commands (e.g. run the test suite, verify the hybrid app boots) before the cutover, and gate the cutover on passing validation.

Move the inlined hybrid-setup, component/DI/routing/forms code into the referenced reference files and actually create those files so the Resources links resolve.

Provide a concrete analysis/validate step using the referenced scripts/analyze-angular-app.sh (and ship that script) so the first workflow step is executable rather than abstract.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean before/after code with little concept padding, but the opening sentence restates the frontmatter description and the large inlined code volume could be trimmed by offloading detail to reference files.	4 / 5
Actionability	It provides copy-paste-ready TypeScript/JavaScript before/after examples covering the common migration cases — hybrid bootstrap, controller/directive-to-component, service, DI, routing, and forms.	5 / 5
Workflow Clarity	The four-step Instructions and Safety section give a rough sequence, but a migration cutover is a destructive operation and validation is only implicit ('Validate with tests') with no concrete validate→fix→retry checkpoint, so it is capped at 3.	3 / 5
Progressive Disclosure	Section headers and a clearly signaled Resources list provide structure, but the detail code that the Resources section promises to live in separate files is inlined in SKILL.md, and none of the referenced reference/asset/script files actually exist on disk.	3 / 5
	Total	15 / 20 Passed

Description

75%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.

The description is specific and occupies a clearly distinct niche, but it omits any explicit 'when to use' trigger guidance, which caps completeness. Adding a 'Use when...' clause with natural trigger phrases would raise the score.

Suggestions

Append an explicit trigger clause such as 'Use when migrating AngularJS (1.x) apps to Angular (2+), running hybrid apps, or converting directives and services.'

Add natural synonyms and version markers users actually say, e.g. 'Angular 2+', 'ngUpgrade', and 'AngularJS 1.x'.

Tie the 'when' directly to user utterances like 'migrate to Angular', 'set up ngUpgrade', or 'convert this directive'.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete migration sub-actions — 'hybrid apps, component conversion, dependency injection changes, and routing migration' — giving comprehensive coverage of the migration domain rather than vague abstraction.	5 / 5
Completeness	It clearly answers the 'what' but contains no 'Use when...' clause or equivalent explicit trigger guidance, so per the judging guideline completeness is capped at 3.	3 / 5
Trigger Term Quality	Natural terms like 'AngularJS to Angular migration', 'hybrid apps', and 'component conversion' are present, but it lacks synonyms and version markers (e.g. '1.x', 'Angular 2+', 'ngUpgrade') that users would also say.	4 / 5
Distinctiveness Conflict Risk	'AngularJS to Angular migration' is a sharply defined niche with distinct triggers and minimal overlap risk with other skills.	5 / 5
	Total	17 / 20 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 7 missing	Warning

	Total	14 / 16 Passed

Repository: boisenoise/skills-collections
Path: skills/antigravity-angular-migration/SKILL.md
Commit: 19c310e

Reviewed: about 17 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.