tessl-labs/angular-best-practices
Angular patterns — standalone components, signals, inject(), reactive forms, HTTP interceptors, and new control flow
95
94%
Does it follow best practices?
Impact
99%
2.75xAverage score across 4 eval scenarios
Passed
No known issues
Quality
Discovery
100%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 is an excellent skill description that follows best practices. It uses third person voice, lists specific Angular capabilities, includes natural trigger terms developers would use, and provides explicit 'Use when...' guidance covering multiple scenarios (building, reviewing, migrating, new projects).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions and concepts: 'standalone components, signals, services, dependency injection, reactive forms, and HTTP client' - these are all specific Angular features and patterns. | 3 / 3 |
Completeness | Clearly answers both what (Angular patterns including specific features) AND when with explicit triggers: 'Use when building or reviewing Angular apps, when migrating to standalone components or signals, or when setting up a new Angular project.' | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'Angular apps', 'standalone components', 'signals', 'Angular project', 'migrating'. These are terms developers naturally use when working with Angular. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with Angular-specific terminology that wouldn't conflict with other frontend frameworks. Terms like 'standalone components', 'signals', 'dependency injection' are Angular-specific patterns that create a clear niche. | 3 / 3 |
Total | 12 / 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 an excellent Angular skill file that provides comprehensive, actionable guidance with lean, efficient content. The RIGHT/WRONG pattern with executable code examples is highly effective. The main weakness is the lack of explicit workflow guidance for migration scenarios or validation checkpoints when applying these patterns to existing code.
Suggestions
Add a brief 'Migration Workflow' section with steps for converting legacy Angular code (e.g., 1. Identify NgModule components, 2. Convert to standalone, 3. Verify with ng build, 4. Run verifier)
Include validation commands or checks after major pattern applications (e.g., 'Run `ng build` to verify standalone conversion succeeded')
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is highly efficient with no unnecessary explanations of concepts Claude would know. Each section delivers the pattern with minimal preamble, using RIGHT/WRONG examples that speak for themselves. | 3 / 3 |
Actionability | Every pattern includes fully executable, copy-paste ready TypeScript code examples. The RIGHT/WRONG format with complete code snippets makes implementation unambiguous. | 3 / 3 |
Workflow Clarity | While individual patterns are clear, there's no explicit workflow for applying these patterns to an existing codebase or new project. Missing validation steps for migration scenarios (e.g., how to verify a component was correctly converted to standalone). | 2 / 3 |
Progressive Disclosure | Well-organized with numbered sections, a comprehensive quick reference table, and clear links to verifiers for deeper validation. Content is appropriately structured for a single SKILL.md file without needing external references. | 3 / 3 |
Total | 11 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
Reviewed
Table of Contents