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.
92
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a strong skill description that clearly defines its scope within Angular's signal-based state management ecosystem. It uses third person voice, lists concrete capabilities, includes an explicit 'Use when' clause with highly specific trigger terms matching actual API names, and occupies a distinct niche that minimizes conflict with other Angular or state management skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'application state with Angular Signals', 'computed derivations', and 'NgRx Signal Store'. These are distinct, concrete capabilities within the Angular state management domain. | 3 / 3 |
Completeness | Clearly answers both 'what' (implement application state with Angular Signals, computed derivations, and NgRx Signal Store) and 'when' (explicit 'Use when' clause with specific trigger terms like signal(), computed(), effect(), @ngrx/signals). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms a developer would use: 'signal()', 'computed()', 'effect()', '@ngrx/signals', 'Angular Signals', 'reactive state', 'Signal Store'. These are the exact API names and concepts developers would mention. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Angular Signals and NgRx Signal Store. The specific API references (signal(), computed(), effect(), @ngrx/signals) make it very unlikely to conflict with general Angular skills or other state management skills (e.g., RxJS-based NgRx). | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise skill that efficiently communicates Angular Signals state management patterns. Its main weakness is the lack of executable code examples — the guidance is specific in naming APIs and patterns but doesn't include any runnable code snippets that demonstrate usage. Adding even brief inline code examples for key patterns (signal creation with asReadonly, computed derivation, effect usage) would elevate the actionability significantly.
Suggestions
Add brief executable code examples for key patterns: e.g., a private signal with asReadonly() exposure, a computed() derivation, and an effect() for localStorage sync.
Include a short code snippet showing the anti-pattern of updating signals inside effect() alongside the correct alternative, to make the warning more actionable.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is purposeful and assumes Claude already understands Angular, Signals, and RxJS concepts. No unnecessary explanations of what signals are or how reactive programming works. | 3 / 3 |
Actionability | Provides specific API guidance (e.g., `asReadonly()`, `computed()`, `linkedSignal()`, `untracked()`, `.set()`, `.update()`) but lacks executable code examples. The instructions are concrete but not copy-paste ready — actual code snippets showing signal creation, computed derivations, or signal store setup would significantly improve actionability. | 2 / 3 |
Workflow Clarity | This is a pattern/convention skill rather than a multi-step process, so workflow clarity is assessed on whether the single-purpose guidance is unambiguous. The numbered sections provide a clear progression from basic signals → derived state → scaling with stores → side effects, with explicit anti-patterns serving as guardrails. | 3 / 3 |
Progressive Disclosure | The SKILL.md is a concise overview that appropriately delegates detailed examples to a single reference file (references/signal-store.md) with clear, well-signaled links. The reference is one level deep and mentioned twice for discoverability. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
81%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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- Reviewed
Table of Contents
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.