angular-state-management

Master modern Angular state management with Signals, NgRx, and RxJS. Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns.

Quality

83%

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

Quality

Content

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

A dense, highly actionable reference with comprehensive executable TypeScript patterns and a clear organizational sequence. Its main weakness is progressive disclosure: everything lives in one ~630-line file with no references to split-out detail files.

Suggestions

Split large walkthroughs (NgRx feature slice, SignalStore, migration paths) into separate reference files under references/ and link to them from SKILL.md to improve progressive disclosure and reduce context-token cost.

Add explicit validation/checkpoint guidance to the state-mutating patterns rather than bare `catch {}` blocks, so error-recovery feedback loops are visible alongside the existing optimistic-update rollback.

Trim inline component templates and boilerplate (e.g., full @Component decorators with HTML) from the core pattern examples, keeping only the state logic that earns its place.

Dimension	Reasoning	Score
Conciseness	Prose is lean and avoids explaining concepts Claude already knows, but the ~630-line body inlines multiple complete stores with full component templates and boilerplate that could be trimmed; it sits above the efficient-but-slightly-padded midpoint toward lean.	4 / 5
Actionability	Extensive copy-paste-ready, fully executable TypeScript covering local/shared/global/server state patterns plus migration and RxJS-Signal bridging, with complete imports and real Angular APIs across the common cases.	5 / 5
Workflow Clarity	Clear logical sequence (categories -> selection criteria -> patterns -> best practices -> migration) with scoping sections and an explicit rollback feedback loop on the destructive optimistic-update case, though most patterns use implicit `catch {}` handling without explicit validation checkpoints.	4 / 5
Progressive Disclosure	Well-organized with clear section headers and tables, but the monolithic single-file body inlines substantial blocks (NgRx feature-slice walkthrough, SignalStore, migration) that belong in separate reference files, and no bundle files or internal file references exist.	3 / 5
	Total	16 / 20 Passed

Description

87%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 well-crafted description that clearly states both capability and explicit 'Use when' trigger conditions with concrete framework-specific terms. The only soft spot is that the verbs describe scenario areas rather than enumerating many discrete concrete actions.

Dimension	Reasoning	Score
Specificity	Names the domain ('Angular state management') and concrete technologies (Signals, NgRx, RxJS) plus four use-case scenarios, but the verbs ('Master', 'setting up', 'managing') are somewhat higher-level than enumerating discrete concrete actions, sitting between the 1-2-action anchor and the multi-action comprehensive anchor.	4 / 5
Completeness	Explicitly answers both 'what' (master Angular state management with Signals/NgRx/RxJS) and 'when' with a concrete four-part trigger clause ('Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns').	5 / 5
Trigger Term Quality	Good keyword coverage with framework-specific natural phrases users would say ('setting up global state', 'managing component stores', 'migrating from legacy patterns'), though a few natural synonyms (Akita, BehaviorSubject) are absent.	4 / 5
Distinctiveness Conflict Risk	Angular-specific state management with named libraries forms a clear niche with distinct triggers and minimal conflict risk; the body even explicitly redirects React state work to a separate skill.	5 / 5
	Total	18 / 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 (641 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: sickn33/antigravity-awesome-skills
Path: skills/angular-state-management/SKILL.md
Commit: 1f67c44

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