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.

1.50x

Quality

85%

Does it follow best practices?

Impact

99%

1.50x

Average score across 3 eval scenarios

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.

The body is highly actionable with comprehensive executable examples and clear decision guidance, but it is a monolithic single-file skill with bulk reference content inlined rather than split into one-level-deep reference files.

Suggestions

Move the full NgRx slice boilerplate (actions/reducer/selectors/effects) and the larger store implementations into reference files under ./references/, keeping SKILL.md as a concise overview with signaled links.

Trim the introductory and best-practice prose ('Comprehensive guide to...', rationale columns) to assume Claude's familiarity and reduce token weight.

Add a short numbered quick-start workflow at the top (pick category → choose solution → apply pattern) so the selection criteria become an explicit sequence.

Dimension	Reasoning	Score
Conciseness	Mostly efficient and code-forward with tight tables and minimal prose padding, though the ~630-line body retains some explanatory scaffolding ('Comprehensive guide to...', inline comments) that could be trimmed.	4 / 5
Actionability	Provides fully executable, copy-paste-ready TypeScript across signal services, feature stores, SignalStore, full NgRx slices, component stores, HTTP+signals, and migration examples covering the common cases.	5 / 5
Workflow Clarity	A decision-criteria block sequences solution choice by app size, and patterns progress from simple to complex; as a pattern catalog rather than a destructive workflow it needs no validation checkpoints, but lacks an explicit end-to-end procedure.	4 / 5
Progressive Disclosure	No bundle files exist and all material is inlined in one large file; section headers give some structure, but substantial reference-grade boilerplate (full NgRx slice, multiple complete stores) that would benefit from separate reference files remains inline.	3 / 5
	Total	16 / 20 Passed

Description

92%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, complete, and well-triggered, clearly scoping an Angular state-management skill with both what-it-does and when-to-use guidance. Minor room for additional natural synonyms in the trigger terms.

Dimension	Reasoning	Score
Specificity	Names the domain and multiple concrete capabilities — 'setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns' — alongside specific technologies (Signals, NgRx, RxJS), giving comprehensive coverage.	5 / 5
Completeness	Clearly states what ('Master modern Angular state management with Signals, NgRx, and RxJS') and an explicit 'Use when...' clause with concrete trigger phrases, satisfying both requirements.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('setting up global state', 'component stores', 'migrating from legacy patterns') and the named solutions, but lacks common synonyms or broader variations a user might voice.	4 / 5
Distinctiveness Conflict Risk	Anchored to a clear Angular state-management niche with named libraries and an explicit redirect away from React (in the body), giving minimal conflict risk with unrelated skills.	5 / 5
	Total	19 / 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 (636 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills-claude/skills/angular-state-management/SKILL.md
Commit: 57c135b

Reviewed: 5 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.