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 ./plugins/antigravity-awesome-skills-claude/skills/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 selection guide—it lists areas of expertise rather than concrete actions the skill performs. It completely lacks trigger guidance ('Use when...'), making it difficult for Claude to know when to select this skill. The Angular-specific terminology provides some distinctiveness but the description needs actionable verbs and explicit usage triggers.
Suggestions
Add a 'Use when...' clause specifying triggers, e.g., 'Use when the user asks about Angular development, component creation, signal-based reactivity, SSR configuration, or migration to standalone components.'
Replace the expertise-framing with concrete actions, e.g., 'Generates Angular v20+ components using Signals and standalone architecture, configures SSR/hydration, migrates zone-based apps to zoneless, and implements reactive patterns.'
Include common user-facing terms and file types like '.component.ts', 'Angular CLI', 'ng generate', 'template', 'routing', 'NgModule migration' to improve trigger term coverage.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and lists specific technical areas (Signals, Standalone Components, Zoneless applications, SSR/Hydration, reactive patterns), but describes expertise areas rather than concrete actions the skill performs. No verbs describing what it actually does (e.g., 'generates components', 'migrates code', 'configures SSR'). | 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, but the 'what' is also weak (describes knowledge areas, not actions), warranting 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. However, it misses common user-facing terms like 'component', 'template', 'routing', 'dependency injection', or file extensions like '.ts', '.component.ts'. | 2 / 3 |
Distinctiveness Conflict Risk | The specificity to Angular v20+ and modern features like Signals and Zoneless helps distinguish it from generic web development skills. However, it could overlap with general TypeScript, frontend framework, or broader Angular skills since it doesn't clearly delineate its 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 comprehensive Angular tutorial or cheat sheet rather than a focused skill for Claude. While the code examples are excellent and fully executable, the document is far too verbose for a skill file — it explains many concepts Claude already knows, lacks a clear workflow with validation steps, and dumps everything into a single monolithic file instead of using progressive disclosure. The high-level instructions are too vague to guide Claude through complex tasks like SSR setup or zoneless migration.
Suggestions
Drastically reduce content to ~100 lines focusing only on what Claude wouldn't already know — non-obvious gotchas, project-specific conventions, and decision criteria rather than API tutorials.
Add a concrete workflow with validation checkpoints, e.g., 'Run `ng build` to verify no compilation errors → Run `ng test` → Check hydration with `ng serve --ssr` → Verify no console warnings'.
Split into bundle files: a main SKILL.md overview (~50 lines) pointing to separate files like SIGNALS.md, SSR.md, TESTING.md, STATE-MANAGEMENT.md for detailed reference.
Remove the version timeline with future dates (time-sensitive information that will become stale) and basic concept explanations that Claude already knows.
| 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 'Core Concepts' explanations are all things Claude would already know about Angular v20+. Most sections read like a tutorial rather than a concise reference. | 1 / 3 |
Actionability | The skill provides fully executable, copy-paste ready code examples throughout — from signal creation, to component definitions, to bootstrapping, routing, testing, and SSR configuration. Every section includes concrete TypeScript code with proper imports. | 3 / 3 |
Workflow Clarity | The 'Instructions' section is just 4 vague bullet points ('Assess the Angular version', 'Apply modern patterns', 'Validate with build and tests') with no concrete commands, validation checkpoints, or error recovery steps. For a skill covering complex operations like SSR setup and zoneless migration, this is insufficient. There are no feedback loops for any of the multi-step processes described. | 1 / 3 |
Progressive Disclosure | This is a monolithic wall of text with 11 major sections all inline. There are no bundle files to reference, yet the content clearly warrants splitting into separate files (e.g., signals reference, SSR guide, testing guide, state management patterns). The external links at the bottom are to Angular docs, not to organized bundle files. Everything is dumped into one massive document. | 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
- sickn33/antigravity-awesome-skills
- Commit
0839f85
- 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.