angular

Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns.

Quality

58%

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/SKILL.md

The canonical home for this skill is angular in sickn33/antigravity-awesome-skills

Quality

Content

46%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 content is technically rich and mostly actionable with solid executable code, but it is a long monolithic document that over-explains familiar concepts and lacks both progressive disclosure into bundle files and explicit validation checkpoints in its workflow.

Suggestions

Move the numbered topical deep-dives (e.g. SSR/hydration, forms, performance, testing) into separate reference files in ./references/ and keep SKILL.md as a concise overview with one-level-deep links.

Tighten or remove explanations of concepts Claude already knows (e.g. what standalone components are, what zone.js does) and trim inline code comments that restate the obvious.

Add explicit validation checkpoints to the Instructions workflow (e.g. 'run ng build', 'run ng test', 'verify hydration with no console mismatch errors') with a fix-and-retry loop for migration steps.

Dimension	Reasoning	Score
Conciseness	At ~800 lines the body extensively restates concepts Claude already knows and pads each section with boilerplate explanations and comments; while accurate, it is noticeably verbose relative to a lean reference.	2 / 5
Actionability	Most sections provide complete, copy-paste-ready TypeScript examples with real imports and runnable patterns, with only minor gaps such as elided class bodies ('export class TooltipDirective { ... }').	4 / 5
Workflow Clarity	A short 'Instructions' sequence exists (assess, apply, implement, validate) but checkpoints are implicit and the only validation step ('Validate with build and tests') is vague for operations that include migrations and SSR changes.	3 / 5
Progressive Disclosure	The skill is a monolithic single-file wall of content with no bundle files; large reference-grade material (11 numbered topical sections, multiple API tables) that clearly belongs in separate referenced files is inlined rather than split out.	2 / 5
	Total	11 / 20 Passed

Description

70%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 well-scoped to modern Angular, with strong distinctiveness and decent trigger terms. Its main weakness is the absence of an explicit 'Use when...' clause, which leaves the activation criteria implicit.

Suggestions

Add an explicit trigger clause, e.g. 'Use when building or modernizing Angular v20+ apps with Signals, Standalone Components, Zoneless change detection, or SSR/hydration.'

Convert topic-area nouns into concrete actions (e.g. 'implement Signal-based state', 'configure Zoneless change detection') to lift specificity from topic listing to actionable verbs.

Include common user phrasings and synonyms such as 'change detection', 'NgModules migration', or '.ts Angular templates' to broaden natural trigger coverage.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete capabilities ('Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns'), but these are topic areas rather than executable actions, leaving minor coverage gaps.	4 / 5
Completeness	It clearly states the 'what' (Angular v20+ expertise across named areas) but has no 'Use when...' clause or equivalent explicit trigger guidance for when Claude should invoke it, which caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural terms users say ('Angular', 'Signals', 'SSR', 'Standalone Components'), with good coverage of common variations, though it omits file extensions and some synonyms like 'change detection'.	4 / 5
Distinctiveness Conflict Risk	Scoped tightly to modern Angular v20+ with specific sub-features, and the body points legacy cases to other skills, giving it a clear niche with minimal conflict risk.	5 / 5
	Total	16 / 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
skill_md_line_count	SKILL.md is long (824 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: boisenoise/skills-collections
Path: skills/antigravity-angular/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.