angular-architect
tessl i github:jeffallan/claude-skills --skill angular-architectUse when building Angular 17+ applications with standalone components or signals. Invoke for enterprise apps, RxJS patterns, NgRx state management, performance optimization, advanced routing.
61%
Overall
Validation
Implementation
Activation
Validation
75%| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md line count is 98 (<= 500) | Pass |
frontmatter_valid | YAML frontmatter is valid | Pass |
name_field | 'name' field is valid: 'angular-architect' | Pass |
description_field | 'description' field is valid (191 chars) | Pass |
description_voice | 'description' uses third person voice | Pass |
description_trigger_hint | Description includes an explicit trigger hint | Pass |
compatibility_field | 'compatibility' field not present (optional) | Pass |
allowed_tools_field | 'allowed-tools' field not present (optional) | Pass |
metadata_version | 'metadata' field is not a dictionary | Warning |
metadata_field | 'metadata' field not present (optional) | Pass |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_present | SKILL.md body is present | Pass |
body_examples | No examples detected (no code fences and no 'Example' wording) | Warning |
body_output_format | Output/return/format terms detected | Pass |
body_steps | Step-by-step structure detected (ordered list) | Pass |
Total | 12 / 16 Passed |
Implementation
42%This skill has strong organizational structure with good progressive disclosure through reference files, but critically lacks actionable code examples. It reads more like a checklist of best practices than executable guidance. The constraints are useful but would benefit from concrete examples showing correct vs incorrect patterns.
Suggestions
- Add executable code examples for key patterns: a standalone component with signals, an OnPush component with proper change detection, and an RxJS subscription with proper cleanup
- Include a concrete NgRx example showing store setup, action, reducer, and selector in minimal form
- Add validation checkpoints to the Core Workflow, such as 'Run ng build --configuration production to verify bundle size' after optimization step
- Remove or condense the 'Role Definition' and 'Knowledge Reference' sections as they don't provide actionable guidance
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is reasonably efficient but includes some unnecessary elements like the 'Role Definition' section that explains Claude's persona rather than actionable guidance. The 'Knowledge Reference' section is a keyword list that adds little value. | 2 / 3 |
Actionability | The skill lacks any concrete, executable code examples. It describes what to do ('Use standalone components', 'Use OnPush change detection') but provides no actual implementation code, commands, or copy-paste ready snippets. | 1 / 3 |
Workflow Clarity | The 'Core Workflow' provides a clear 6-step sequence, but lacks validation checkpoints or feedback loops. For complex Angular development involving state management and testing, there's no guidance on when to verify or how to recover from errors. | 2 / 3 |
Progressive Disclosure | Excellent structure with a clear reference table pointing to topic-specific files (components.md, rxjs.md, etc.) with explicit 'Load When' guidance. References are one level deep and well-signaled. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
72%The description has strong trigger term coverage and clear distinctiveness for Angular development, but lacks specificity about what concrete actions the skill performs. It reads more like a topic list than a capability description, telling Claude when to use it but not what it will actually do.
Suggestions
- Add concrete actions describing what the skill does, e.g., 'Generates Angular 17+ components, configures routing, implements NgRx stores, and optimizes performance'
- Restructure to lead with capabilities before the 'Use when' clause to clearly answer 'what does this do' first
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular 17+) and lists several areas (standalone components, signals, RxJS, NgRx, routing, performance) but doesn't describe concrete actions - it lists topics rather than specific capabilities like 'create components', 'configure routes', or 'implement state management'. | 2 / 3 |
Completeness | Has a 'Use when' clause which is good, but the 'what' portion is weak - it lists topics/technologies rather than explaining what the skill actually does. The description tells when to invoke but not what actions or outputs to expect. | 2 / 3 |
Trigger Term Quality | Good coverage of natural terms users would say: 'Angular', 'standalone components', 'signals', 'enterprise apps', 'RxJS', 'NgRx', 'state management', 'routing', 'performance optimization' - these are terms developers naturally use when seeking Angular help. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly distinguishable with specific Angular 17+ focus, standalone components, signals, and NgRx - these are distinct enough to avoid conflicts with generic web development or other framework skills. | 3 / 3 |
Total | 10 / 12 Passed |
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.