angular-core
Angular core patterns: standalone components, signals, inject, control flow, zoneless. Trigger: When creating Angular components, using signals, or setting up zoneless.
78
72%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./ywai/skills/angular/core/SKILL.mdQuality
Discovery
57%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 identifies a clear Angular-focused niche with modern framework patterns, providing good distinctiveness. However, it lacks concrete action verbs describing what the skill does (e.g., 'creates', 'migrates', 'configures') and the trigger terms could be expanded to cover more natural user phrasings. The description reads more like a topic list than a capability statement.
Suggestions
Add action verbs to describe concrete capabilities, e.g., 'Creates standalone components, implements reactive state with signals, configures zoneless change detection'
Expand trigger terms to include common user phrasings like 'Angular app', 'ng component', 'reactive state', 'change detection', 'Angular 17+'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and lists specific concepts (standalone components, signals, inject, control flow, zoneless), but these are feature names rather than concrete actions. Missing verbs describing what the skill actually does with these patterns. | 2 / 3 |
Completeness | Has a 'Trigger:' clause which addresses 'when', but the 'what' is weak - it lists concepts without explaining what actions the skill performs. The trigger clause exists but is narrow, only covering component creation and signals/zoneless setup. | 2 / 3 |
Trigger Term Quality | Includes relevant Angular-specific terms like 'signals', 'zoneless', 'standalone components' that users might mention, but missing common variations like 'Angular app', 'ng', 'reactive', or action-oriented terms like 'create component', 'migrate to signals'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly targets Angular-specific modern patterns (signals, zoneless, standalone) which are distinct from general web development or other frameworks. The specific Angular terminology creates a clear niche unlikely to conflict with React, Vue, or general JavaScript skills. | 3 / 3 |
Total | 9 / 12 Passed |
Implementation
87%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 Angular skill file that efficiently communicates modern Angular patterns (signals, standalone components, zoneless) with executable code examples and clear do/don't comparisons. The content is exceptionally concise and actionable. The only weakness is the zoneless migration section, which could benefit from validation steps to confirm the migration succeeded.
Suggestions
Add a validation step for zoneless setup (e.g., 'Verify zoneless is working: check console for no zone.js warnings, confirm change detection triggers only on signal updates')
Consider adding a troubleshooting note for common zoneless issues (e.g., 'If UI doesn't update, ensure you're using signals or calling markForCheck()')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No explanations of what Angular is or how components work. Every section delivers actionable patterns with minimal prose, using ✅/❌ markers and tables for quick scanning. | 3 / 3 |
Actionability | Fully executable TypeScript and HTML examples throughout. Code is copy-paste ready with real patterns (signals, inject, control flow syntax). The comparison tables clearly show what to use vs avoid. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, the zoneless setup section lacks explicit validation steps. No guidance on verifying zoneless is working correctly or troubleshooting if change detection breaks after removing zone.js. | 2 / 3 |
Progressive Disclosure | Well-organized with clear section headers and horizontal rules. External resources linked at the end. Content is appropriately sized for a single SKILL.md without needing separate files. Tables provide quick reference without bloating the document. | 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
- Yoizen/dev-ai-workflow
- Commit
d9bf9a4
- 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.