CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

85%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, tight skill body: concrete API-level directives, appropriate use of a single real reference file, and clear organization with anti-patterns. The only improvements are cosmetic — deduplicating the repeated reference link and tightening a couple of redundant bullets.

DimensionReasoningScore

Conciseness

The body is lean and directive ('never use untyped FormGroup', 'Sync `valueChanges` to stores using `takeUntilDestroyed()`'), but has trimmable redundancy: the same references/typed-forms.md link appears three times, section 2's second bullet restates the first, and 'This ensures form values always strings — avoids null in form values' repeats itself. Fits 'efficient; minor instances of over-explanation that could be trimmed' rather than the every-token-earns-its-place level of 5.

4 / 5

Actionability

Directives are concrete and API-specific — 'fb.nonNullable.group(...)', 'nonNullable: true', 'takeUntilDestroyed()', a named validators.ts file — with executable examples delivered in the linked reference file. Fits 'mostly executable guidance; concrete code or commands with minor gaps': not 5 because the body itself contains no complete code example, not 3 because the guidance is specific and executable rather than pseudocode.

4 / 5

Workflow Clarity

This is a simple, single-purpose pattern skill (~35 lines, no destructive or batch operations, so the validation cap does not apply). Per the simple-skill exception, the three directives are unambiguous and well-ordered (typed group → extracted validators → nonNullable controls), with an anti-patterns section as guardrails — matching the top anchor for a simple skill.

5 / 5

Progressive Disclosure

Scored against the actual bundle: one one-level-deep reference (references/typed-forms.md) that exists and delivers exactly what the links promise (typed FormGroup examples, standalone validator example), clearly signaled both in-context and in a References section, with the body kept as a concise overview. Matches 'clear overview with well-signaled one-level-deep references; easy navigation'.

5 / 5

Total

18

/

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 strong description: concrete, third-person, Angular-scoped, with an explicit 'Use when' trigger clause covering the main use cases. The only weaknesses are minor — slightly incomplete action coverage and trigger terms that could overlap a general Angular skill.

DimensionReasoningScore

Specificity

Lists several concrete third-person actions — 'Build typed reactive forms with strict FormGroup typing, custom validators, and nonNullable controls' — matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because coverage of the forms domain (e.g., value access, submission patterns) is not comprehensive, and short of 3 because it names far more than 1-2 actions.

4 / 5

Completeness

Explicitly answers both: 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. This matches the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Contains natural terms users would say — 'typed reactive forms', 'custom validators', 'form control patterns', 'FormGroup', 'in Angular' — giving good keyword coverage. A few natural variants are missing ('form validation', 'Angular forms' as a phrase, file extensions), so it fits anchor 4 rather than the comprehensive synonym coverage of 5, and is clearly above the sparse coverage of 3.

4 / 5

Distinctiveness Conflict Risk

The niche is clear (Angular typed reactive forms), but phrases like 'custom validators' and 'form control patterns' could minorly overlap with a generic Angular or validation skill. Fits 'mostly distinct; minor overlap risk' rather than the minimal-conflict clarity of 5.

4 / 5

Total

17

/

20

Passed

Validation

87%

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

CriteriaDescriptionResult

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

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.