generate-frontend-forms

Guide for creating forms using Sentry's new form system. Use when implementing forms, form fields, validation, or auto-save functionality.

Quality

66%

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 ./.agents/skills/generate-frontend-forms/SKILL.md

Quality

Content

65%Weight 40%Scale 1-3

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A highly actionable, well-structured reference with excellent executable examples, weakened mainly by length/redundancy and the absence of any progressive-disclosure file split.

Suggestions

Remove or consolidate the Do's and Don'ts section, which duplicates the main sections, to tighten conciseness.

Split the field component catalog and/or the Do's and Don'ts into a reference file (e.g., FIELDS.md) referenced from SKILL.md to improve progressive disclosure.

Add an explicit gated workflow (e.g., define schema -> validate on submit -> map server errors with setFieldErrors -> reset on success) with validation checkpoints to lift workflow clarity.

Dimension	Reasoning	Score
Conciseness	The guide stays domain-specific (no padding about what forms or Zod are), but at ~1000 lines the Do's and Don'ts section rehashes material already covered in the main sections, so it could be tightened.	2 / 3
Actionability	It provides abundant complete, executable TSX examples with imports and props for every field type and pattern, making the guidance copy-paste ready.	3 / 3
Workflow Clarity	A clear Quick Reference Checklist plus setFieldErrors error recovery gives a usable sequence, but validation checkpoints are implicit (zod runs automatically) rather than an explicit gated validate-fix-proceed workflow.	2 / 3
Progressive Disclosure	Sections are well-organized with clear headers and a File References table, but the skill is a monolithic single file with content (field catalog, layouts, do's/don'ts) that could be split into reference files, and no bundle files exist.	2 / 3
	Total	9 / 12 Passed

Description

67%Weight 40%Scale 1-3

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 solid description with an explicit 'Use when' trigger covering both what and when, though its action list and trigger-term coverage are broad rather than sharply specific.

Suggestions

List more concrete actions (e.g., schema-based validation with Zod, server error mapping, confirmation dialogs for dangerous settings) to lift specificity toward level 3.

Broaden trigger terms with natural variations users actually say, such as 'Zod schema', 'form inputs', or 'settings auto-save'.

Tie the 'Use when' clause more tightly to Sentry (e.g., 'Use when building Sentry forms…') to reduce overlap with generic form skills.

Dimension	Reasoning	Score
Specificity	It names the domain ("Sentry's new form system") and several actions ("creating forms", "form fields", "validation", "auto-save"), but the framing "Guide for creating forms" is general rather than a list of sharply concrete operations like the level-3 anchor.	2 / 3
Completeness	It explicitly states what it does ("Guide for creating forms using Sentry's new form system") and when to use it ("Use when implementing forms, form fields, validation, or auto-save functionality"), satisfying both what and when with an explicit trigger.	3 / 3
Trigger Term Quality	It includes natural terms users would say ("forms", "form fields", "validation", "auto-save"), but misses common variations such as Zod, schema, inputs, or settings, matching the level-2 anchor of relevant keywords with gaps.	2 / 3
Distinctiveness Conflict Risk	The "Sentry's new form system" qualifier gives a clear niche, but the trigger terms themselves (forms, validation, auto-save) are generic and could overlap with other form-related skills.	2 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (1012 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: getsentry/sentry
Path: .agents/skills/generate-frontend-forms/SKILL.md
Commit: b4b3565

Reviewed: 2 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.