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.
92
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 a strong skill description that clearly identifies its domain (Angular component development) with specific, concrete capabilities and explicit trigger guidance. It uses appropriate third-person voice and includes natural developer terminology that would facilitate accurate skill selection. The description is concise yet comprehensive, covering both what the skill does and when to use it.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: building standalone Angular components, Signals inputs, OnPush change detection, Control Flow (@if/@for), and Smart/Dumb patterns. These are concrete, well-defined Angular concepts. | 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 four specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords users would say: 'standalone Angular components', '@if/@for control flow', 'OnPush change detection', 'Signals', 'Smart/Dumb patterns'. These cover the specific Angular terminology developers would naturally use. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Angular-specific terminology like Signals inputs, OnPush change detection, @if/@for control flow, and Smart/Dumb patterns. This is unlikely to conflict with other skills unless there are multiple Angular-specific skills, and even then the focus on these specific patterns is narrow enough. | 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 modern Angular patterns and anti-patterns. Its main strength is token efficiency and clear organization. The primary weakness is the lack of executable code examples — a single complete component example demonstrating signals, OnPush, and control flow together would significantly boost actionability.
Suggestions
Add a short, complete executable component example (15-20 lines) showing a presentational component with signal inputs, OnPush, and @if/@for control flow together.
Include a brief smart component example showing service injection and state management with signals to complement the Smart/Dumb pattern description.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Every bullet point delivers specific, 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. No copy-paste ready component template showing these patterns together, which would significantly improve actionability. | 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. No destructive or batch operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-organized into logical sections (Structure, Signals, Control Flow, Anti-Patterns) with clear one-level-deep references to standalone-pattern.md and control-flow.md. The main file serves as a concise overview without inlining excessive detail. | 3 / 3 |
Total | 11 / 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- 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.