formik-patterns

Formik form handling with validation patterns. Use when building forms, implementing validation, or handling form submission.

Quality

91%

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

Quality

Content

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

The body is a lean, highly actionable pattern catalog with complete executable code and clear topical organization, including wrong-vs-correct anti-patterns. Its main gap is progressive disclosure: everything is inline in one long file with no references to split out detailed material.

Suggestions

Move the lengthy Validation Schemas reference and/or Multi-Step Forms detail into a references file (e.g. VALIDATION.md) and link to it from a concise overview, so SKILL.md stays a quick overview.

Add a short top-of-file "Quick start" summary pointing to each section so navigation is explicit.

Consider splitting the GraphQL submission and edit-form patterns into their own reference for one-level-deep disclosure.

Dimension	Reasoning	Score
Conciseness	The body is almost entirely executable code under terse headers with no padding explaining what Formik or forms are, matching the score-3 anchor "Lean and efficient; assumes Claude's competence; every token earns its place." It avoids the unnecessary prose that defines score 2.	3 / 3
Actionability	Every section provides complete, copy-paste-ready TSX/Yup code (e.g. useFormik setup, validation schemas, GraphQL submission, edit forms), matching the score-3 anchor for fully executable, specific examples. It is well above the pseudocode/vague level of scores 1-2.	3 / 3
Workflow Clarity	Although a patterns reference rather than a single linear workflow, content is clearly sequenced by topic and the Anti-Patterns section gives wrong-vs-correct feedback; the simple-skills scoring note allows a 3 for well-organized single-purpose references. It would drop to 2 only if validation checkpoints were missing for risky operations, which do not apply here.	3 / 3
Progressive Disclosure	No bundle files exist and all ~360 lines live inline in a single SKILL.md with no one-level-deep references, matching the score-2 anchor where "content that should be separate is inline." It is better organized than a monolithic wall (clear sections) so it is above score 1, but lacks the signaled external references required for score 3.	2 / 3
	Total	11 / 12 Passed

Description

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

The description is clear, trigger-rich, and distinctive, with an explicit Use-when clause answering both what and when. Its only weakness is specificity: it states the domain and concerns broadly rather than enumerating multiple concrete actions.

Suggestions

Replace the generic "form handling" with concrete actions, e.g. "Build, validate, and submit React forms with Formik and Yup; manage field state, multi-step flows, and GraphQL submission."

Add common natural variations users might say (e.g. "form validation", "Yup schema", "controlled inputs") to widen trigger coverage.

Dimension	Reasoning	Score
Specificity	The phrase "Formik form handling with validation patterns" names the domain (Formik) and a couple of concerns (handling, validation) but does not list multiple distinct concrete actions, matching the score-2 anchor "Names domain and some actions, but not comprehensive." It falls short of score 3, which requires listing several specific actions (e.g. extract, fill, merge), and exceeds score 1, which is purely vague/abstract.	2 / 3
Completeness	It answers both what ("Formik form handling with validation patterns") and when ("Use when building forms, implementing validation, or handling form submission") with an explicit trigger clause, matching the score-3 anchor. It is above score 2, where the when clause is missing or only implied.	3 / 3
Trigger Term Quality	"Use when building forms, implementing validation, or handling form submission" covers natural terms a user would actually say (building forms, validation, form submission). It is not jargon-heavy and matches the score-3 anchor for good coverage of natural user terms.	3 / 3
Distinctiveness Conflict Risk	Naming the specific library Formik plus focused triggers (form building, validation, submission) carves a clear niche unlikely to fire for unrelated skills, matching the score-3 anchor. It is more specific than the score-2 example "Works with document files".	3 / 3
	Total	11 / 12 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: ChrisWiles/claude-code-showcase
Path: .claude/skills/formik-patterns/SKILL.md
Commit: a95518f

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