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

61

Quality

73%

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

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/vibe-research/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 skill body is a well-structured, actionable interview-to-research workflow with clear sequencing and a verification checkpoint. Its weakest point is conciseness, driven largely by a duplicated Handoff Context block and verbose AI-related question wording.

Suggestions

Remove the duplication between the Handoff Context template block and the "Output contract" section by defining the fields once and referencing them, to cut redundant tokens.

Tighten the AI/builder-related interview questions (Steps 2 and the Step 4 bullets) to concrete prompts without stacking multiple provider/framework names into one sentence.

Add one or two example WebSearch queries in Step 4 so the research-gathering step is fully executable rather than directional.

DimensionReasoningScore

Conciseness

The body is mostly efficient and sectioned, but the Handoff Context block is duplicated (template plus repeated fields in "Output contract") and several AI/builder question items are verbose, indicating tightening opportunity.

3 / 5

Actionability

Verbatim interview questions, an exact verification-echo template, a numbered output format, and a concrete output path give mostly executable guidance, with the minor gap of no example WebSearch queries.

4 / 5

Workflow Clarity

Steps 1-4 are clearly sequenced with a confirmation checkpoint before research generation and interview rules handling skipped/vague answers; the only gap is limited validation of the research findings themselves when browsing is unavailable.

4 / 5

Progressive Disclosure

No bundle files exist and the content is organized into well-labeled sections with no nested references; the three 10-item per-level question banks could be split out but are reasonable inline for an interview skill.

4 / 5

Total

15

/

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.

The description is strong: it pairs a clear capability statement with explicit, natural-language trigger phrases covering both situational and quoted user phrasings. Specificity of the action list is the main soft spot, since only two concrete actions are named.

DimensionReasoningScore

Specificity

"Deep research and market validation for app ideas" names the domain plus two concrete actions (research, market validation) but does not enumerate several distinct actions, matching the anchor for 1-2 concrete actions.

3 / 5

Completeness

It explicitly answers what (deep research and market validation for app ideas) and when ("Use when starting a new project, validating an idea, or when the user says...") with concrete trigger phrases.

5 / 5

Trigger Term Quality

Natural phrases users would say are present ("research my idea", "validate my app", "help me start a new project") alongside situational triggers, with only minor synonym gaps.

4 / 5

Distinctiveness Conflict Risk

The app-idea research/validation niche with specific verbal triggers is mostly distinct, though "starting a new project" is broad enough to risk minor overlap with general project-setup skills.

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.