quick-design

Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to warrant one. Produces a Quick Design Spec that embeds directly into story files.

Quality

67%

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 ./.claude/skills/quick-design/SKILL.md

Quality

Content

77%

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 well-structured, highly actionable process skill with concrete templates, clear sequencing, and strong validation checkpoints for its file-writing steps. Its weakest aspect is progressive disclosure: the substantial inline spec templates could be split into reference files, and a little intro/redirect redundancy could be trimmed.

Suggestions

Consider moving the three full spec templates into a single references/spec-templates.md file referenced from the main workflow to reduce inline bulk.

De-duplicate the redirect criteria that appear in both section 1 and section 5, keeping one canonical list and linking to it.

Trim the opening paragraph, which largely restates the frontmatter description, to tighten token efficiency.

Dimension	Reasoning	Score
Conciseness	It assumes Claude's competence throughout with no concept padding, but the intro framing overlaps the description and the redirect criteria are restated in both section 1 and section 5, so not every token earns its place.	2 / 3
Actionability	Provides complete copy-paste-ready markdown spec templates per change category with concrete field structures, tables, acceptance-criteria formats, explicit file paths, and exact AskUserQuestion prompts and options — fully executable guidance.	3 / 3
Workflow Clarity	A clear five-step sequence with explicit validation checkpoints (classification confirmation, approval gate before writing, a separate GDD-edit approval with old-vs-new diff) and a revise feedback loop, satisfying the destructive-operation validation requirement.	3 / 3
Progressive Disclosure	Well-organized as a single self-contained file with no nested references, but it is a ~290-line monolith with three full spec templates inline and no reference split, so the 'appropriately split / one-level-deep references' anchor for 3 does not apply.	2 / 3
	Total	10 / 12 Passed

Description

57%

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 well-differentiated, clearly conveying a lightweight design-spec niche distinct from full GDD authoring. Its main weakness is the absence of an explicit positive "Use when..." trigger clause, leaving the invocation condition implied rather than stated as a user-facing trigger.

Suggestions

Add an explicit 'Use when...' clause naming user-facing triggers, e.g. 'Use when making tuning adjustments, minor mechanics, or balance tweaks too small for a full GDD.'

Broaden trigger-term coverage with common variations users would actually say (e.g. 'tweak', 'small balance change', 'quick design') to improve trigger matching.

Reframe the when-condition as a positive invocation trigger rather than only describing when it skips the heavyweight path.

Dimension	Reasoning	Score
Specificity	Names the domain ("lightweight design spec for small changes"), concrete change categories ("tuning adjustments, minor mechanics, balance tweaks"), and a specific output ("Quick Design Spec that embeds directly into story files"), but lists input categories plus one output rather than multiple concrete actions.	2 / 3
Completeness	Clearly states what it does and gives a when-condition ("when a system GDD already exists or the change is too small to warrant one"), but it is phrased as a skip condition for the heavyweight path rather than a positive "Use when..." trigger clause, which caps completeness at 2.	2 / 3
Trigger Term Quality	Contains relevant natural game-dev terms ("tuning adjustments", "balance tweaks", "minor mechanics") a user might say, but offers limited variations and no explicit trigger-phrase coverage, matching "some relevant keywords but missing common variations."	2 / 3
Distinctiveness Conflict Risk	Occupies a clear niche — a lightweight spec path explicitly contrasted against full GDD authoring and tied to a specific game-dev design workflow — making it unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 Passed

Validation

81%

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

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
referenced_paths_exist	Referenced path issues: 3 missing	Warning

	Total	13 / 16 Passed

Repository: Donchitos/Claude-Code-Game-Studios
Path: .claude/skills/quick-design/SKILL.md
Commit: 984023d

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.