CtrlK
BlogDocsLog inGet started
Tessl Logo

vibe-research

Deep research and market validation for app ideas. Use when starting a new project, validating an idea, or when the user says "research my idea", "validate my app", or "help me start a new project".

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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-structured research-workflow skill: lean, highly actionable, with a clear step sequence and an explicit confirmation checkpoint. Its only structural caveat is reliance on an external (non-bundled) question-bank file, which it handles gracefully.

DimensionReasoningScore

Conciseness

The body is a lean workflow script that assumes Claude's competence and teaches no background concepts; the inline templates (verification echo, Handoff Context block) earn their tokens.

3 / 3

Actionability

Guidance is concrete and specific: an exact output path (docs/research-[AppName].md), exact section headings, an exact Handoff Context block, and per-level question paths — fully actionable despite being instruction-only.

3 / 3

Workflow Clarity

A clearly sequenced Step 1→4 process with an explicit validation checkpoint in Step 3 ('Is this accurate? Should I adjust anything?') before proceeding to the research phase.

3 / 3

Progressive Disclosure

A well-organized overview with a single, clearly signaled one-level-deep reference (part1-deepresearch.md as the 'single source of truth'), with graceful handling of its absence and no nested references.

3 / 3

Total

12

/

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 strong, well-targeted description with excellent trigger coverage, explicit use-when guidance, and a clear niche. Its only weakness is that the stated capabilities are somewhat high-level rather than a concrete enumerated action list.

Suggestions

Expand the capability list beyond 'Deep research and market validation' to name concrete actions, e.g. 'Research competitors, analyze the market landscape, estimate tool costs, and validate app ideas.'

Name the concrete deliverable in the description, e.g. note that it produces a research document with handoff context for the downstream PRD and tech-design steps.

DimensionReasoningScore

Specificity

It names the domain ('app ideas') and two actions ('Deep research and market validation'), but these are high-level rather than a list of multiple concrete distinct actions as the score-3 anchor requires.

2 / 3

Completeness

It explicitly answers both what ('Deep research and market validation for app ideas') and when via an explicit 'Use when...' clause with concrete triggers.

3 / 3

Trigger Term Quality

It includes natural phrases a user would actually say — 'research my idea', 'validate my app', 'help me start a new project' — plus variations like 'starting a new project' and 'validating an idea'.

3 / 3

Distinctiveness Conflict Risk

It carves a clear niche (app-idea research and market validation) with distinct trigger phrases, making conflict with other skills unlikely; voice is third person.

3 / 3

Total

11

/

12

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.