CtrlK
BlogDocsLog inGet started
Tessl Logo

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.

68

Quality

82%

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

72%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 an exemplar of progressive disclosure — lean, well-structured, delegating all executable detail to a single clearly-signaled one-level-deep guide. Its weakness is that the body itself carries no executable code or explicit validation steps, so actionability and workflow clarity rest entirely on the external reference.

Suggestions

Add 1–2 inline executable snippets (e.g., a minimal Signal service or a selection-criteria quick reference) so the skill is actionable without loading the full guide.

Surface at least one explicit validation checkpoint inline (e.g., 'Verify the store compiles with `ng build` before migrating the next slice') rather than only asserting validation 'as mandatory' in the guide.

Add a brief 2–3 step execution sequence in the body (choose pattern → implement → validate) so the workflow is legible at a glance.

DimensionReasoningScore

Conciseness

The ~28-line body is lean, assumes Claude's competence with no concept explanations, and delegates bulk to the guide — every token earns its place per anchor 5.

5 / 5

Actionability

The body itself gives directional guidance ('Read the detailed guide... load relevant sections') rather than executable code or commands; the executable TypeScript lives entirely in the external reference, sitting between the high-level-hints anchor 2 and concrete-guidance anchor 3.

3 / 5

Workflow Clarity

A rough sequence is present (read guide → treat safety/prereqs/validation as mandatory → choose scope → stop-and-ask if inputs missing), but validation checkpoints are only pointed-to as existing in the guide rather than shown inline, matching the implicit-checkpoints anchor 3.

3 / 5

Progressive Disclosure

A clear overview with a single one-level-deep, verified reference (references/detailed-guide.md) clearly signaled as a markdown link with full-vs-section loading guidance, and no nested internal references — matching anchor 5.

5 / 5

Total

16

/

20

Passed

Description

92%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 concisely states what the skill does and gives explicit, multi-trigger 'Use when' guidance with concrete library names. It is specific, distinctive, and well-targeted; only trigger-term synonym coverage keeps it from a perfect sweep.

DimensionReasoningScore

Specificity

Names the Angular state-management domain and enumerates concrete capabilities across Signals, NgRx, and RxJS plus setup, component stores, solution selection, and legacy migration — comprehensive coverage matching anchor 5.

5 / 5

Completeness

Explicitly answers both what ('Master modern Angular state management with Signals, NgRx, and RxJS') and when (a multi-trigger 'Use when...' clause) with concrete trigger phrases, matching anchor 5.

5 / 5

Trigger Term Quality

Strong natural user phrases ('setting up global state', 'managing component stores', 'choosing between state solutions', 'migrating from legacy patterns') plus the canonical library names, but lacks synonym variation that would reach comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

Angular-specific niche pinned to named technologies with the body explicitly redirecting React to a sibling skill, giving a clear niche with minimal conflict risk per anchor 5.

5 / 5

Total

19

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
boisenoise/skills-collections
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.