angular

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

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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 rich, highly actionable Angular reference with executable code throughout, but it is an oversized monolith with concept-explaining prose and no file-based progressive disclosure, and its top-level workflow lacks explicit validation checkpoints.

Suggestions

Move the deeper per-topic references (Signals, SSR/hydration, state management, testing) into separate files under references/ and keep SKILL.md as a concise overview with one-level-deep links.

Tighten or remove introductory sentences that explain well-known concepts (what Signals/Standalone/Zoneless are) and let the code carry the meaning.

Make the Instructions workflow explicit with concrete validation commands and a fix-and-retry feedback loop rather than the generic "Validate with build and tests".

Dimension	Reasoning	Score
Conciseness	The ~800-line body is dominated by useful code, but each section opens with explanatory prose about concepts Claude already knows (e.g. "Signals are Angular's fine-grained reactivity system…", "Standalone components are self-contained…"), and the overall length could be tightened.	2 / 3
Actionability	It provides abundant executable TypeScript with imports, concrete commands like `ng add @angular/ssr`, and copy-paste-ready patterns across signals, routing, DI, SSR, and testing.	3 / 3
Workflow Clarity	The Instructions section lists a numbered sequence but validation is generic ("Validate with build and tests") with no explicit commands or error-recovery feedback loop, leaving checkpoints implicit.	2 / 3
Progressive Disclosure	No bundle files exist (references/scripts/assets all absent) and the 800-line reference is a single monolithic SKILL.md with all 11 sections inline — content that would benefit from being split into separate reference files.	2 / 3
	Total	9 / 12 Passed

Description

57%

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 clearly scopes a modern-Angular niche and lists relevant sub-domains, but it is capability-flavored ("expert with deep knowledge of") rather than action-oriented and omits any explicit "Use when…" trigger guidance.

Suggestions

Replace the capability framing with concrete actions, e.g. "Builds and migrates Angular v20+ apps using Signals, Standalone components, Zoneless change detection, and SSR/hydration."

Add an explicit trigger clause such as "Use when building or modernizing Angular v20+ applications, adopting Signals, or configuring Zoneless/SSR."

Trim the over-claiming "expert with deep knowledge of" phrasing in favor of what the skill actually does.

Dimension	Reasoning	Score
Specificity	Names a concrete domain and several sub-areas ("Signals, Standalone Components, Zoneless applications, SSR/Hydration"), but lists no concrete actions/verbs and leads with the mildly over-claiming phrase "expert with deep knowledge of".	2 / 3
Completeness	It states what the skill covers (modern Angular domains) but provides no explicit "when to use" trigger clause, which caps completeness at 2 per the rubric guideline.	2 / 3
Trigger Term Quality	Includes relevant terms a user might say ("Angular", "Signals", "SSR/Hydration") but offers no "Use when…" phrasing and lacks common variations, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The "Modern Angular (v20+)" scope is a clear, narrow niche unlikely to trigger for unrelated skills, even though it could overlap with adjacent Angular skills.	3 / 3
	Total	9 / 12 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
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	14 / 16 Passed

Repository: boisenoise/skills-collections
Commit: f36337d

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