angular-forms
Angular forms: Signal Forms (experimental) and Reactive Forms. Trigger: When working with forms, validation, or form state in Angular.
Install with Tessl CLI
npx tessl i github:Yoizen/dev-ai-workflow --skill angular-forms85
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
75%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 description has good completeness with an explicit trigger clause and is distinctively scoped to Angular forms. However, it lacks concrete action verbs describing what the skill actually does (e.g., create, validate, manage) and could benefit from more natural trigger terms that users commonly use when working with Angular forms.
Suggestions
Add specific action verbs describing capabilities, e.g., 'Create and manage Angular forms using Signal Forms (experimental) and Reactive Forms. Handle validation, form controls, and form state.'
Expand trigger terms to include common user phrases like 'FormBuilder', 'form controls', 'form groups', 'ngModel', 'form validation errors', or 'form submission'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Angular forms) and mentions two specific form types (Signal Forms, Reactive Forms) plus validation and form state, but doesn't list concrete actions like 'create forms', 'validate inputs', or 'handle form submission'. | 2 / 3 |
Completeness | Explicitly answers both what (Angular forms with Signal Forms and Reactive Forms) and when (explicit 'Trigger: When working with forms, validation, or form state in Angular') with clear trigger guidance. | 3 / 3 |
Trigger Term Quality | Includes relevant keywords like 'forms', 'validation', 'form state', and 'Angular', but misses common variations users might say such as 'form controls', 'form groups', 'form validation errors', 'ngModel', or 'FormBuilder'. | 2 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to Angular framework specifically, with distinct form types (Signal Forms, Reactive Forms) that are Angular-specific. Unlikely to conflict with generic form skills or other framework form skills. | 3 / 3 |
Total | 10 / 12 Passed |
Implementation
87%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted skill that efficiently covers Angular forms with concrete, executable examples. The decision table provides clear guidance on form type selection, and code examples are complete and production-ready. The main gap is the lack of validation error handling patterns and feedback loops for form submission workflows.
Suggestions
Add a brief section showing how to display validation errors in templates (e.g., `@if (emailField.invalid && emailField.touched)`) to complete the form validation workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, providing only essential information. No unnecessary explanations of what forms are or how Angular works - it jumps straight to actionable code examples. | 3 / 3 |
Actionability | Provides fully executable, copy-paste ready code examples for both Signal Forms and Reactive Forms. Includes complete component definitions with imports, templates, and TypeScript logic. | 3 / 3 |
Workflow Clarity | The decision table at the top provides clear guidance on when to use each approach, but there are no validation checkpoints or error handling patterns shown. For form validation workflows, showing how to handle/display validation errors would improve this. | 2 / 3 |
Progressive Disclosure | Well-structured with a decision table upfront, followed by progressively detailed sections. External resources are clearly linked at the end. Content is appropriately sized for a single SKILL.md file. | 3 / 3 |
Total | 11 / 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.
- 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.