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.
83
77%
Does it follow best practices?
Impact
99%
1.50xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/antigravity-angular-state-management/SKILL.mdQuality
Discovery
89%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 capabilities could be more concrete — listing specific actions rather than broad categories would strengthen the specificity dimension. Also, 'Master' as the opening verb reads slightly like marketing copy rather than a functional description.
Suggestions
Replace 'Master modern Angular state management' with more concrete actions like 'Implements signal-based stores, configures NgRx feature states, converts BehaviorSubjects to Signals' to improve specificity.
Consider adding file type or pattern triggers like 'store.ts', 'effects.ts', or '.store.ts' to further aid skill selection in code-heavy contexts.
| 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 |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive and highly actionable Angular state management reference with excellent, executable code examples covering the full spectrum from Signals to NgRx. However, it suffers from being overly long for a SKILL.md file—much of the content (NgRx full setup, ComponentStore, migration patterns) should be split into referenced sub-files. It also lacks workflow clarity for multi-step setup processes and includes some unnecessary explanatory content that Claude already knows.
Suggestions
Split the monolithic content into sub-files (e.g., NGRX_STORE.md, SIGNAL_PATTERNS.md, MIGRATION.md) and keep SKILL.md as a concise overview with links to each
Add explicit step-by-step setup workflows with validation checkpoints, especially for NgRx Store setup (e.g., 'verify store is connected via DevTools before adding effects')
Remove the 'Core Concepts' state categories table and selection criteria text block—these are general knowledge that Claude can infer; replace with a brief decision tree if needed
Trim the Do's/Don'ts tables which largely restate obvious Angular best practices
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is quite lengthy (~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 already understands. 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. Every pattern includes complete, runnable code with component usage. | 3 / 3 |
Workflow Clarity | The skill presents patterns clearly but lacks explicit workflow sequencing for multi-step processes like setting up NgRx (setup is shown but no step-by-step validation). The migration section shows before/after but no verification steps. There are no validation checkpoints for state management setup or debugging guidance beyond listing it as a use case. | 2 / 3 |
Progressive Disclosure | The content is a monolithic document with all patterns inline rather than split into separate files. For a skill this large, the NgRx Store section, RxJS patterns, and migration guides could be referenced as separate files. The Resources section at the end links to external docs but internal progressive disclosure is absent. | 2 / 3 |
Total | 9 / 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 |
|---|---|---|
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
- boisenoise/skills-collections
- Commit
636b862
- 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.