create-creation-form

Use when: scaffolding a creation form drawer with Formik validation and a Relay mutation for a new entity

Quality

77%

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 ./.github/skills/create-creation-form/SKILL.md

Quality

Content

76%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 lean and actionable with a clear step sequence, but its workflow for a store-mutating Relay operation lacks any error handling or post-mutation verification, capping workflow clarity. Minor executable gaps (undefined Props type, missing imports, t/t_i18n inconsistency) keep actionability just below the top.

Suggestions

Add a validation/feedback loop after the mutation — an onError handler that resets submitting and surfaces the error, plus a note to verify the entity appears in the list — to lift workflow clarity above 3.

Complete the code example: show the imports and define the Props type, and reconcile the t() vs t_i18n() i18n helper inconsistency.

Dimension	Reasoning	Score
Conciseness	The body is lean with no concept explanations or padding — only a prerequisites list, one-line step intros, and two minimal code blocks, every token earning its place and assuming Claude's competence.	5 / 5
Actionability	Provides concrete, mostly copy-paste-ready TSX covering the mutation, Yup schema, and component structure, but has minor gaps: the Props type and imports are undefined and the validation uses t() while the component uses t_i18n().	4 / 5
Workflow Clarity	Steps are clearly sequenced (Step 0, 1, 2) but the skill performs a Relay write mutation with no error handling (onError) or verification that the entity was created, so the destructive/batch feedback-loop cap of 3 applies.	3 / 5
Progressive Disclosure	Well organized into Prerequisites and a numbered Procedure with no nested references and a single self-contained task; slightly over the 50-line simple-skill threshold, so it sits just below the top anchor.	4 / 5
	Total	16 / 20 Passed

Description

78%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 specific, third-person, and clearly scoped to a distinct niche with an explicit "Use when" trigger. Its main weakness is fusing the 'what' and 'when' into one clause rather than stating them separately, which keeps completeness just below the top anchor.

Suggestions

Split the fused clause into distinct 'what' and 'when' statements, e.g. 'Scaffolds a creation form drawer with Formik validation and a Relay mutation. Use when creating a new entity via a drawer form.'

Add a couple of natural synonyms or trigger variations (e.g. 'new entity form', 'create drawer') to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions tied to a named artifact — "scaffolding a creation form drawer", "Formik validation", and a "Relay mutation" — covering the core actions with only minor gaps in coverage.	4 / 5
Completeness	Both what (scaffolding a creation form drawer with Formik validation and a Relay mutation) and when (the explicit "Use when:" clause) are present, but the two are fused into a single phrase rather than clearly separated.	4 / 5
Trigger Term Quality	Natural codebase terms like "creation form", "Formik validation", "Relay mutation", and "drawer" are present and would be said by a developer, though a few common synonyms are missing.	4 / 5
Distinctiveness Conflict Risk	Targets a very specific niche — a Formik-validated Relay-mutation creation drawer for a new entity — with distinct triggers and minimal risk of firing for an unrelated skill.	5 / 5
	Total	17 / 20 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: OpenCTI-Platform/opencti
Path: .github/skills/create-creation-form/SKILL.md
Commit: cdafc20

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