angular
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns.
34
31%
Does it follow best practices?
Impact
—
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 reads more like a resume bullet point than a skill selector — it declares expertise areas but fails to describe concrete actions the skill performs or when it should be selected. It lacks any 'Use when...' clause and uses no action verbs, making it difficult for Claude to reliably choose this skill from a large pool. The Angular-specific terminology provides some distinctiveness but is insufficient without explicit trigger guidance.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Angular development, Angular components, Angular signals, or building Angular applications.'
Replace the expertise declaration with concrete actions using third-person verbs, e.g., 'Generates Angular v20+ components using Signals and Standalone architecture, configures SSR/Hydration, migrates Zone-based apps to Zoneless.'
Include common user-facing trigger terms and file extensions like '.ts', '.html', 'Angular CLI', 'ng generate', 'Angular template', 'Angular routing' to improve keyword coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and lists specific technical areas (Signals, Standalone Components, Zoneless, SSR/Hydration, reactive patterns), but describes expertise areas rather than concrete actions the skill performs. No verbs describing what it actually does. | 2 / 3 |
Completeness | Describes 'what' only loosely (expertise areas, not actions) and completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, which per the rubric should cap completeness at 2, and the 'what' is also weak, bringing it to 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 user phrases like 'Angular component', 'Angular app', 'TypeScript', or action-oriented terms like 'build', 'debug', 'migrate'. | 2 / 3 |
Distinctiveness Conflict Risk | The Angular v20+ specificity and named features like Signals and Zoneless help distinguish it from generic coding skills, but 'reactive patterns' and 'SSR/Hydration' could overlap with other framework skills (e.g., React, Next.js). Without clear trigger boundaries, some conflict risk remains. | 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 more like a comprehensive Angular documentation page than a focused skill file. While the code examples are excellent and fully executable (strong actionability), the content is far too verbose, explains many concepts Claude already knows, and lacks a clear workflow with validation steps. The monolithic structure with no bundle files means everything is crammed into one enormous file with no progressive disclosure.
Suggestions
Reduce content by 70%+ — remove explanations of concepts Claude already knows (what Signals are, what Standalone Components are, basic DI) and keep only Angular-specific patterns that are non-obvious or version-specific gotchas.
Split detailed sections (SSR, Testing, State Management, Forms, Routing) into separate bundle files and reference them from a concise SKILL.md overview.
Replace the vague 4-step 'Instructions' section with a concrete workflow including specific CLI commands and validation checkpoints (e.g., 'Run `ng build` to verify no compilation errors', 'Run `ng test` to validate changes').
Remove the version timeline with future dates (Angular 21, 22) and speculative features (Signal Forms 'Coming in v22+') — 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, basic DI patterns, how reactive forms work). The version timeline with future dates, the extensive comparison tables, and the exhaustive code examples for well-known Angular patterns all consume tokens without adding unique value. Much of this reads like Angular documentation rather than a concise skill reference. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — from Signal creation, to bootstrapping, to SSR configuration, to testing patterns. Every section includes concrete TypeScript code with proper imports and realistic usage patterns. | 3 / 3 |
Workflow Clarity | The top-level 'Instructions' section lists only 4 vague steps ('Assess the Angular version', 'Apply modern patterns', 'Implement with proper typing', 'Validate with build and tests') with no concrete commands, validation checkpoints, or error recovery. For a skill involving potentially destructive migration/refactoring operations, there are no feedback loops or verification steps. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of text with no bundle files to reference. All content — from basic Signals to SSR to testing to state management — is inlined in a single massive file. There are no references to supporting files for detailed topics, and the external links are just generic Angular documentation URLs rather than structured skill bundle references. | 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
cfced3a
- 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.