angular
Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns.
53
31%
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 reads more like a resume bullet point ('expert with deep knowledge of...') than a functional skill description. It identifies the domain and some specific Angular features but fails to describe concrete actions the skill performs and completely lacks 'when to use' guidance. The first-person-adjacent 'expert' framing doesn't follow the recommended third-person action voice.
Suggestions
Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about Angular development, mentions Angular components, signals, SSR, or works with .component.ts files.'
Replace the expertise claim with concrete actions in third person, e.g., 'Builds and refactors Angular v20+ applications using Signals, Standalone Components, and Zoneless architecture. Implements SSR/Hydration and reactive patterns.'
Include common natural language variations users might say, such as 'Angular app', 'Angular project', 'ng serve', 'Angular template', '.ts files', or 'frontend framework'.
| 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' at a high level (Angular expertise areas) but completely lacks any 'when should Claude use it' guidance—there is no 'Use when...' clause or equivalent explicit trigger guidance, which per the rubric should cap completeness at 2, and since the 'what' is also weak (expertise claims rather than actions), this scores a 1. | 1 / 3 |
Trigger Term Quality | Includes relevant Angular-specific keywords like 'Signals', 'Standalone Components', 'Zoneless', 'SSR/Hydration' that users might mention, but misses common natural language triggers like 'Angular app', 'Angular project', 'component', 'template', 'TypeScript', or file extensions like '.ts', '.component.ts'. | 2 / 3 |
Distinctiveness Conflict Risk | The Angular v20+ specificity and mention of modern features like Signals and Zoneless help 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 like a condensed Angular documentation/cheat sheet rather than a focused skill file. While the code examples are excellent and executable, the document is far too long and monolithic, explaining many concepts Claude already understands. It lacks clear workflows with validation steps and would benefit enormously from splitting into focused sub-files with a concise overview in the main SKILL.md.
Suggestions
Reduce SKILL.md to a concise overview (~50-80 lines) with quick-start patterns, and move detailed sections (testing, state management, forms, SSR, routing, performance) into separate referenced files like SIGNALS.md, SSR.md, TESTING.md, etc.
Replace the vague 4-step Instructions with concrete workflows for common tasks (e.g., 'Adding a new standalone component', 'Enabling zoneless mode', 'Setting up SSR') with explicit validation checkpoints like 'ng build --configuration production' and 'ng test'.
Remove explanatory text that Claude already knows (e.g., 'Signals are Angular's fine-grained reactivity system', 'Standalone components are self-contained') and keep only the code patterns and decision tables.
Remove or move the version timeline with future dates to a separate reference, as time-sensitive information clutters the main skill and may become stale.
| 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). Much of this is Angular documentation repackaged rather than novel, project-specific guidance. The version timeline with future dates is time-sensitive filler. | 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 usage patterns. Testing examples are complete with setup and assertions. | 3 / 3 |
Workflow Clarity | The 4-step 'Instructions' section is extremely vague ('Assess the Angular version', 'Apply modern patterns', 'Validate with build and tests') with no concrete commands or validation checkpoints. There's no clear workflow for any multi-step process like migration, SSR setup, or going zoneless. The skill reads as a reference document, not a workflow guide. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of text with 11 major sections all inline. Content that should be in separate reference files (testing patterns, state management, forms, SSR configuration, routing) is all crammed into one massive document. The external links at the bottom are just generic Angular docs, not structured sub-files. No content is split into referenced files. | 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 (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
636b862
- 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.