migrate-frontend-forms

Guide for migrating forms from the legacy JsonForm/FormModel system to the new TanStack-based form system.

Quality

64%

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/migrate-frontend-forms/SKILL.md

Quality

Content

71%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 thorough, executable before/after examples and a strong migration checklist including verification. Its main weaknesses are overall length/redundancy and the absence of any progressive disclosure — all detail lives in one large file.

Suggestions

Move the per-feature Old/New detail blocks into a separate reference file (e.g. references/feature-migrations.md) and keep SKILL.md as the mapping table + checklist + pointers to reduce length and improve progressive disclosure.

Trim repeated boilerplate across the Old/New examples by sharing a single canonical AutoSaveForm/useScrapsForm skeleton and showing only the varying part per feature.

Promote the Migration Checklist earlier or anchor each feature section to its checklist item so the workflow sequencing is explicit alongside the reference material.

Dimension	Reasoning	Score
Conciseness	The body is dense with earned, actionable content and avoids explaining concepts Claude already knows, but at ~700 lines the repeated Old/New code blocks for every feature introduce mild redundancy and length that could be tightened.	3 / 5
Actionability	It provides copy-paste-ready TSX examples with specific imports, concrete mutation patterns, and an exact command ("pnpm run extract-form-fields") covering the common migration cases comprehensively.	5 / 5
Workflow Clarity	A detailed Migration Checklist sequences the work and includes a verification checkpoint (regenerating the field registry), but the main body is organized by feature rather than as a strict ordered workflow, leaving minor sequencing gaps.	4 / 5
Progressive Disclosure	The file is well-sectioned with headers, a mapping table, and a checklist, but it is a single ~700-line monolith with no skill bundle files or one-level-deep references to split out the detailed feature mappings.	3 / 5
	Total	15 / 20 Passed

Description

57%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 precise about its niche and clearly states what it does, but it is a single declarative sentence with no "Use when..." trigger guidance and limited action coverage. Adding explicit trigger phrasing and the new-system component names would lift completeness and trigger quality.

Suggestions

Add a "Use when..." clause naming the migration trigger, e.g. "Use when migrating Sentry settings forms from JsonForm/FormModel to TanStack AutoSaveForm or useScrapsForm."

Include the new-system component names (AutoSaveForm, useScrapsForm) as trigger terms so the description matches how developers actually refer to the target system.

Optionally enumerate a couple of concrete migration actions (e.g. "convert field configs to JSX, remap error handling, preserve FormSearch indexing") to raise specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain and one concrete action — "migrating forms from the legacy JsonForm/FormModel system to the new TanStack-based form system" — but lists only a single action rather than multiple specific concrete actions.	3 / 5
Completeness	It gives a clear "what" (a migration guide from one form system to another) but has no "Use when..." clause or equivalent explicit trigger guidance, which caps completeness at 3 per the rubric.	3 / 5
Trigger Term Quality	It surfaces relevant system names (JsonForm, FormModel, TanStack) that a developer would mention, but omits the new-system component triggers (AutoSaveForm, useScrapsForm) and common synonyms a user might naturally say.	3 / 5
Distinctiveness Conflict Risk	The unique, codebase-specific system names (JsonForm/FormModel vs TanStack) carve out a clear niche with minimal risk of triggering for an unrelated skill.	5 / 5
	Total	14 / 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 (717 lines); consider splitting into references/ and linking	Warning

	Total	15 / 16 Passed

Repository: getsentry/sentry
Path: .agents/skills/migrate-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.