angular

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

Quality

58%

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

Fix and improve this skill with Tessl

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

Quality

Content

55%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.

The body is a lean, well-organized overview that delegates depth to a real one-level-deep reference with sensible loading guidance, and its scope/anti-scope lists are concrete. Its weaknesses are the absence of any task workflow or validation checkpoints in the body itself and the lack of inline actionable guidance, all of which is deferred to a single monolithic guide file.

Suggestions

Surface the core procedure and its validation checkpoint in the body (e.g., a short numbered list: assess version → apply patterns → implement → 'Validate with build and tests') instead of deferring the entire workflow to the guide by reference.

Add a minimal quick-start snippet or command inline (e.g., the CLI commands for enabling zoneless or SSR setup) so the body carries some executable guidance.

Split the 800-line detailed-guide.md into per-topic reference files (signals.md, zoneless.md, ssr.md, etc.) and link each from the 'When to Use' bullets so focused loading does not require scanning headers.

Dimension	Reasoning	Score
Conciseness	The body is lean with no explanation of concepts Claude already knows and no padding; every section carries information. It misses anchor 5 only because of minor duplication — the opening line "Master modern Angular development with Signals, Standalone Components, Zoneless applications, SSR/Hydration..." restates the frontmatter description nearly verbatim, and the 'When to Use' bullets partially re-enumerate the same topics.	4 / 5
Actionability	There is concrete navigation guidance ("Read [the detailed guide](references/detailed-guide.md) before executing this skill", "For focused work, load the relevant sections") and specific redirects ("use `angular-migration` skill", "use `typescript-expert` skill"), but the body itself contains no executable instructions, commands, or code examples — the actionable detail is entirely deferred to the reference. This matches anchor 3: some concrete guidance but incomplete in the body.	3 / 5
Workflow Clarity	The body contains no task sequence at all — no steps, no numbered workflow, and no validation checkpoints stated in the SKILL.md body itself; it only says to treat the guide's "safety, prerequisites, and validation requirements as mandatory" by reference. This sits between anchor 1 (steps missing) and anchor 3 (steps listed): a rough directive ('read the guide first, follow its procedure') exists, but the multi-step sequence and checkpoints are not written here.	2 / 5
Progressive Disclosure	The structure is good: a concise overview body with a single well-signaled, one-level-deep reference (references/detailed-guide.md, which exists, is 801 lines with clear section headers, and contains no nested .md references), plus explicit loading guidance. It misses anchor 5 because all ten topic areas live in one monolithic reference file with no per-topic links or section-level navigation from SKILL.md ("load the relevant sections" without saying where they are), leaving a minor organization gap.	4 / 5
	Total	13 / 20 Passed

Description

61%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.

The description is specific and distinctive about its modern Angular domain, but it describes expertise rather than concrete actions and completely lacks a 'when to use' trigger clause, which caps its completeness. Adding an explicit "Use when..." clause and action verbs would move it toward the top anchors.

Suggestions

Add an explicit trigger clause, e.g. "Use when building or upgrading Angular v20+ apps, implementing Signals or Standalone Components, enabling Zoneless change detection, or configuring SSR/hydration."

Replace the persona framing ("expert with deep knowledge of") with concrete actions such as "Builds, migrates, and optimizes Angular v20+ applications using Signals, Standalone Components, Zoneless rendering, and SSR/Hydration."

Include natural user phrasings and synonyms (e.g., 'Angular 20', 'NgModules', 'hydration', 'RxJS') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	The description names the domain and several concrete capability areas ("Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns") but describes knowledge ("expert with deep knowledge of") rather than actions — no verbs for what the skill actually does, matching anchor 3 (domain plus concrete topics, but not comprehensive actions). It is above anchor 2 ('Processes PDF files'-level genericity) because the enumerated topics are specific, but below anchor 4, which requires several specific actions.	3 / 5
Completeness	The 'what' is reasonably clear via the enumerated modern-Angular topics, but the 'when' is entirely absent — there is no "Use when..." or equivalent trigger clause, which caps completeness at 3 per the judging guidelines. It is not a 2 because the 'what' is more specific than the vague-'what' anchor ("Use when working with documents"), and not a 4 because no usage conditions are stated even implicitly.	3 / 5
Trigger Term Quality	"Angular", "Signals", "Standalone Components", "Zoneless", "SSR/Hydration" are terms users working on modern Angular would naturally say, giving good keyword coverage. It falls short of anchor 5 because common variations and synonyms are missing (e.g., 'Angular 20', 'NgModules', 'hydration', 'RxJS', 'change detection'), and no file extensions or 'when' phrasing appear.	4 / 5
Distinctiveness Conflict Risk	"Modern Angular (v20+)" carves a clear niche with distinct technical triggers, so it is mostly distinguishable from generic skills. It is below anchor 5 because closely related skills (e.g., an AngularJS migration skill or a general TypeScript skill) would overlap on terms like 'Angular' and 'reactive patterns', and no trigger phrasing further separates them.	4 / 5
	Total	14 / 20 Passed

Validation

93%

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

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: sickn33/agentic-awesome-skills
Path: skills/angular/SKILL.md
Commit: c26b706

Reviewed: 1 hour 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.