CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

The canonical home for this skill is angular-state-management in sickn33/agentic-awesome-skills

SKILL.md
Quality
Evals
Security

Quality

Content

57%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 well-organized and highly code-centric, giving mostly executable patterns for Signals, SignalStore, NgRx, ComponentStore, and server state with optimistic updates. Its main weaknesses are monolithic length that belongs in reference files, re-teaching of boilerplate Claude already knows, minor code errors that keep examples from being copy-paste ready, and absent validation/verification steps in the migration workflow.

Suggestions

Split the body into one-level-deep reference files (e.g., references/ngrx-store.md, references/signalstore.md, references/component-store.md, references/migration.md) and keep SKILL.md as a concise overview with the selection-criteria table and links, dramatically reducing token load.

Fix the executable gaps: import 'computed' in the SignalStore example, use the injected HttpClient (via firstValueFrom) instead of raw 'fetch' in Pattern 2, and type the template input handler to keep examples copy-paste ready.

Cut sections that re-teach what Claude already knows — the trivial counter service (Pattern 1) and full NgRx actions/reducer/selectors/effects boilerplate — down to the non-obvious parts (e.g., signalStore with patchState, toSignal/toObservable bridging, optimistic-update rollback).

DimensionReasoningScore

Conciseness

The body is mostly code with little prose padding, but substantial sections re-teach boilerplate Claude already knows: a trivial counter service (Pattern 1), full standard NgRx actions/reducer/selectors/effects slices, and ComponentStore boilerplate. This matches 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, where such re-teaching would be minor.

3 / 5

Actionability

Patterns are concrete, near-executable TypeScript with file paths and usage examples, matching 'mostly executable guidance; concrete code with minor gaps'. It falls short of 5 due to execution gaps: Pattern 3 uses 'computed' without importing it from '@angular/core', Pattern 2 injects HttpClient and imports toSignal but uses raw 'fetch', and the template '(input)' handler's '$event.target.value' is not type-safe in strict mode.

4 / 5

Workflow Clarity

The selection-criteria block gives a decision path and the migration section shows before/after, but there is no explicit step sequencing or validation checkpoints — e.g., no incremental migration procedure, no verify step after adopting a pattern. This matches 'steps listed but validation gaps; checkpoints missing or implicit' rather than 4, which requires most checkpoints present.

3 / 5

Progressive Disclosure

The body has clear section headers and good internal organization, but the skill is a ~630-line monolith with no bundle files at all — content like the full NgRx setup, ComponentStore patterns, and the migration guide clearly belong in separate reference files. This matches 'some structure; content that should be separate is inline' rather than 4, since nothing is split out into one-level-deep references.

3 / 5

Total

13

/

20

Passed

Description

87%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 strong: it clearly states what the skill covers (Angular state management across Signals, NgRx, and RxJS) and provides an explicit 'Use when...' clause with four concrete trigger scenarios. Trigger-term coverage is good with only minor synonyms missing, and it is clearly distinguishable from related skills.

DimensionReasoningScore

Specificity

The description names the domain and technologies ("Master modern Angular state management with Signals, NgRx, and RxJS") and the trigger clause lists several concrete activities ("setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns"), matching the 'several specific actions with minor gaps' anchor. It falls short of 5 because the lead verb 'Master' is broad and does not itself enumerate concrete capabilities, but exceeds 3's '1-2 concrete actions' threshold.

4 / 5

Completeness

It explicitly answers both 'what' ("Master modern Angular state management with Signals, NgRx, and RxJS") and 'when' ("Use when setting up global state, managing component stores, choosing between state solutions, or migrating from legacy patterns") with four concrete trigger phrases. This matches the score-5 anchor with an explicit, concrete 'Use when...' clause rather than the weaker, more generic score-4 form.

5 / 5

Trigger Term Quality

Natural user phrases like "Angular state management", "Signals", "NgRx", "RxJS", "global state", "component stores", and "migrating from legacy patterns" are present. A few natural terms are missing (e.g., "signal store", "Akita", "optimistic updates", "state migration"), matching the 'good keyword coverage; a few natural terms missing' anchor rather than 5's comprehensive synonym coverage.

4 / 5

Distinctiveness Conflict Risk

The description is firmly niched to Angular state management with named libraries (Signals, NgRx, RxJS), giving it a clear niche with distinct triggers and minimal conflict risk against generic state-management or other-framework skills. The body further disambiguates by pointing React tasks to a separate skill.

5 / 5

Total

18

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (635 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

agent-skills-hub/agent-skills-hub

Path

skills/angular-state-management/SKILL.md

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.