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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill angular-state-management80
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 with excellent trigger terms and completeness. The explicit 'Use when' clause covers multiple relevant scenarios. The main weakness is the vague action verb 'Master' instead of concrete actions like 'configure', 'implement', or 'migrate'.
Suggestions
Replace 'Master' with specific concrete actions like 'Configure NgRx stores, implement Signals for reactive state, create RxJS-based effects'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular state management) and mentions specific technologies (Signals, NgRx, RxJS), but uses vague action verb 'Master' rather than listing concrete actions like 'configure stores', 'implement selectors', or 'create effects'. | 2 / 3 |
Completeness | Clearly answers both what (Angular state management with Signals, NgRx, RxJS) and when (explicit 'Use when' clause covering setup, management, choosing solutions, and migration scenarios). | 3 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'global state', 'component stores', 'state solutions', 'migrating', 'legacy patterns', plus technology names 'Signals', 'NgRx', 'RxJS' that developers would naturally mention. | 3 / 3 |
Distinctiveness Conflict Risk | Clear niche targeting Angular-specific state management with distinct triggers (Signals, NgRx, RxJS, component stores). Unlikely to conflict with generic JavaScript or other framework skills due to Angular-specific terminology. | 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 solid, actionable Angular state management skill with excellent code examples covering multiple patterns from simple Signals to NgRx. However, it's overly comprehensive for a single SKILL.md file, includes some explanatory content Claude doesn't need (state category definitions), and lacks explicit validation workflows for state migrations or debugging steps.
Suggestions
Remove the 'When to Use' and 'Do Not Use' sections as they duplicate frontmatter purpose; trim the 'State Categories' table to just the solutions column
Add explicit validation checkpoints to the migration section: 'After converting, verify: 1) Template bindings use () syntax, 2) No remaining .subscribe() calls, 3) Run tests'
Split into SKILL.md (quick start + selection criteria) with references to NGRX.md, SIGNAL-PATTERNS.md, and MIGRATION.md for detailed patterns
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity, such as the 'When to Use This Skill' and 'Do Not Use This Skill' sections that duplicate frontmatter intent, and the 'Core Concepts' table explaining basic state categories Claude already understands. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all patterns include complete, copy-paste ready TypeScript with proper imports, decorators, and usage examples. The migration examples are particularly actionable with clear before/after comparisons. | 3 / 3 |
Workflow Clarity | While patterns are well-organized, there are no explicit validation checkpoints or error recovery workflows. The migration section lacks step-by-step sequencing, and the optimistic update pattern doesn't include verification that the rollback succeeded. | 2 / 3 |
Progressive Disclosure | Content is well-structured with clear sections, but it's a monolithic 400+ line file that could benefit from splitting advanced patterns (NgRx, ComponentStore) into separate referenced files. The Resources section provides external links but no internal file references for deeper content. | 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 | |
- 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.