angular-best-practices
Angular performance optimization and best practices guide. Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency.
71
66%
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-best-practices/SKILL.mdQuality
Discovery
67%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 has a solid structure with an explicit 'Use when...' clause that clearly communicates both purpose and trigger conditions. However, it lacks specific concrete actions (e.g., lazy loading, OnPush change detection, tree shaking) that would help Claude distinguish this skill from a general Angular skill, and the trigger terms could be expanded to cover more natural user phrasings.
Suggestions
Add specific concrete actions like 'Implements OnPush change detection, configures lazy loading, optimizes bundle size with tree shaking, and applies trackBy in ngFor loops'.
Expand trigger terms to include natural phrases users might say, such as 'slow Angular app', 'change detection strategy', 'lazy loading', 'AOT', 'zone.js optimization', or 'Angular build size'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular performance optimization) and mentions some areas (bundle size, rendering efficiency), but doesn't list specific concrete actions like 'configure lazy loading', 'implement OnPush change detection', or 'tree-shake unused modules'. | 2 / 3 |
Completeness | Clearly answers both 'what' (Angular performance optimization and best practices guide) and 'when' (Use when writing, reviewing, or refactoring Angular code for optimal performance, bundle size, and rendering efficiency) with an explicit 'Use when...' clause. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Angular', 'performance', 'bundle size', 'rendering efficiency', 'refactoring', but misses common natural variations users might say such as 'slow Angular app', 'change detection', 'lazy loading', 'AOT compilation', 'trackBy', or 'zone.js'. | 2 / 3 |
Distinctiveness Conflict Risk | The Angular focus provides some distinctiveness, but 'performance optimization' and 'best practices guide' are broad enough to potentially overlap with general Angular development skills or general web performance optimization skills. | 2 / 3 |
Total | 9 / 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 solid, highly actionable Angular performance guide with excellent executable code examples covering all major optimization areas. Its main weaknesses are its monolithic length (better suited to progressive disclosure across multiple files), some redundancy in the CORRECT/WRONG pattern pairs, and the lack of workflow guidance for actually applying these optimizations with validation steps. The duplicated 'When to Use' section and generic 'Limitations' boilerplate detract slightly from conciseness.
Suggestions
Split detailed sections (SSR, State Management, Memory Management) into separate referenced files, keeping SKILL.md as a concise overview with the priority table and quick reference checklist.
Add a brief workflow section describing how to audit and apply these optimizations to an existing codebase, including validation steps (e.g., 'Run ng build --stats-json and check bundle sizes before/after changes').
Remove the duplicated 'When to Use' section at the bottom and the generic 'Limitations' boilerplate, which add no Angular-specific value.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient with good code examples, but includes some unnecessary elements: the 'When to Use' section appears twice, the priority table adds moderate value but could be leaner, and some CORRECT/WRONG pairs are verbose when the correct pattern alone would suffice. The 'Limitations' boilerplate at the end is generic filler. | 2 / 3 |
Actionability | Every rule includes fully executable, copy-paste-ready TypeScript and HTML code examples with clear CORRECT/WRONG patterns. Specific imports, decorators, and configurations are shown rather than described abstractly. | 3 / 3 |
Workflow Clarity | The content is organized by priority categories with clear checklists, but it's primarily a reference guide rather than a workflow. There are no validation checkpoints, feedback loops, or sequenced steps for applying these optimizations to an existing codebase. For a performance optimization skill that could involve destructive refactoring, some verification guidance would be valuable. | 2 / 3 |
Progressive Disclosure | The content is well-structured with clear headers and a priority table for navigation, but at ~400 lines it's a monolithic document that could benefit from splitting detailed sections (SSR, state management, etc.) into separate files. The external resource links at the bottom are helpful but the inline content is heavy for a SKILL.md overview. | 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 (568 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.