vibe-techdesign

Create a Technical Design Document for your MVP. Use when the user wants to plan architecture, choose tech stack, or says "plan technical design", "choose tech stack", or "how should I build this".

Quality

83%

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

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A tightly written, well-sequenced workflow with a good confirmation checkpoint. Its main weakness is that the core question bank and template live in an external file that is not shipped with the skill, undermining both actionability and progressive disclosure.

Suggestions

Ship 'part3-tech-design-mvp.md' inside the skill bundle (e.g. ./references/) and update the body to reference that real path, so the 'single source of truth' is actually available rather than missing.

If keeping the external dependency, inline the minimal question-bank paths and template skeleton into SKILL.md so the skill remains actionable when the external file is absent.

Soften or justify the 'use its question bank ... EXACTLY ... with no renames' instruction so it reads as concrete guidance rather than a directive to a file the model cannot assume exists.

Dimension	Reasoning	Score
Conciseness	The body is lean and directive ('Read the PRD and extract:', 'Ask:', 'After confirmation, generate...') and avoids explaining concepts Claude already knows; it assumes competence and every section earns its place.	3 / 3
Actionability	Process guidance is concrete (specific glob patterns, output path, a filled verification-echo template), but the substantive instructions delegate the question bank and document template to 'part3-tech-design-mvp.md ... the single source of truth', which is not present in the skill bundle, leaving key details incomplete.	2 / 3
Workflow Clarity	Steps 1-5 are clearly sequenced with a Prerequisites gate and an explicit confirmation checkpoint in Step 4 ('Is this correct? Any adjustments before I create the Technical Design?') acting as a feedback loop before generation.	3 / 3
Progressive Disclosure	The content is organized into clear sections and references only one external file at one level deep, but that reference ('part3-tech-design-mvp.md' in the repository root) is not part of the skill bundle and is absent, so the 'well-signaled one-level-deep reference' ideal is not actually realized.	2 / 3
	Total	10 / 12 Passed

Description

90%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A well-formed description that clearly states its purpose and gives strong, natural trigger terms. The only gap is that it names a single composite action rather than several discrete capabilities.

Suggestions

Broaden the capability statement to list a few concrete sub-actions (e.g. 'plan architecture, choose a tech stack, and structure a Technical Design Document') to lift specificity from a single composite action to multiple distinct ones.

Dimension	Reasoning	Score
Specificity	Names the single concrete action 'Create a Technical Design Document for your MVP' but does not enumerate multiple distinct concrete actions like the score-3 anchor (e.g. 'extract, fill, merge'), so it lands at 'names domain and some actions, but not comprehensive'.	2 / 3
Completeness	Explicitly answers both what ('Create a Technical Design Document for your MVP') and when via an explicit 'Use when the user wants to...' trigger clause.	3 / 3
Trigger Term Quality	Includes natural phrases a user would actually say — 'plan architecture', 'choose tech stack', 'how should I build this', 'plan technical design' — giving good coverage of common variations rather than jargon.	3 / 3
Distinctiveness Conflict Risk	The MVP technical-design framing with triggers like 'plan technical design' and 'choose tech stack' carves a clear niche that is unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 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
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning

	Total	15 / 16 Passed

Repository: KhazP/vibe-coding-prompt-template
Path: .claude/skills/vibe-techdesign/SKILL.md
Commit: 06d0796

Reviewed: about 18 hours 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.