angular

Modern Angular (v20+) expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns.

Quality

37%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

—

The risk profile of this skill

Fix and improve this skill with Tessl

tessl review fix ./skills/angular/SKILL.md

Quality

Content

42%Scale 1-3

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

This skill reads like a comprehensive Angular tutorial or documentation mirror rather than a focused skill file. While the code examples are excellent and fully executable, the content is far too verbose for a SKILL.md — it explains concepts Claude already knows extensively and packs everything into a single monolithic file. The workflow instructions are too vague to guide Claude through complex multi-step operations like SSR setup or migration.

Suggestions

Reduce the SKILL.md to a concise overview (~50-100 lines) covering key patterns and decision points, moving detailed code examples into separate bundle files (e.g., signals.md, ssr.md, zoneless.md, testing.md) with clear references.

Remove explanatory content Claude already knows (what Signals are, what Standalone Components are, basic DI concepts) and focus only on Angular-specific gotchas, non-obvious patterns, and decision criteria.

Add explicit workflow steps with validation checkpoints for common multi-step tasks like 'migrating to Zoneless' or 'adding SSR to an existing app', including verification commands (ng build, ng test) at each stage.

Remove the version timeline with future dates (Angular 21, 22) as this is time-sensitive information that will become stale and may be inaccurate.

Dimension	Reasoning	Score
Conciseness	This is extremely verbose at ~500+ lines. It explains many concepts Claude already knows (what Signals are, what Standalone Components are, what SSR is, how DI works). The version timeline with future dates, extensive comparison tables, and comprehensive API coverage reads more like a tutorial/documentation mirror than a skill file. Most of this content is readily available in Claude's training data.	1 / 3
Actionability	The code examples are concrete, executable, and copy-paste ready throughout. Every section includes real TypeScript/Angular code with proper imports, decorators, and usage patterns. Examples cover components, services, routing, testing, and configuration.	3 / 3
Workflow Clarity	The top-level 'Instructions' section lists 4 steps but they are vague ('Assess the Angular version', 'Apply modern patterns'). There are no explicit validation checkpoints or feedback loops for multi-step processes like migration or SSR setup. The skill lacks clear sequencing for complex operations like transitioning to Zoneless or implementing SSR.	2 / 3
Progressive Disclosure	This is a monolithic wall of text with 11 major sections all inline. There are no bundle files to reference, yet the content would greatly benefit from being split into separate files (e.g., signals.md, ssr.md, testing.md). The external links at the bottom are to Angular docs, not to organized bundle files. The SKILL.md should be an overview pointing to detailed materials, not a comprehensive reference document.	1 / 3
	Total	7 / 12 Passed

Description

32%Scale 1-3

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 identifies a clear technical domain (modern Angular) and lists relevant sub-topics, but it reads more like a resume bullet point than a skill selection guide. It lacks concrete actions (what it does) and completely omits trigger guidance (when to use it), making it difficult for Claude to reliably select this skill from a large pool.

Suggestions

Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks about Angular components, Angular Signals, zoneless change detection, Angular SSR, or mentions .component.ts files.'

Replace the expertise-framing ('expert with deep knowledge of') with concrete actions, e.g., 'Builds and refactors Angular v20+ applications using Signals, Standalone Components, and zoneless architecture. Configures SSR and hydration.'

Include common user-facing terms and file patterns like 'Angular app', 'ng generate', 'angular.json', '.component.ts', 'Angular CLI' to improve trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (Angular) and lists several specific technical areas (Signals, Standalone Components, Zoneless applications, SSR/Hydration, reactive patterns), but describes expertise rather than concrete actions. It says what it knows, not what it does.	2 / 3
Completeness	Describes 'what' at a high level (Angular expertise areas) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent, which per the rubric should cap completeness at 2, and the 'what' itself is weak (describes knowledge areas, not actions), warranting a 1.	1 / 3
Trigger Term Quality	Includes relevant Angular-specific keywords like 'Signals', 'Standalone Components', 'Zoneless', 'SSR/Hydration', and 'v20+' that users might mention, but misses common user phrases like 'Angular app', 'component creation', 'Angular routing', 'dependency injection', or file extensions like '.ts', '.component.ts'.	2 / 3
Distinctiveness Conflict Risk	The specificity to Angular v20+ and particular features like Signals and Zoneless helps distinguish it from generic frontend skills, but 'reactive patterns' and 'SSR/Hydration' could overlap with other framework skills (e.g., React, Next.js). Without clear trigger boundaries, there's moderate conflict risk.	2 / 3
	Total	7 / 12 Passed

Validation

81%

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 — 9 / 11 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (824 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

Repository: popey/claude-code-skills
Path: skills/angular/SKILL.md
Commit: a5a6601

Reviewed: 5 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.