angular
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns.
64
Quality
48%
Does it follow best practices?
Impact
94%
1.32xAverage score across 3 eval scenarios
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 framework features, but reads more like a resume bullet point than a skill selection guide. It lacks concrete actions Claude would perform and critically missing any 'Use when...' guidance, making it difficult for Claude to know when to select this skill from a large skill library.
Suggestions
Add a 'Use when...' clause with explicit triggers like 'Use when the user asks about Angular applications, Angular components, Angular signals, or mentions .ts files with @Component decorators'
Replace 'expert with deep knowledge of' with concrete actions like 'Build, migrate, and debug Angular v20+ applications using Signals, Standalone Components, and Zoneless architecture'
Include natural user terms alongside technical ones, such as 'Angular app', 'Angular project', 'frontend framework', or file extensions like '.component.ts'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and lists specific technical concepts (Signals, Standalone Components, Zoneless applications, SSR/Hydration, reactive patterns), but doesn't describe concrete actions like 'build', 'migrate', 'debug', or 'refactor'. | 2 / 3 |
Completeness | Describes what expertise the skill covers but completely lacks any 'Use when...' clause or explicit trigger guidance. There's no indication of when Claude should select this skill over others. | 1 / 3 |
Trigger Term Quality | Includes relevant technical terms like 'Angular', 'Signals', 'Standalone Components', 'SSR', but these are more technical jargon than natural user language. Missing common variations users might say like 'Angular app', 'component', 'frontend', or version-agnostic terms. | 2 / 3 |
Distinctiveness Conflict Risk | The 'Angular v20+' and specific modern features like 'Zoneless' and 'Signals' provide some distinction, but 'reactive patterns' and general frontend concepts could overlap with React, Vue, or other framework skills. | 2 / 3 |
Total | 7 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a comprehensive Angular reference with excellent, executable code examples covering modern patterns like Signals, Standalone Components, and Zoneless applications. However, it's overly verbose for a skill file (~600 lines), lacks explicit workflow validation steps for complex operations like SSR setup, and would benefit from splitting detailed sections into referenced files while keeping SKILL.md as a concise overview.
Suggestions
Add explicit validation checkpoints to the Instructions section (e.g., 'Run `ng build` to verify compilation', 'Test hydration with `ng serve --ssr`')
Split detailed sections (Signals, SSR, Testing) into separate reference files and keep SKILL.md as a concise overview with links
Remove explanatory prose that Claude already knows (e.g., 'Signals are Angular's fine-grained reactivity system') and lead directly with code examples
Move the version timeline to a separate file or remove it - time-sensitive information with future dates becomes stale quickly
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary explanations Claude would know (e.g., 'Signals are Angular's fine-grained reactivity system'). The version timeline with future dates and extensive tables add bulk that could be trimmed. | 2 / 3 |
Actionability | Excellent executable code examples throughout - all TypeScript/Angular code is copy-paste ready with proper imports, complete component definitions, and realistic usage patterns. The examples cover real-world scenarios effectively. | 3 / 3 |
Workflow Clarity | The 'Instructions' section provides only a vague 4-step process without validation checkpoints. For a skill covering SSR, hydration, and migration patterns, explicit validation steps (e.g., 'run ng build --configuration production to verify SSR') are missing. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and tables, but it's monolithic - all 11 major topics are inline rather than split into referenced files. The Resources section links externally but doesn't reference any companion skill files for deep dives. | 2 / 3 |
Total | 9 / 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 (819 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
5c5ae21
- 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.