angular-core
Angular core patterns: standalone components, signals, inject, control flow, zoneless. Trigger: When creating Angular components, using signals, or setting up zoneless.
Install with Tessl CLI
npx tessl i github:Yoizen/dev-ai-workflow --skill angular-core83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
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 niche with modern framework-specific terminology, making it distinctive. However, it reads more like a feature list than a capability description - it doesn't explain what actions the skill performs (generate, review, teach, refactor). The trigger clause exists but could be broader to capture more user scenarios.
Suggestions
Add concrete actions describing what the skill does: 'Generates Angular components using standalone architecture, implements reactive state with signals, configures zoneless change detection.'
Expand trigger terms to include common user phrases: 'Angular app', 'reactive state', '@Component decorator', 'change detection', 'Angular 17+', 'modern Angular'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and lists specific concepts (standalone components, signals, inject, control flow, zoneless), but doesn't describe concrete actions - it lists features/patterns rather than what the skill does with them. | 2 / 3 |
Completeness | Has a 'Trigger:' clause which addresses 'when', but the 'what' is weak - it lists patterns but doesn't explain what the skill actually does (teaches? generates? reviews?). The trigger is present but narrow. | 2 / 3 |
Trigger Term Quality | Includes relevant Angular-specific terms like 'signals', 'zoneless', 'standalone components', but missing common variations users might say like 'Angular app', 'reactive state', '@Component', or 'change detection'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly targets Angular-specific modern patterns with distinct terminology (signals, zoneless, standalone components) that wouldn't conflict with other frontend frameworks or general coding skills. | 3 / 3 |
Total | 9 / 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 an excellent skill file that efficiently communicates Angular's modern patterns. It assumes Claude's competence with TypeScript and Angular basics, focusing only on the specific patterns to follow. The ✅/❌ contrast examples and decision tables make the guidance immediately actionable without verbosity.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. No unnecessary explanations of what Angular is or how components work. Every section delivers actionable patterns with minimal prose, using ✅/❌ markers effectively. | 3 / 3 |
Actionability | Fully executable TypeScript and HTML examples throughout. Code is copy-paste ready with real patterns (signals, inject, control flow syntax). Decision tables provide clear guidance on when to use what. | 3 / 3 |
Workflow Clarity | For a patterns/conventions skill, the workflow is appropriately clear. Each section covers a single concern with explicit REQUIRED markers. The 'When to Use What' tables provide clear decision paths. No multi-step destructive operations require validation checkpoints. | 3 / 3 |
Progressive Disclosure | Well-organized with clear section headers and horizontal rules. Content is appropriately scoped for a single SKILL.md. External resources linked at the end for deeper dives. No unnecessary nesting or monolithic walls of text. | 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.
- 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.