angular-core

Angular core patterns: standalone components, signals, inject, control flow, zoneless. Trigger: When creating Angular components, using signals, or setting up zoneless.

Quality

88%

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

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

An efficient, highly actionable Angular patterns reference that assumes Claude's competence and surfaces concrete code for every rule. It is not a sequenced workflow skill, so workflow clarity and single-file density keep those dimensions at 4.

Dimension	Reasoning	Score
Conciseness	Lean and code-forward with brief section headers and ✅/❌ patterns; it assumes Angular competence and avoids explaining concepts Claude already knows.	5 / 5
Actionability	Copy-paste-ready TypeScript/HTML examples plus a concrete command ('npm uninstall zone.js') cover the common modern-Angular cases with clear do/don't contrasts.	5 / 5
Workflow Clarity	Each pattern is unambiguous with helpful decision tables ('When to Use What', signals-vs-RxJS), but there is no multi-step sequenced workflow needing validation checkpoints.	4 / 5
Progressive Disclosure	Well-organized REQUIRED sections with no nested references and one-level-deep external doc URLs; the single-file body is dense but appropriately cohesive since no bundle files exist.	4 / 5
	Total	18 / 20 Passed

Description

87%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 pairs a concrete capability list with explicit trigger guidance and a distinct Angular niche. Tightening trigger synonyms and converting pattern nouns to action verbs would round it out.

Dimension	Reasoning	Score
Specificity	Lists several concrete pattern names ('standalone components, signals, inject, control flow, zoneless') but as noun phrases rather than action verbs, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers both what ('Angular core patterns: ...') and when ('Trigger: When creating Angular components, using signals, or setting up zoneless') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Natural triggers ('creating Angular components, using signals, setting up zoneless') are present and user-aligned, but synonyms like 'modern Angular', 'Angular 17+', or 'change detection' are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a clear Angular-specific niche with distinct, framework-scoped triggers, so overlap with other skills is minimal.	5 / 5
	Total	18 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: Gentleman-Programming/Gentleman-Skills
Path: curated/angular/core/SKILL.md
Commit: c8036a3

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.