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

76%

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-5

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

The content is highly actionable with comprehensive executable examples and good section structure, but a 1000+ line monolith with a redundant Do's/Don'ts section and no bundle-based progressive disclosure drags down conciseness and progressive_disclosure. Workflow clarity is capped at 3 because form-submission workflows lack explicit validation checkpoints.

Suggestions

Collapse the Do's and Don'ts section into cross-references to the dedicated sections (or keep only items not covered elsewhere) to remove ~200 lines of duplicated nullable-default, mutation-typing, and auto-save guidance and improve conciseness.

Split the per-field component catalog and layout details into bundled reference files under references/ and link to them from the SKILL.md overview, so the main file stays an index and progressive_disclosure can score higher.

Add explicit validation/verification checkpoints to the Quick Reference Checklist (e.g., verify mutation success, check mutation.isError, confirm form.reset() resyncs pristine state) to lift workflow_clarity above the destructive-write cap.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean and example-driven with no basic-concept padding, but the extensive Do's and Don'ts section (~lines 811-1019) re-covers nullable defaults, mutation typing, form reset, auto-save cache, and default options already detailed above, and field examples repeat the same value/onChange pattern heavily, so it could be tightened well beyond 'minor'.	3 / 5
Actionability	It provides copy-paste-ready executable code across every field type, layout, validation, error-handling, and auto-save scenario, plus prop tables, a File References table, and a quick-reference checklist, fully covering the common cases.	5 / 5
Workflow Clarity	The Quick Reference Checklist sequences form creation, but form submission via network mutations has no explicit validation/verification checkpoints or error-recovery feedback loops, and the rubric caps destructive/batch write workflows without validation at 3.	3 / 5
Progressive Disclosure	No bundle files exist (references/scripts/assets absent), so this is a 1000+ line monolith; section headers and a File References table provide some structure, but field-by-field catalogs and layout details that could live in separate reference files are inlined, matching the 'some structure but content that should be separate is inline' anchor.	3 / 5
	Total	14 / 20 Passed

Description

87%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.

The description is strong, concise, and third-person with an explicit 'Use when' clause covering multiple natural triggers. It clearly answers both what the skill does and when to invoke it. Minor room for more enumerated actions and synonym coverage keeps specificity and trigger_term_quality at 4.

Dimension	Reasoning	Score
Specificity	Names the domain ('creating forms using Sentry's new form system') and lists several concrete capabilities ('forms, form fields, validation, or auto-save functionality'), but is framed as a guide rather than enumerating discrete actions like the comprehensive anchor, so it sits between 4 and 5.	4 / 5
Completeness	It explicitly answers both 'what' ('Guide for creating forms using Sentry's new form system') and 'when' with multiple concrete trigger phrases ('Use when implementing forms, form fields, validation, or auto-save functionality'), matching the anchor that requires both with concrete triggers.	5 / 5
Trigger Term Quality	Natural user-facing terms are present ('implementing forms', 'form fields', 'validation', 'auto-save functionality') with good coverage; it lacks synonyms and file-extension-style variations the 5 anchor expects, so it is below the comprehensive level.	4 / 5
Distinctiveness Conflict Risk	'Sentry's new form system' carves a clear niche with distinct triggers tied to a specific internal system, minimizing conflict risk with unrelated skills.	5 / 5
	Total	18 / 20 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 (1061 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

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

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