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.
78
75%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/angular/angular-forms/SKILL.mdQuality
Discovery
100%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a strong skill description that clearly identifies its niche within Angular typed reactive forms. It lists specific concrete capabilities, includes natural developer-facing trigger terms, and provides an explicit 'Use when' clause. The description is concise, uses third-person voice, and would be easily distinguishable from other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Build typed reactive forms', 'strict FormGroup typing', 'custom validators', and 'nonNullable controls'. These are concrete, well-defined Angular concepts. | 3 / 3 |
Completeness | Clearly answers both 'what' (build typed reactive forms with strict FormGroup typing, custom validators, nonNullable controls) and 'when' (explicit 'Use when implementing typed reactive forms, custom validators, or form control patterns'). | 3 / 3 |
Trigger Term Quality | Includes strong natural keywords that Angular developers would use: 'typed reactive forms', 'FormGroup', 'custom validators', 'nonNullable controls', 'form control patterns'. These are terms developers naturally use when seeking help with Angular forms. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific to Angular's typed reactive forms ecosystem with distinct triggers like 'FormGroup typing', 'nonNullable controls', and 'reactive forms'. Unlikely to conflict with general form-building or other framework skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
50%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is concise and well-structured at a high level, but critically lacks any concrete code examples in the main body, making it largely non-actionable on its own. The entire burden of executable guidance is pushed to a single reference file, and the skill would benefit greatly from at least one inline typed FormGroup example and a validator snippet.
Suggestions
Add at least one inline executable code example showing a typed FormGroup<T> definition with nonNullable controls — this is the core skill and should not require following a reference link.
Include a concrete standalone validator function example directly in the skill body (e.g., a password match validator) to make section 2 actionable.
Differentiate the two references to typed-forms.md by linking to specific sections or adding brief descriptions of what each link covers (e.g., 'See typed-forms.md § FormGroup typing' vs '§ Custom validators').
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what reactive forms or FormGroups are, assumes Claude's Angular competence, and every line provides actionable guidance or constraints. | 3 / 3 |
Actionability | There are no concrete code examples, no executable snippets, and no copy-paste ready patterns. All guidance is abstract (e.g., 'Define typed FormGroup<T>' and 'Create standalone validator functions') with actual examples deferred entirely to a reference file. | 1 / 3 |
Workflow Clarity | The numbered sections provide a reasonable sequence (define typed forms → extract validators → ensure nonNullable), but there are no validation checkpoints, no feedback loops, and no concrete steps for verifying correctness of form implementations. | 2 / 3 |
Progressive Disclosure | References to typed-forms.md are present and one-level deep, which is good. However, the same reference is linked twice for different purposes without clear signaling of what each section contains, and the main file lacks even a minimal inline example to orient the reader before following references. | 2 / 3 |
Total | 8 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
4c72e76
- 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.