CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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.

66

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

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, high-signal reference skill: exact API guidance, explicit anti-patterns, and a clean split between the short overview body and two real one-level-deep reference files. Main improvement room is removing duplicated cleanup guidance and the meta 'Canonical response anchors' section.

DimensionReasoningScore

Conciseness

The body is lean, imperative, and free of explanations of concepts Claude already knows; it falls short of 5 due to small waste — "Never subscribe() without cleanup" is stated twice (Cleanup and Anti-Patterns) and the 'Canonical response anchors' section adds tokens with little operational value.

4 / 5

Actionability

Concrete, exact APIs are given throughout ("input.required<T>()", "output<T>() (v17.3+)", "model()", "toSignal()", "'[class.active]': 'isActive()'") with the right/wrong alternatives named; not a 5 because no complete inline code example appears in SKILL.md itself — full snippets are deferred to the reference files.

4 / 5

Workflow Clarity

As a pattern/reference skill with no multi-step or destructive operations, its directives are unambiguous ("ALWAYS use ChangeDetectionStrategy.OnPush. No exceptions.", "ALWAYS provide a tracking function"); it does not reach 5 because there is no guidance sequencing decisions such as when to apply the Smart/Dumb split.

4 / 5

Progressive Disclosure

The ~35-line body is well-sectioned and appropriately split: detail code lives in two clearly signaled, one-level-deep references (references/standalone-pattern.md and references/control-flow.md), both verified to exist and contain the expected focused content — matching the clear-overview top anchor.

5 / 5

Total

17

/

20

Passed

Description

83%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 description with an explicit what-and-when structure and concrete, domain-specific trigger phrases. Trigger coverage is good but lacks synonyms and file-extension terms that would push it to the top anchors.

DimensionReasoningScore

Specificity

The description lists several concrete capabilities ("Signals inputs", "OnPush change detection", "Smart/Dumb patterns"), matching the several-specific-actions anchor; it is not a 5 because "Control Flow" and "Smart/Dumb patterns" are noun phrases rather than actions and coverage has minor gaps.

4 / 5

Completeness

It explicitly answers both 'what' ("Build standalone Angular components with Signals inputs, OnPush change detection, Control Flow, and Smart/Dumb patterns") and 'when' with concrete trigger phrases ("Use when building standalone Angular components, implementing @if/@for control flow, applying OnPush change detection, or implementing Signals"), matching the top anchor.

5 / 5

Trigger Term Quality

The 'Use when' clause includes natural phrases users would say ("building standalone Angular components", "implementing @if/@for control flow", "applying OnPush change detection"), giving good keyword coverage; a 5 would require synonyms and file extensions (e.g., '.component.ts', 'presentational components') which are absent from the description itself.

4 / 5

Distinctiveness Conflict Risk

The Angular-components niche with distinct triggers (signals inputs, OnPush, @if/@for) keeps conflict risk low; it stays at 4 rather than 5 because a closely related sibling skill (e.g., Angular services or forms) could still overlap on generic 'Angular' phrasing.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

Reviewed

Table of Contents

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.