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.

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A compact, well-structured skill body that delegates code examples to a single clearly-signaled reference file and assumes Claude's competence. It is actionable and well-organized, with only minor conciseness tweaks warranted.

Suggestions

Consider removing or repurposing the 'Canonical response anchors' section, since instructing the skill to preserve the words 'No logic' and 'deprecated' adds little actionable value.

Inline one minimal `provideRouter(routes, withComponentInputBinding())` route snippet in section 3 so the most common case is copy-paste ready without opening the reference.

Add a one-line note in section 4 clarifying when to prefer a custom TitleStrategy versus inline `title` route data, to close the small guidance gap.

Dimension	Reasoning	Score
Conciseness	The body is lean, assumes Angular competence, and avoids explaining basic concepts, though the 'Canonical response anchors' section (preserving 'No logic' / 'deprecated') reads as minor self-referential padding that could be trimmed.	4 / 5
Actionability	Provides concrete API names and configuration snippets (`loadComponent`, `withComponentInputBinding()`, `input.required<string>()`, `ResolveFn<T>`) with full executable examples one click away in the reference file, leaving only minor gaps inline.	4 / 5
Workflow Clarity	The four numbered practices plus an Anti-Patterns section are clearly enumerated and well-organized for a simple, single-purpose skill; no validation checkpoints are needed since the skill prescribes rules rather than a destructive or batch process.	4 / 5
Progressive Disclosure	The body is a concise overview that repeatedly and clearly signals a single one-level-deep reference (references/routing-patterns.md, verified to exist) containing the full code examples, making navigation easy.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, well-scoped description that clearly answers both what the skill does and when to use it with concrete Angular-specific triggers. It is tightly written in third person with minimal fluff.

Dimension	Reasoning	Score
Specificity	Names several concrete capabilities (lazy-loaded routes, functional guards, component input binding) but the 'what' clause leans on a single verb 'Configure' with sub-objects rather than multiple distinct action verbs, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly states both what ('Configure Angular Router with lazy-loaded routes, functional guards, and component input binding') and when ('Use when defining routes, lazy-loading features, creating route guards, or setting up resolvers') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural phrases an Angular developer would say ('defining routes', 'lazy-loading features', 'creating route guards', 'setting up resolvers') with good coverage, though a few natural synonyms (e.g. 'navigation', 'query params') are missing.	4 / 5
Distinctiveness Conflict Risk	Scoped narrowly to Angular Router configuration with domain-specific triggers, making conflict with unrelated skills unlikely.	5 / 5
	Total	18 / 20 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 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	14 / 16 Passed

Repository: HoangNguyen0403/agent-skills-standard
Path: skills/angular/angular-routing/SKILL.md
Commit: 405cdd5

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.