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

73%

Does it follow best practices?

Impact

99%

1.50x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/angular-state-management/SKILL.md

Quality

Content

57%Scale 1-3

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

The skill excels at actionability with comprehensive, executable code examples covering the full spectrum of Angular state management patterns. However, it suffers from being a monolithic document that tries to cover too much in one file—Signal services, NgRx global store, ComponentStore, server state, and migration patterns all inline. The content would benefit significantly from splitting into focused sub-files with a concise overview in the main SKILL.md.

Suggestions

Split into separate files (e.g., SIGNALS.md, NGRX-STORE.md, COMPONENT-STORE.md, MIGRATION.md) and keep SKILL.md as a concise overview with the selection criteria and links to each pattern file.

Remove the 'Core Concepts' state categories table and selection criteria prose—replace with a brief decision tree or keep only the selection criteria block.

Add explicit workflow steps for setting up NgRx in a new project (install, configure, create feature slice, verify with devtools) with validation checkpoints.

Remove the 'When to Use / Do Not Use' sections and the Do's/Don'ts tables, which mostly restate things Claude already knows about Angular development.

Dimension	Reasoning	Score
Conciseness	The skill is quite long (~400+ lines) with extensive code examples that are mostly useful, but includes some unnecessary elements like the 'Core Concepts' state categories table and selection criteria that Claude likely already knows. The 'When to Use' and 'Do Not Use' sections add little value. The Do's/Don'ts tables restate common knowledge.	2 / 3
Actionability	Excellent actionability with fully executable, copy-paste ready TypeScript code examples covering Signal services, NgRx SignalStore, NgRx global store (actions, reducers, selectors, effects), ComponentStore, HTTP+Signals patterns, optimistic updates, and migration examples. Each pattern is complete and usable.	3 / 3
Workflow Clarity	The skill presents patterns well but lacks explicit workflow sequencing for multi-step processes like setting up NgRx (setup is shown but no validation steps). The migration section shows before/after but no step-by-step migration workflow with checkpoints. The selection criteria is a simple text block rather than a decision workflow.	2 / 3
Progressive Disclosure	This is a monolithic wall of content with no references to separate files for detailed patterns. The NgRx section alone could be its own file. All patterns (Signals, NgRx Store, ComponentStore, Server State, Migration) are inlined, making this very long. External links at the bottom are to third-party docs, not organized companion files.	1 / 3
	Total	8 / 12 Passed

Description

89%Scale 1-3

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies its domain (Angular state management) and provides explicit trigger guidance via a 'Use when' clause. The trigger terms are well-chosen and cover the main technologies and scenarios. The main weakness is that the capability descriptions lean slightly toward categories of work rather than listing specific concrete actions the skill enables.

Suggestions

Replace 'Master modern Angular state management' with more specific concrete actions, e.g., 'Creates signal-based stores, configures NgRx feature states, implements RxJS-based reactive patterns, and converts legacy state patterns to modern Angular Signals.'

Dimension	Reasoning	Score
Specificity	Names the domain (Angular state management) and mentions specific technologies (Signals, NgRx, RxJS), but the actions are somewhat vague — 'setting up global state', 'managing component stores', 'choosing between state solutions', and 'migrating from legacy patterns' are more categories of work than concrete actions like 'create a signal-based store' or 'convert BehaviorSubject to Signal'.	2 / 3
Completeness	Clearly answers both 'what' (master modern Angular state management with Signals, NgRx, and RxJS) and 'when' (explicit 'Use when' clause covering setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns).	3 / 3
Trigger Term Quality	Includes strong natural keywords users would say: 'Angular', 'Signals', 'NgRx', 'RxJS', 'global state', 'component stores', 'state management', and 'migrating from legacy patterns'. These cover the main terms a developer would use when seeking help with Angular state management.	3 / 3
Distinctiveness Conflict Risk	The combination of Angular-specific state management technologies (Signals, NgRx, RxJS) creates a clear niche that is unlikely to conflict with general frontend skills, React state management skills, or other Angular skills focused on routing/forms/etc.	3 / 3
	Total	11 / 12 Passed

Validation

81%

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 — 9 / 11 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	9 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/angular-state-management/SKILL.md
Commit: fbdfd63

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