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. (triggers: FormBuilder, FormGroup, FormControl, Validators, reactive forms, typed forms)
83
78%
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 defines its scope within Angular reactive forms, provides explicit trigger guidance with a 'Use when...' clause, and lists concrete trigger terms that developers would naturally use. It uses proper third-person voice and is concise without being vague. The description effectively differentiates itself from general Angular or general forms skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Build typed reactive forms with strict FormGroup typing, custom validators, and nonNullable controls in Angular.' This names the domain (Angular) and several specific capabilities (typed reactive forms, strict FormGroup typing, custom validators, nonNullable controls). | 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') with additional trigger terms listed. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say, including explicit trigger terms: FormBuilder, FormGroup, FormControl, Validators, reactive forms, typed forms. These are exactly the terms Angular developers would use when seeking help with this topic. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with a clear niche: Angular typed reactive forms. The specific trigger terms (FormBuilder, FormGroup, FormControl, Validators) are unique to this domain and unlikely to conflict with other skills. The Angular framework context further narrows the scope. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill is well-structured and concise with good progressive disclosure to a reference file. However, it critically lacks any concrete code examples in the main body, making it more of an abstract guideline than an actionable skill. The absence of executable code for a code-centric skill (Angular typed reactive forms) significantly undermines its usefulness.
Suggestions
Add at least one complete, executable code example showing a typed FormGroup definition with FormBuilder (e.g., `fb.nonNullable.group({ name: ['', Validators.required] })`) directly in the skill body.
Include a concrete custom validator function example inline rather than deferring all code to the reference file.
Add a brief end-to-end mini-workflow: define form interface → create typed FormGroup → add validators → sync with store, with a small code snippet for each step.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient. It avoids explaining what reactive forms or FormGroup 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 specific commands. All guidance is descriptive ('use fb.nonNullable.group(...)') without showing a complete, copy-paste-ready example. The actual code is deferred entirely to a reference file. | 1 / 3 |
Workflow Clarity | The numbered sections provide a logical sequence (define typed forms → extract validators → ensure nonNullable), but there are no validation checkpoints or feedback loops. For a skill that's more of a pattern guide than a multi-step destructive process, this is acceptable but could be improved with a concrete workflow showing how to set up a form end-to-end. | 2 / 3 |
Progressive Disclosure | The skill provides a clear overview with well-signaled one-level-deep references to typed-forms.md. Content is appropriately split between the overview and the reference file, and navigation is straightforward. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- HoangNguyen0403/agent-skills-standard
- Commit
19a1140
- 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.