angular-forms

Build typed reactive forms with strict FormGroup typing, custom validators, and nonNullable controls in Angular. Use when implementing typed reactive forms, custom validators, or form control patterns.

Quality

79%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/angular/angular-forms/SKILL.md

Quality

Content

75%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 well-structured, lean guidance skill that delegates executable examples to a real one-level-deep reference and covers its niche with specific API-level directives. It stops short of top marks due to cryptic filler, no inline executable example, and a single shared reference file.

Suggestions

Remove or clarify the cryptic "Canonical response anchors: separate file" line, which adds no actionable guidance.

Tighten the redundant validator wording ("Name the validator module as a separate file ... in the response and keep validation out of the component class") to a single concrete directive.

Add a brief inline typed-FormGroup snippet or split the single reference into topic-specific files (typed-forms.md, validators.md) so each section links to a focused reference.

Dimension	Reasoning	Score
Conciseness	The body is lean bullet-style guidance that assumes Angular competence and avoids explaining reactive-forms basics, but phrasing like "Name the validator module as a separate file ... in the response" and the cryptic "Canonical response anchors: separate file" line could be trimmed.	4 / 5
Actionability	Specific API names (fb.nonNullable.group(...), takeUntilDestroyed(), FormGroup<T>, nonNullable: true) give concrete direction, with executable examples delegated to the real reference file; minor gaps such as the valueChanges sync not being shown keep it just below fully copy-paste ready.	4 / 5
Workflow Clarity	Three numbered guidance sections plus an Anti-Patterns block are clearly sequenced and easy to follow, and as a rules-style skill it needs no validation checkpoints; it is not a 5 only because the guidance is directive rather than a tightly ordered procedure.	4 / 5
Progressive Disclosure	The overview lives in SKILL.md with executable detail one level deep in references/typed-forms.md (a real file), signaled both inline and in a References section; minor gaps are the cryptic "Canonical response anchors" section and all three sections pointing to the same single reference rather than topic-specific files.	4 / 5
	Total	16 / 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 concise, third-person description that clearly answers both what the skill does and when to use it, with concrete capability statements and natural trigger terms. It is held back from a perfect score by overlapping action descriptions and minor overlap risk with adjacent Angular skills.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — "strict FormGroup typing, custom validators, and nonNullable controls" — but the actions overlap within the typed-forms niche, leaving minor coverage gaps rather than comprehensive breadth.	4 / 5
Completeness	It explicitly states what ("Build typed reactive forms with strict FormGroup typing, custom validators, and nonNullable controls in Angular") and when ("Use when implementing typed reactive forms, custom validators, or form control patterns") with concrete trigger phrases.	5 / 5
Trigger Term Quality	"typed reactive forms", "custom validators", and "form control patterns" are natural developer phrases, though common synonyms and specific API names (FormBuilder, FormGroup) that appear in the metadata triggers are omitted from the description.	4 / 5
Distinctiveness Conflict Risk	The Angular typed-forms niche is clearly delimited, but generic trigger phrases like "form control patterns" create minor overlap risk with a broader Angular or forms skill.	4 / 5
	Total	17 / 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-forms/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.