angular
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns.
43
31%
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 ./skills/antigravity-angular/SKILL.mdQuality
Discovery
32%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 technical domain (modern Angular) and lists relevant feature areas, but reads more like a resume bullet point than a skill selection guide. It lacks concrete actions (what it does) and completely omits 'Use when...' guidance, making it difficult for Claude to reliably select this skill from a large pool.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Angular development, Angular components, signals, SSR, or mentions .component.ts files.'
Replace expertise claims with concrete actions, e.g., 'Creates and refactors Angular v20+ components using Signals and Standalone patterns, configures SSR/Hydration, and migrates Zone-based apps to Zoneless architecture.'
Include common natural language variations users might say, such as 'Angular app', 'Angular project', 'ng generate', 'Angular migration', or 'Angular routing'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and lists specific technical areas (Signals, Standalone Components, Zoneless applications, SSR/Hydration, reactive patterns), but doesn't describe concrete actions—it describes expertise areas rather than what it does (e.g., 'creates components', 'migrates to signals'). | 2 / 3 |
Completeness | Describes 'what' only in terms of expertise areas (not concrete actions), and completely lacks any 'when' clause or explicit trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant Angular-specific keywords like 'Signals', 'Standalone Components', 'Zoneless', 'SSR/Hydration', and 'Angular v20+' that users might mention, but misses common natural language variations like 'Angular app', 'Angular project', 'component creation', 'migration', or '.ts files'. | 2 / 3 |
Distinctiveness Conflict Risk | The specificity to Angular v20+ and named features like Signals and Zoneless helps distinguish it from generic web development skills, but it could still overlap with general TypeScript, frontend, or web framework skills due to the lack of explicit trigger boundaries. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
29%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill reads as a comprehensive Angular tutorial/reference document rather than a focused skill file. While the code examples are excellent and executable, the content is far too verbose for a skill file—it explains concepts Claude already knows from training data, includes speculative future features (v22+ Signal Forms), and packs everything into a single monolithic file. The workflow instructions are vague and lack validation checkpoints.
Suggestions
Reduce the content to only what Claude wouldn't already know—project-specific conventions, non-obvious patterns, or gotchas. Remove explanations of standard Angular concepts like what Signals are or how DI works.
Split the monolithic content into focused sub-files (e.g., SIGNALS.md, SSR.md, ZONELESS.md) and make SKILL.md a concise overview with navigation links to each.
Replace the vague 4-step 'Instructions' section with a concrete workflow that includes specific validation steps, e.g., 'Run ng build to verify compilation' and 'Run ng test to check for regressions' with error recovery guidance.
Remove the version timeline with future dates (Angular 21, 22) and speculative features (Signal Forms 'Coming in v22+') as these are time-sensitive and may become inaccurate.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | This is extremely verbose at ~500+ lines. It explains many concepts Claude already knows (what Signals are, what Standalone Components are, what SSR is, how DI works). The version timeline with future dates, extensive tables comparing Signals vs RxJS, and comprehensive coverage of nearly every Angular feature makes this more of a tutorial/reference manual than a skill. Most of this content is general Angular documentation that Claude would already have in its training data. | 1 / 3 |
Actionability | The code examples are concrete, executable, and copy-paste ready throughout. Every section includes real TypeScript/Angular code with proper imports, decorators, and complete component definitions. The examples cover realistic use cases like auth guards, state services, and testing patterns. | 3 / 3 |
Workflow Clarity | The 'Instructions' section is extremely vague: 'Assess the Angular version', 'Apply modern patterns', 'Validate with build and tests' - these are not actionable workflow steps. There are no validation checkpoints, no error recovery loops, and no clear sequence for multi-step operations like migration or SSR setup. For a skill that includes destructive operations like migration, this is insufficient. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of text with 11 major sections all inline. There are no references to separate files for detailed content. The entire Angular reference (Signals, Standalone, Zoneless, SSR, Routing, DI, Composition, State Management, Forms, Performance, Testing) is crammed into a single file. This should be split into focused sub-files with the SKILL.md serving as an overview with navigation links. | 1 / 3 |
Total | 6 / 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 |
|---|---|---|
skill_md_line_count | SKILL.md is long (824 lines); consider splitting into references/ and linking | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Repository
- boisenoise/skills-collections
- Commit
431bfad
- 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.