angular-state-management

Implement application state with Angular Signals, computed derivations, and NgRx Signal Store. Use when implementing reactive state with signal(), computed(), effect(), or @ngrx/signals in Angular.

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 tight, well-structured prescriptive skill that delegates detailed code to a real one-level reference and avoids redundant concept explanations. The main improvement is removing the 'Canonical response anchors' duplication and optionally inlining a minimal executable snippet.

Suggestions

Remove or fold the 'Canonical response anchors' section into the existing rules — its two bullets ('Never update signals inside effect()' and 'resets when source changes') already appear in sections 4 and 2, so it is redundant.

Add one short copy-paste signalStore or signal-based-service snippet inline in section 3 or 1 so the body is self-sufficient for the common case without requiring the reference.

Add an explicit immutability/validation checkpoint (e.g. 'after .update(), verify the computed still resolves') to turn the prescriptive rules into a clearer workflow for state migrations.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-point guidance that assumes Angular competence and avoids explaining what signals are, but the 'Canonical response anchors' section duplicates two phrases already stated in the body, a minor instance of over-explanation that could be trimmed.	4 / 5
Actionability	Gives concrete, named APIs to use — 'asReadonly()', 'computed()', 'linkedSignal(() => source())', 'untracked()', 'signalStore with withState/withComputed/withMethods/withEntities()', '.set()'/'.update(v => ...)' — but defers all copy-paste code to the reference file, leaving minor gaps versus fully executable inline examples.	4 / 5
Workflow Clarity	Clear sequenced principles (1. Use Signals → 2. Derive State → 3. Scale with Signal Store → 4. Handle Side Effects) plus an Anti-Patterns section; this is a prescriptive-rules skill with no destructive/batch operation requiring validation, so it is well-organized but lacks an explicit multi-step workflow with checkpoints.	4 / 5
Progressive Disclosure	A concise overview body with a single clearly-signaled one-level-deep reference ([references/signal-store.md](references/signal-store.md), verified to exist) holding the detailed code, with content appropriately split and easy to navigate.	5 / 5
	Total	17 / 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 strong, third-person description that clearly states what the skill does and when to use it with concrete Angular-specific trigger terms. Minor room for more comprehensive action coverage and additional synonyms.

Dimension	Reasoning	Score
Specificity	Names the domain and several concrete actions — 'Angular Signals, computed derivations, and NgRx Signal Store' — covering multiple specific capabilities with only minor gaps, fitting the 'lists several specific actions' anchor rather than the fully comprehensive 5.	4 / 5
Completeness	Explicitly answers both 'what' ('Implement application state with Angular Signals, computed derivations, and NgRx Signal Store') and 'when' ('Use when implementing reactive state with signal(), computed(), effect(), or @ngrx/signals') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger terms users would say — 'reactive state', 'signal()', 'computed()', 'effect()', '@ngrx/signals', 'Angular signals' — giving good keyword coverage, though a few synonyms/file extensions are missing so it does not reach 5.	4 / 5
Distinctiveness Conflict Risk	Scoped to 'Angular' with signal-store-specific triggers ('@ngrx/signals', 'signal()', 'linkedSignal'), giving it a clear niche with minimal overlap risk against other skills.	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
metadata_version	'metadata.version' is missing	Warning
metadata_field	'metadata' should map string keys to string values	Warning

	Total	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: skills/angular/angular-state-management/SKILL.md
Commit: 405cdd5

Reviewed: 4 days 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.