Generates Angular 17+ standalone components, configures advanced routing with lazy loading and guards, implements NgRx state management, applies RxJS patterns, and optimizes bundle performance. Use when building Angular 17+ applications with standalone components or signals, setting up NgRx stores, establishing RxJS reactive patterns, performance tuning, or writing Angular tests for enterprise apps.
98
100%
Does it follow best practices?
Impact
97%
1.38xAverage score across 6 eval scenarios
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 an excellent skill description that follows best practices. It uses third person voice, lists specific concrete capabilities, includes comprehensive trigger terms that users would naturally use, and has an explicit 'Use when...' clause. The Angular-specific terminology makes it highly distinctive and unlikely to conflict with other frontend framework skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Generates Angular 17+ standalone components', 'configures advanced routing with lazy loading and guards', 'implements NgRx state management', 'applies RxJS patterns', and 'optimizes bundle performance'. | 3 / 3 |
Completeness | Clearly answers both what (generates components, configures routing, implements state management, applies patterns, optimizes performance) AND when with explicit 'Use when...' clause covering multiple trigger scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'Angular 17+', 'standalone components', 'signals', 'NgRx stores', 'RxJS', 'lazy loading', 'guards', 'performance tuning', 'Angular tests', 'enterprise apps'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Angular 17+ specific terminology, NgRx, RxJS, and standalone components/signals - these are unique to Angular ecosystem and unlikely to conflict with React, Vue, or general JavaScript skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality skill that exemplifies best practices: it's concise yet comprehensive, provides executable code examples, includes clear validation checkpoints in the workflow, and uses progressive disclosure effectively with a reference table. The constraints section provides clear guardrails without being verbose.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, assuming Claude's competence with Angular concepts. No unnecessary explanations of what Angular, signals, or NgRx are—it jumps straight to actionable patterns and code. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for standalone components, RxJS subscription management, and NgRx patterns. Commands like `ng build --configuration production` are specific and actionable. | 3 / 3 |
Workflow Clarity | The 6-step core workflow is clearly sequenced with explicit validation checkpoints: verify store hydration with Redux DevTools, run production build to check bundle size, and verify >85% coverage threshold before proceeding. | 3 / 3 |
Progressive Disclosure | Excellent structure with a clear overview, reference table pointing to one-level-deep topic files (components.md, rxjs.md, etc.), and well-organized sections for patterns, constraints, and output templates. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
5b76101
Table of Contents
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.