Optimization techniques including OnPush, @defer, and Image Optimization. Use when optimizing Angular rendering, deferring blocks, or improving Core Web Vitals.
82
80%
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/angular/angular-performance/SKILL.mdQuality
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.
The description is reasonably well-structured with a clear 'Use when' clause and Angular-specific terminology that aids distinctiveness. However, it lists techniques rather than concrete actions the skill performs, and it could benefit from additional natural trigger terms users might use when seeking performance help (e.g., 'slow', 'performance', 'change detection').
Suggestions
Rewrite capabilities as concrete actions rather than just listing techniques, e.g., 'Configures OnPush change detection strategy, implements @defer blocks for lazy loading, and optimizes images for Core Web Vitals.'
Add more natural trigger terms users would say, such as 'performance', 'slow rendering', 'change detection', 'lazy loading', 'Angular performance optimization'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular optimization) and lists some specific techniques (OnPush, @defer, Image Optimization), but doesn't describe concrete actions—it lists techniques rather than what the skill does with them (e.g., 'configure OnPush change detection', 'implement lazy loading with @defer blocks'). | 2 / 3 |
Completeness | Clearly answers both 'what' (optimization techniques including OnPush, @defer, Image Optimization) and 'when' (explicit 'Use when' clause covering optimizing Angular rendering, deferring blocks, or improving Core Web Vitals). | 3 / 3 |
Trigger Term Quality | Includes some relevant keywords like 'OnPush', '@defer', 'Core Web Vitals', 'Angular rendering', and 'deferring blocks', but misses common user terms like 'performance', 'lazy loading', 'change detection', 'slow rendering', or 'Angular performance'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Angular-specific optimization techniques with distinct triggers like OnPush, @defer, and Core Web Vitals, making it unlikely to conflict with general performance or other framework skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, concise performance optimization skill that efficiently communicates Angular-specific patterns and anti-patterns. Its main weakness is the lack of executable code examples — inline template/component snippets for OnPush, @defer, NgOptimizedImage, and computed() signals would significantly improve actionability. The organization and progressive disclosure are strong.
Suggestions
Add a short executable code example for at least the most critical patterns (e.g., a component with OnPush + signals, a @defer block with @placeholder, and an NgOptimizedImage usage)
Include a brief computed() signal example to concretely illustrate the anti-pattern fix for function calls in templates
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, covering multiple optimization techniques without explaining basic Angular concepts. Every bullet point delivers actionable, non-obvious guidance that Claude wouldn't inherently know (specific API names, specific patterns, specific anti-patterns). | 3 / 3 |
Actionability | The guidance is specific (e.g., naming exact APIs like NgOptimizedImage, ChangeDetectionStrategy.OnPush, @defer triggers) but lacks executable code examples. Concrete template/component snippets showing OnPush setup, @defer blocks, or computed() signal usage would make this copy-paste ready. | 2 / 3 |
Workflow Clarity | This is a collection of optimization principles rather than a multi-step workflow, so there's no sequential process requiring validation checkpoints. Each optimization technique is clearly stated as a single, unambiguous action, which is appropriate for this type of skill. | 3 / 3 |
Progressive Disclosure | The content is well-organized into clear sections (Principles, Guidelines, Anti-Patterns, References) with a single-level reference to defer-usage.md. The main file stays concise while pointing to detailed material where appropriate. | 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 |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
4c72e76
Table of Contents
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.