angular-forms

DEPRECATED - this skill is unmaintained. Use the official Angular skills at https://github.com/angular/skills instead. Build signal-based forms in Angular v21+ using the new Signal Forms API. Use for form creation with automatic two-way binding, schema-based validation, field state management, and dynamic forms. Triggers on form implementation, adding validation, creating multi-step forms, or building forms with conditional fields. Signal Forms are experimental but recommended for new Angular projects. Don't use for template-driven forms without signals or third-party form libraries like Formly or ngx-formly.

Quality

87%

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

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

This is a deliberately deprecated skill whose body has been stripped to a clean redirect: it concisely tells Claude to install the official replacement and remove the deprecated package, with copy-paste commands. It scores high on conciseness and structure because the minimal content is exactly what the situation calls for.

Dimension	Reasoning	Score
Conciseness	The body is extremely lean — a short deprecation banner with a single install command and one removal command — and assumes Claude's competence without restating known concepts; every token earns its place.	5 / 5
Actionability	Provides two concrete, executable commands ('npx skills add https://github.com/angular/skills' and 'npx skills remove analogjs/angular-skills') that are copy-paste ready, but offers no guidance on the deprecated skill's actual domain since guidance was intentionally removed.	4 / 5
Workflow Clarity	The deprecation workflow is clear and correctly ordered — install the replacement, remove the deprecated skill — with no destructive batch operation that would require a validation checkpoint; minor gaps only because there is no verification step after removal.	4 / 5
Progressive Disclosure	No bundle files exist (references/, scripts/, assets/ are absent) and the body is a well-organized single screen pointing to an external URL; for an under-50-line simple skill with no need for internal references, this structure is appropriate and easy to navigate.	5 / 5
	Total	18 / 20 Passed

Description

88%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 is highly specific, comprehensive, and clearly answers both what the skill does and when to use it, with concrete trigger phrases and thoughtful scope exclusions. Its main weakness is the prominent DEPRECATED prefix and experimental-status caveats, which add noise but do not obscure the capability statement.

Suggestions

Consider trimming the deprecation and experimental caveats from the description (the body already covers them) so the frontmatter reads as a clean capability/trigger statement.

Add a few common synonyms or extensions users might naturally say (e.g., 'form validation', 'Angular forms') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'Build signal-based forms', 'automatic two-way binding', 'schema-based validation', 'field state management', 'dynamic forms', 'multi-step forms', 'conditional fields' — giving comprehensive coverage of the skill's capabilities.	5 / 5
Completeness	Explicitly answers both 'what' (build signal-based forms with binding, validation, state management, dynamic forms) and 'when' ('Triggers on form implementation, adding validation, creating multi-step forms, or building forms with conditional fields') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Includes natural trigger phrases users would say ('form implementation', 'adding validation', 'creating multi-step forms', 'building forms with conditional fields') plus framework-specific terms, though it is missing some common synonyms and file extensions.	4 / 5
Distinctiveness Conflict Risk	The narrow niche of 'Signal Forms API' in 'Angular v21+' is fairly distinct, and explicit exclusions ('Don't use for template-driven forms without signals or ... Formly or ngx-formly') reduce conflict risk; minor overlap remains with other Angular form skills.	4 / 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: analogjs/angular-skills
Path: skills/angular-forms/SKILL.md
Commit: 18996fd

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