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.
Install with Tessl CLI
npx tessl i github:sickn33/antigravity-awesome-skills --skill angular-best-practices83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description has good structure with explicit 'Use when' guidance and clear Angular-specific focus, making it complete and distinctive. However, it lacks specific concrete actions (what optimization techniques it covers) and could include more natural trigger terms users might actually say when experiencing Angular performance issues.
Suggestions
Add specific concrete actions like 'implement lazy loading, configure OnPush change detection, optimize template expressions, reduce bundle size with tree shaking'
Include more natural trigger terms users might say: 'slow Angular app', 'large bundle', 'change detection issues', 'lazy loading', 'AOT', 'zone.js'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular) and mentions general areas (performance, bundle size, rendering efficiency) but doesn't list specific concrete actions like 'implement lazy loading', 'configure change detection', or 'optimize template bindings'. | 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 explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant terms like 'Angular', 'performance', 'bundle size', 'rendering' but misses common variations users might say like 'slow Angular app', 'reduce build size', 'change detection', 'lazy loading', or 'AOT compilation'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Angular-specific performance optimization, which is distinct from general JavaScript/TypeScript skills or other framework skills. The combination of 'Angular' + 'performance' creates a clear niche. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a high-quality Angular performance skill with excellent actionability through concrete CORRECT/WRONG code patterns and strong conciseness that respects Claude's existing knowledge. The priority-based organization and checklists provide good structure. The main weakness is the lack of validation steps or feedback loops for verifying that performance optimizations are working correctly.
Suggestions
Add a validation section with commands/tools to measure performance improvements (e.g., Lighthouse scores, bundle analyzer commands, or Angular DevTools profiling steps)
Include a brief troubleshooting workflow: 'If performance doesn't improve after applying X, check Y and Z'
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is highly efficient with no unnecessary explanations of basic concepts. Every section provides direct, actionable code examples without verbose preambles or explanations of what Angular is or how frameworks work. | 3 / 3 |
Actionability | Excellent executable code examples throughout with clear CORRECT/WRONG patterns. Code snippets are copy-paste ready with proper imports, decorators, and complete implementations rather than pseudocode. | 3 / 3 |
Workflow Clarity | While the priority table provides good sequencing and checklists exist at the end, the content lacks explicit validation checkpoints or feedback loops. For performance optimization work that can break applications, there's no guidance on how to verify changes work correctly before proceeding. | 2 / 3 |
Progressive Disclosure | Well-organized with clear sections, a priority table for navigation, and external resource links at the end. The quick reference checklists provide excellent summary navigation. Content is appropriately structured within a single comprehensive file without unnecessary nesting. | 3 / 3 |
Total | 11 / 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 (564 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 | |
- 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.