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/agentic-awesome-skills

Quality

Content

51%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 body is a well-structured, lean routing layer with excellent progressive disclosure, but it offers almost no executable guidance or sequenced workflow inline, relying entirely on the referenced detailed guide for actionability and workflow steps.

Suggestions

Add a short inline quick-start with one concrete, runnable example (e.g., a minimal standalone Signals component or a build/test command) so the skill is actionable without loading the full guide.

Include an inline high-level workflow sequence with an explicit validation checkpoint (e.g., "1. Assess version, 2. Apply patterns, 3. `ng build` + run tests, 4. Proceed only if passing") rather than deferring all steps to the guide.

Tighten the promotional opening and replace vague phrases ("latest reactive patterns", "best practices") with specific, concrete guidance.

Dimension	Reasoning	Score
Conciseness	The body is lean and avoids explaining basic Angular concepts, but the opening tagline ("Master modern Angular development with...") and phrases like "the latest reactive patterns" / "best practices" add minor promotional padding.	4 / 5
Actionability	The body provides concrete routing guidance (When to Use, Do Not Use with specific alternative skill names, Safety) but contains no inline code, commands, or executable steps for performing Angular work, delegating all execution detail to the external guide.	2 / 5
Workflow Clarity	No inline sequenced workflow is present; the body points to the detailed guide for the procedure and only generally emphasizes that validation requirements are "mandatory", leaving checkpoints implicit and undefined in the overview.	2 / 5
Progressive Disclosure	A clean, thin overview points to a single well-signaled, one-level-deep reference ("references/detailed-guide.md", verified to exist) with easy navigation and content appropriately split between overview and detail.	5 / 5
	Total	13 / 20 Passed

Description

66%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 names a specific, modern Angular niche with strong trigger terms, but is framed as a persona claim rather than a list of concrete actions and entirely lacks an explicit "Use when..." trigger clause.

Suggestions

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

Reframe the expertise areas as concrete actions (e.g., "Implements Signals-based state, migrates NgModules to Standalone, configures Zoneless apps, adds SSR/hydration") to lift specificity.

Include a few natural synonyms/variations users might say (e.g., "Angular signals", "standalone components", "change detection") to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete capability areas ("Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns") with a version pin (v20+), but frames them as "deep knowledge of" expertise rather than concrete actions the skill performs.	4 / 5
Completeness	The "what" is clear (modern Angular v20+ expertise across named areas) but there is no "Use when..." clause or equivalent trigger guidance, which the rubric caps at 3.	3 / 5
Trigger Term Quality	Includes strong Angular-specific keywords a user would naturally say ("Signals", "Standalone Components", "Zoneless", "SSR/Hydration"), though synonyms and variations beyond the canonical terms are absent.	4 / 5
Distinctiveness Conflict Risk	The v20+ version pin plus the specific modern feature set carves a clear niche with only minor overlap risk against closely related general frontend or TypeScript skills.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: boisenoise/skills-collections
Path: skills/antigravity-angular/SKILL.md
Commit: 652629d

Reviewed: ~14 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.