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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-organized, token-efficient overview that defers executable examples to a real one-level-deep reference. Weakest on actionability and workflow clarity, since the body lacks inline copy-paste code and explicit decision criteria for choosing between patterns.

Suggestions

Add one minimal inline executable snippet (e.g., a signal + computed service example) so the body is copy-paste ready without opening the reference.

Make escalation criteria explicit: state when to move from raw signals to @ngrx Signal Store and when to choose linkedSignal() over computed().

Include a one-line verification cue (e.g., confirm derivations stay pure / no signal writes inside effect()) so the side-effects guidance has a concrete check step.

Dimension	Reasoning	Score
Conciseness	Lean bullet-point guidance that assumes Angular competence — it never explains what signals or Angular are. Every line directs an action, matching the 'lean and efficient; every token earns its place' anchor.	3 / 3
Actionability	Concrete API names are cited ('linkedSignal(() => source())', 'withState, withComputed, withMethods, withEntities()'), but the body contains no complete inline executable code block — copy-paste examples live only in the reference file. It is above a 1 because the guidance is specific, but not a 3 because nothing in the body is copy-paste ready.	2 / 3
Workflow Clarity	Sections are numbered and prioritized (P1 HIGH), giving a usable sequence of concerns, but decision criteria are thin — 'For complex features' is the only cue for escalating to Signal Store, and linkedSignal-vs-computed selection is left implicit. No validation checkpoints are needed (no destructive ops), but the lack of explicit branching keeps it at 2.	2 / 3
Progressive Disclosure	SKILL.md is a concise overview that points to references/signal-store.md one level deep, the referenced file exists and holds the detailed code, and a dedicated References section signals navigation. Content is appropriately split between overview and reference, matching the top anchor.	3 / 3
	Total	10 / 12 Passed

Description

100%

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 tight, well-targeted description: concrete capabilities, explicit 'Use when' triggers, natural keywords, and a distinct Angular-signals niche. Third-person voice is maintained throughout.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — 'Angular Signals, computed derivations, and NgRx Signal Store' — rather than vague language. It names the exact mechanisms, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Clearly states 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 in Angular'), with an explicit trigger clause. It is not a 2 because the 'when' is explicit, not merely implied.	3 / 3
Trigger Term Quality	The 'Use when' clause surfaces natural terms a developer would say: 'signal()', 'computed()', 'effect()', '@ngrx/signals', 'reactive state', and 'Angular'. Coverage of common variations is good, fitting the top anchor.	3 / 3
Distinctiveness Conflict Risk	Scoped to Angular reactive state with distinct API triggers, a clear niche unlikely to fire for unrelated skills. Voice is third person ('Implement…'), so no specificity penalty applies.	3 / 3
	Total	12 / 12 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
Commit: 611f52a

Reviewed: 1 day 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.