goose-graphics-create-style

End-to-end skill that turns a single reference image into a published Gooseworks style — analyzes the image, drafts the slim style spec, renders a hero example plus 2-3 additional formats via Playwright, writes the `gooseworks-style.json` manifest, and publishes via `npx gooseworks styles publish` so other agents can discover it. Mirrors goose-graphics-create-format but for styles.

Quality

80%

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 ./skills/design/composites/goose-graphics-create-style/SKILL.md

Quality

Content

88%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 body is a highly actionable, well-sequenced end-to-end workflow with explicit validation checkpoints and copy-paste-ready commands and examples. Its main weakness is mild redundancy and the absence of any bundle-file split for a skill of this length.

Suggestions

De-duplicate the slug-collision / 409 handling by stating it once and cross-referencing from Steps 5 and 7.

Consider moving the standard brief and the description/tag-writing guidelines into a reference file (e.g. references/brief.md) to slim the main SKILL.md and improve progressive disclosure.

Keep the strong validation structure intact when trimming.

Dimension	Reasoning	Score
Conciseness	The ~415-line body is largely purposeful operational guidance for a complex pipeline, but slug-collision/409 handling is repeated across Steps 2, 5, and 7 and a few guideline sections could be tightened, placing it above the score-3 anchor but short of the lean score-5 anchor.	4 / 5
Actionability	Provides exact CLI commands, the full gooseworks-style.json example, a format dimension table, concrete HTML rules, and the screenshot.js invocation with flags — copy-paste ready and covering the common cases, matching the score-5 anchor.	5 / 5
Workflow Clarity	Eight clearly sequenced steps with an explicit analysis checklist and "do not skip ahead" directive in Step 1, a visual-QA feedback loop in Step 6 ("If anything looks off, fix the HTML and re-render"), collision checks, and exit-code error recovery, matching the score-5 anchor with validation present for the irreversible publish step.	5 / 5
Progressive Disclosure	No bundle files exist, but the body is well-organized into clear sections with external catalog references explicitly signaled via commands (e.g. `npx gooseworks styles get dot-grid-stat`); the minor gap is that the standard brief and writing guidelines could be split into reference files, keeping it at the score-4 anchor rather than the fully-split score-5 anchor.	4 / 5
	Total	18 / 20 Passed

Description

71%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 and action-dense, clearly delineating an end-to-end pipeline, but it lacks an explicit "Use when…" trigger clause and leans on some technical jargon over natural user phrasing. Distinctiveness is strong though slightly softened by a closely related sibling skill.

Suggestions

Add an explicit trigger clause, e.g. "Use when the user has a reference image and wants it published as a reusable, discoverable Gooseworks style."

Soften technical jargon ("slim style spec", "manifest") or pair it with natural synonyms a user would actually say ("style spec", "style definition").

Briefly differentiate from the sibling, e.g. "Use goose-graphics-create-format to author formats; use this for styles."

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — "analyzes the image, drafts the slim style spec, renders a hero example plus 2-3 additional formats via Playwright, writes the gooseworks-style.json manifest, and publishes via npx gooseworks styles publish" — giving comprehensive pipeline coverage, matching the score-5 anchor; no higher anchor exists.	5 / 5
Completeness	The "what" is clear and detailed, but there is no explicit "Use when…" clause — the "when" is only weakly implied by "turns a single reference image into a published Gooseworks style", and the rubric caps completeness at 3 for a missing explicit trigger clause.	3 / 5
Trigger Term Quality	Natural terms like "reference image", "Gooseworks style", and "publish" are present, but "slim style spec", "Playwright", and "manifest" are technical jargon and some natural synonyms are missing, so it sits above the score-3 anchor but below the comprehensive score-5 anchor.	4 / 5
Distinctiveness Conflict Risk	It carves a clear niche (reference image → published Gooseworks style), but the phrase "Mirrors goose-graphics-create-format but for styles" signals a closely related sibling skill, creating minor overlap risk consistent with the score-4 anchor rather than the minimal-risk score-5 anchor.	4 / 5
	Total	16 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: gooseworks-ai/goose-skills
Path: skills/design/composites/goose-graphics-create-style/SKILL.md
Commit: 2523432

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.