angular-routing
Configure Angular Router with lazy-loaded routes, functional guards, and component input binding. Use when defining routes, lazy-loading features, creating route guards, or setting up resolvers.
87
86%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
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 a strong skill description that clearly identifies the domain (Angular Router), lists specific capabilities (lazy-loaded routes, functional guards, component input binding), and provides explicit trigger guidance via a 'Use when' clause. It uses proper third-person voice and covers natural keywords Angular developers would use.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: configuring Angular Router, lazy-loaded routes, functional guards, and component input binding. These are distinct, well-defined capabilities. | 3 / 3 |
Completeness | Clearly answers both 'what' (configure Angular Router with lazy-loaded routes, functional guards, component input binding) and 'when' (explicit 'Use when' clause covering defining routes, lazy-loading features, creating route guards, setting up resolvers). | 3 / 3 |
Trigger Term Quality | Includes natural keywords users would say: 'routes', 'lazy-loading', 'route guards', 'resolvers', 'Angular Router'. These are terms Angular developers naturally use when seeking help with routing. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Angular Router configuration with distinct triggers like 'lazy-loaded routes', 'functional guards', 'component input binding', and 'resolvers'. Unlikely to conflict with general Angular skills or other framework routing skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
72%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 skill that effectively uses progressive disclosure to keep the main file lean while pointing to detailed references. Its main weakness is the lack of inline executable code examples — the actionable guidance is mostly descriptive rather than copy-paste ready, with concrete implementations deferred entirely to the reference file. Adding at least one minimal code snippet per section would significantly improve actionability.
Suggestions
Add a minimal executable code example for lazy-loaded route configuration (e.g., a routes array with `loadComponent`) directly in the skill body rather than deferring all examples to the reference file.
Include a brief inline code snippet showing a functional guard implementation (`CanActivateFn`) so the skill is actionable without requiring navigation to the reference file.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It assumes Claude knows Angular concepts and doesn't waste tokens explaining what routing, lazy loading, or guards are. Every line provides directive-level guidance. | 3 / 3 |
Actionability | Provides some concrete guidance (e.g., `withComponentInputBinding()` call, `input.required<string>()`, `CanActivateFn`, `ResolveFn<T>`) but lacks executable code examples. Key patterns are deferred to a reference file rather than shown inline, and there are no copy-paste ready code blocks. | 2 / 3 |
Workflow Clarity | Steps are listed in a logical order (lazy load → guards → input binding → resolvers) but there's no explicit workflow sequence, no validation checkpoints, and no guidance on verifying that routes are correctly configured or that lazy loading is working as expected. | 2 / 3 |
Progressive Disclosure | The skill provides a clear, concise overview with well-signaled one-level-deep references to routing-patterns.md. Content is appropriately split between the overview and the reference file, and navigation is straightforward. | 3 / 3 |
Total | 10 / 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 | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- 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.