angular

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

1.32x

Quality

60%

Does it follow best practices?

Impact

94%

1.32x

Average score across 3 eval scenarios

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/AI-Agents-Safe-Coding-Skills/skills/angular/SKILL.md

The canonical home for this skill is angular in sickn33/agentic-awesome-skills

Quality

Content

65%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 content is highly actionable with comprehensive, executable Angular v20+ code examples, but it is long, includes time-sensitive version dating and some over-explanation, inlines material that belongs in separate reference files, and offers only a vague top-level workflow.

Suggestions

Move the detailed per-topic API references (forms, testing, state management) into separate reference files and link to them from SKILL.md to improve progressive disclosure.

Quarantine version-specific dates and "coming in v22+" notes into a clearly labeled version/deprecated section so time-sensitive claims don't dilute the evergreen guidance.

Tighten the Instructions workflow into explicit, ordered steps with a concrete validation checkpoint (e.g. "Run `ng build` and the affected `.spec.ts` before considering the task done").

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient with extensive runnable code, but it carries explanatory prose Claude already knows ("Signals are Angular's fine-grained reactivity system...", "Standalone components are self-contained...") and time-sensitive version/date claims (the version timeline with Q2 2025/Q4 2025/Q2 2026 and "Coming in v22+") that are not placed in a deprecated/old-patterns section, which penalizes conciseness.	3 / 5
Actionability	It provides many complete, copy-paste-ready TypeScript examples covering Signals, inputs/outputs, queries, routing, DI, state, forms, SSR/hydration, and testing — concrete and executable across the common cases.	5 / 5
Workflow Clarity	The "Instructions" section lists a rough sequence (Assess → Apply modern patterns → Implement → Validate with build and tests) but the steps are high-level and vague with only an implicit validation checkpoint, fitting the anchor where steps are listed but validation is implicit and checkpoints missing.	3 / 5
Progressive Disclosure	The body has well-organized section headers, but with no references/scripts/assets bundle present, ~800 lines of detailed API patterns, forms, and testing guidance are inlined in SKILL.md rather than split into one-level-deep reference files, matching the anchor where structure exists but content that should be separate is inline.	3 / 5
	Total	14 / 20 Passed

Description

56%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 names a clear niche and strong natural trigger terms for modern Angular, but it describes expertise rather than concrete actions and omits any explicit "Use when..." guidance, capping completeness and specificity.

Suggestions

Rewrite to lead with concrete actions, e.g. "Builds, migrates, and optimizes Angular v20+ applications using Signals, Standalone Components, and Zoneless change detection."

Add an explicit trigger clause: "Use when building or modernizing Angular v20+ apps, adopting Signals, or configuring SSR/hydration."

Avoid framing as "expert with deep knowledge" which states capability abstractly rather than what the skill does.

Dimension	Reasoning	Score
Specificity	The phrase "expert with deep knowledge of Signals, Standalone Components, Zoneless applications, SSR/Hydration, and reactive patterns" names the Angular domain and several sub-areas but describes knowledge rather than concrete actions (no verbs like build, migrate, configure), matching the anchor where the domain is named but actions are minimal or generic.	2 / 5
Completeness	It states a clear "what" (modern Angular expert across named sub-domains) but has no "Use when..." clause or equivalent explicit trigger guidance, so per the judging guidelines completeness is capped at 3.	3 / 5
Trigger Term Quality	It surfaces natural terms users would say — "Angular", "Signals", "Standalone Components", "SSR/Hydration", "Zoneless" — giving good keyword coverage, though a few common variations (e.g. "change detection", "dependency injection", file/CLI triggers) are missing.	4 / 5
Distinctiveness Conflict Risk	"Modern Angular (v20+)" carves a clear niche with distinct triggers and low conflict risk, with only minor overlap risk against closely related skills (e.g. typescript-expert, angular-migration).	4 / 5
	Total	13 / 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
skill_md_line_count	SKILL.md is long (819 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: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: plugins/AI-Agents-Safe-Coding-Skills/skills/angular/SKILL.md
Commit: 900c504

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