CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

66

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

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

A well-structured, highly actionable interview-and-generation workflow with explicit sequencing and a verification checkpoint. Main weaknesses are minor: some inline bulk that could be split into references and only implicit error-recovery guidance.

Suggestions

Move the per-level question banks (especially Level B's 12 items) into a references file (e.g. references/question-bank.md) and signal it from SKILL.md to improve progressive disclosure.

Add an explicit feedback loop for the verification step (e.g. 'if the user corrects an item, update it and re-confirm before generating') to strengthen workflow clarity.

Trim the small overlap between AI-strategy questions (Step 3) and the AI Product Strategy section (Step 5) to tighten conciseness.

DimensionReasoningScore

Conciseness

The body is mostly efficient, assuming Claude's competence and using terse question banks and templates, but the long Level B question list and some repetition of AI-strategy items between questions and the document structure could be trimmed slightly.

4 / 5

Actionability

Provides copy-paste-ready question scripts, an exact verification-echo template, a fixed document structure, and an exact fenced JSON meta block with precise file path, covering the common cases fully.

5 / 5

Workflow Clarity

Steps 1-5 are clearly sequenced with an explicit Verification Echo checkpoint and confirmation loop, but error-recovery feedback is only implicit and there is no checklist for resuming interrupted interviews.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections in a single self-contained file with no bundle files present; the large inline per-level question banks could arguably live in a separate reference file, leaving a minor organization gap.

4 / 5

Total

17

/

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.

A strong, well-structured description that clearly states both capability and explicit trigger conditions in third person. It is slightly limited on specificity (a single action) and could add a couple more natural trigger synonyms.

Suggestions

Add one or two more concrete actions the skill performs (e.g. 'compare tech stacks, recommend an architecture') to lift specificity beyond a single verb.

Include a few additional natural trigger variants like 'plan architecture' already present, plus 'decide how to build' or 'tech stack recommendation' for broader keyword coverage.

DimensionReasoningScore

Specificity

Names the domain ('Technical Design Document for your MVP') and the single concrete action of creating one, but does not enumerate multiple specific sub-actions; the quoted phrases are use-case triggers rather than performed actions.

3 / 5

Completeness

Explicitly answers both what ('Create a Technical Design Document for your MVP') and when ('Use when the user wants to plan architecture, choose tech stack, or says...') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes natural phrases users would actually say ('plan technical design', 'choose tech stack', 'how should I build this') with good coverage, though a few common variants like 'architecture' or 'scaffold' are absent.

4 / 5

Distinctiveness Conflict Risk

Occupies a clear niche (MVP technical design) with distinct triggers, though 'plan architecture'/'choose tech stack' could mildly overlap with general planning or PRD skills in the same workflow.

4 / 5

Total

16

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

Total

15

/

16

Passed

Repository
KhazP/vibe-coding-prompt-template
Reviewed

Table of Contents

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.