angular-components
Build standalone Angular components with Signals inputs, OnPush change detection, Control Flow, and Smart/Dumb patterns. Use when building standalone Angular components, implementing @if/@for control flow, applying OnPush change detection, or implementing Signals in Angular components. (triggers: **/*.component.ts, **/*.component.html, angular component, standalone, input signal, output, @if, @for, ChangeDetectionStrategy, OnPush, Input, Output)
94
92%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 covers all key dimensions well. It provides specific capabilities, comprehensive trigger terms including both file patterns and natural language keywords, explicit 'Use when' guidance, and a clearly defined niche within Angular component development. The description is concise yet thorough, using proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: building standalone Angular components, using Signals inputs, OnPush change detection, Control Flow (@if/@for), and Smart/Dumb patterns. These are all concrete, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (build standalone Angular components with Signals, OnPush, Control Flow, Smart/Dumb patterns) and 'when' (explicit 'Use when...' clause listing specific scenarios plus a triggers list for file-based matching). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms including file patterns ('**/*.component.ts', '**/*.component.html'), framework-specific terms ('angular component', 'standalone', 'input signal', 'OnPush'), and template syntax keywords ('@if', '@for', 'ChangeDetectionStrategy'). These are terms Angular developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche focused specifically on Angular standalone components with modern patterns (Signals, Control Flow). The file pattern triggers and Angular-specific terminology make it very unlikely to conflict with non-Angular skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured, concise Angular component skill that efficiently communicates conventions, patterns, and anti-patterns. Its main weakness is the lack of any executable code example showing a complete component implementing these patterns (signals, OnPush, control flow) together, which would make it more immediately actionable. The organization and token efficiency are excellent.
Suggestions
Add a short, complete example component (10-15 lines) demonstrating standalone setup, signal inputs/outputs, OnPush, and @if/@for control flow together — this would significantly boost actionability.
Include a brief template snippet showing the difference between the anti-pattern `{{ calculate() }}` and the correct `computed()` approach to make the anti-patterns section more concrete.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every line delivers actionable guidance without explaining what Angular components are or how change detection works conceptually. Assumes Claude's competence throughout. | 3 / 3 |
Actionability | Provides specific API names, patterns, and clear do/don't guidance (e.g., `input.required<T>()` not `@Input()`), but lacks executable code examples. A concrete component snippet showing these patterns together would elevate this significantly. | 2 / 3 |
Workflow Clarity | This is a pattern/convention skill rather than a multi-step workflow skill. The single-purpose guidance is unambiguous: each bullet clearly states what to use and what to avoid. The Smart/Dumb split provides clear architectural sequencing. | 3 / 3 |
Progressive Disclosure | Clean overview with well-organized sections and two clearly signaled one-level-deep references to standalone-pattern.md and control-flow.md. Content is appropriately split between the overview and reference files. | 3 / 3 |
Total | 11 / 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.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.