angular-components

Build standalone Angular components with Signals inputs, OnPush change detection, Control Flow, and Smart/Dumb patterns. Use when building standalone Angular components, implementing @if/@for control flow, applying OnPush change detection, or implementing Signals in Angular components.

Quality

85%

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 tight, well-structured reference skill that offloads code examples to two real one-level-deep reference files and assumes Claude's Angular competence. Main gaps are a redundant 'Canonical response anchors' section and the absence of any inline complete component example or verification checkpoint.

Suggestions

Trim or remove the 'Canonical response anchors' section — it duplicates @if/@for, booleanAttribute, model(), and Smart (Container) already stated in the body, adding tokens without new guidance.

Inline one minimal copy-paste standalone component (signals input + output + OnPush) in the body so the guidance is fully executable without opening the references.

Add a brief verify checkpoint (e.g., confirm ChangeDetectionStrategy.OnPush is set and `ng build` passes) to give the pattern-application flow an explicit validation step.

Dimension	Reasoning	Score
Conciseness	Mostly lean bullet-point rules that assume Angular competence, but the 'Canonical response anchors' section re-lists @if/@for, booleanAttribute, model(), etc. already covered above, adding redundant tokens.	4 / 5
Actionability	Gives concrete API signatures (input.required<T>(), output<T>(), model(), toSignal(), takeUntilDestroyed()) and syntax, but the body has no complete copy-paste component example — those live only in the reference files.	4 / 5
Workflow Clarity	A well-organized pattern catalog with clear categorized sections rather than a multi-step workflow; the 'apply these patterns' intent is unambiguous, though no build/verify checkpoint is given (not needed since operations are non-destructive).	4 / 5
Progressive Disclosure	Clear overview in SKILL.md with well-signaled one-level-deep references to real files (references/standalone-pattern.md, references/control-flow.md); content is appropriately split for easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

92%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, third-person description that concretely states capabilities and gives explicit 'Use when' trigger guidance covering the main entry points. Only minor room for improvement in adding natural synonyms or file-extension triggers.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete capabilities — building standalone components, Signals inputs, OnPush change detection, Control Flow, and Smart/Dumb patterns — giving comprehensive coverage of the skill's scope.	5 / 5
Completeness	Explicitly answers both 'what' (Build standalone Angular components with...) and 'when' (Use when building..., implementing @if/@for, applying OnPush, or implementing Signals) with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural keyword coverage ('standalone Angular components', 'OnPush', 'Signals', '@if/@for') that developers would actually say, but missing synonyms or file-extension triggers like .component.ts/.component.html.	4 / 5
Distinctiveness Conflict Risk	Targets a clear niche — standalone Angular components with Signals/OnPush/control flow — with distinct triggers and minimal overlap risk against other skills.	5 / 5
	Total	19 / 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-components/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.