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.
71
88%
Does it follow best practices?
Impact
—
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), lists specific techniques and patterns, and includes an explicit 'Use when...' clause with natural trigger terms. The description is concise yet comprehensive, covering both modern Angular features (Signals, Control Flow) and architectural patterns (Smart/Dumb). It uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: building standalone Angular components, Signals inputs, OnPush change detection, Control Flow, and Smart/Dumb patterns. These are all concrete, identifiable techniques. | 3 / 3 |
Completeness | Clearly answers both 'what' (build standalone Angular components with Signals inputs, 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', 'Signals', '@if/@for control flow', 'OnPush change detection', '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, OnPush, @if/@for control flow, and Smart/Dumb patterns. Unlikely to conflict with generic component or frontend skills due to the framework-specific and pattern-specific language. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A concise, well-structured Angular component skill that efficiently communicates modern Angular patterns and anti-patterns without unnecessary verbosity. Its main weakness is the lack of a complete, executable component example that demonstrates the patterns working together — the guidance is specific but declarative rather than demonstrative. The referenced files (standalone-pattern.md, control-flow.md) are not present in the bundle, limiting the progressive disclosure score.
Suggestions
Add a complete, copy-paste-ready example component (even a small one) demonstrating standalone, OnPush, signal inputs/outputs, and @if/@for control flow together to boost actionability.
Provide the referenced bundle files (references/standalone-pattern.md, references/control-flow.md) or remove the references if they don't exist.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Every line is dense with actionable guidance. No unnecessary explanations of what Angular is or how components work generally. Assumes Claude knows Angular and focuses only on the specific patterns and constraints to follow. | 3 / 3 |
Actionability | Provides specific API names, patterns, and anti-patterns with clear directives (e.g., use `input.required<T>()` not `@Input()`), but lacks executable code examples showing a complete component. The guidance is concrete but not copy-paste ready — no full component example demonstrating the patterns together. | 2 / 3 |
Workflow Clarity | This is a pattern/convention skill rather than a multi-step process skill. The single task (building Angular components) is unambiguous with clear rules. The Smart/Dumb split provides a clear decision framework, and anti-patterns serve as validation checkpoints for correctness. | 3 / 3 |
Progressive Disclosure | References to standalone-pattern.md and control-flow.md are well-signaled and one level deep, but no bundle files were provided to verify these exist. The main content is well-organized into logical sections, though some sections (like Signals & Change Detection) pack many concepts that could benefit from reference file breakouts. | 2 / 3 |
Total | 10 / 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
3df717f
- 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.