Name: vibe-research
Rating: 62.4 (1 reviews)
Author: KhazP

Blog Docs Log inGet started

vibe-research

Research an app idea or resolve product and technical uncertainties before committing to a design.

Quality

73%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./.agents/skills/vibe-research/SKILL.md

The canonical home for this skill is vibe-research in KhazP/vibe-coding-prompt-template

Quality

Content

86%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 content is a lean, well-structured instruction skill with a clear sequenced workflow, validation guidance, and a single well-signaled reference file. It could be strengthened with concrete reusable templates and an explicit error-recovery loop.

Suggestions

Add a short reusable output template (e.g. a research-doc section skeleton or Handoff Context block) so the common case is copy-paste ready.

Add an explicit validation feedback loop (e.g. 'If a source cannot be verified, mark it as an assumption and re-check authoritative sources') to lift workflow clarity.

Optionally surface the Quick/Guided/Deep mode definitions inline or via a short reference so mode selection is unambiguous.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence, with no padding or explanation of concepts Claude already knows; every sentence carries actionable instruction, matching the score-5 anchor.	5 / 5
Actionability	Provides concrete, specific directives ('Verify changing prices...from authoritative sources', 'Save findings to...docs/research-[AppName].md') that are actionable for an instruction-only skill; not a 5 because there are no copy-paste-ready artifacts or templates for the common cases.	4 / 5
Workflow Clarity	A clear multi-step sequence runs from identifying the decision through research, evidence verification, saving findings, to handoff context, with validation checkpoints ('Verify...from authoritative sources', 'Preserve unknowns explicitly'); not a 5 because there is no explicit error-recovery feedback loop.	4 / 5
Progressive Disclosure	The body is a concise overview with a single, clearly signaled one-level-deep reference to the real file references/question-bank.md, placed exactly where the optional detail is needed, matching the score-5 anchor.	5 / 5
	Total	18 / 20 Passed

Description

61%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 clearly conveys the skill's purpose and distinct pre-design research niche, with natural trigger phrasing. Its main weakness is the absence of an explicit 'Use when...' trigger clause, which caps completeness.

Suggestions

Add an explicit 'Use when...' clause naming concrete triggers, e.g. 'Use when the user has an app idea or open product/technical questions before design begins.'

Enumerate one or two more concrete research actions (e.g. 'investigate competitors, technical options, and costs') to lift specificity toward a comprehensive list.

Include a couple of natural synonym triggers (e.g. 'validate an idea', 'product discovery') to broaden keyword coverage.

Dimension	Reasoning	Score
Specificity	Names the research domain and one to two concrete actions ('Research an app idea', 'resolve product and technical uncertainties') but does not enumerate a comprehensive list of actions, matching the score-3 anchor and falling short of the several-actions bar for score 4.	3 / 5
Completeness	It clearly states what the skill does but lacks any explicit 'Use when...' or equivalent trigger clause; per the judging guidelines a missing explicit trigger caps completeness at 3.	3 / 5
Trigger Term Quality	Includes natural phrases a user would say ('Research an app idea', 'product and technical uncertainties', 'design') giving good keyword coverage; not a 5 because common synonyms and broader trigger variations are missing.	4 / 5
Distinctiveness Conflict Risk	'Research an app idea before committing to a design' carves a fairly distinct pre-design niche with only minor overlap risk against adjacent planning skills; not a 5 because 'resolve product and technical uncertainties' is somewhat broad.	4 / 5
	Total	14 / 20 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: .agents/skills/vibe-research/SKILL.md
Commit: db48176

Reviewed: 4 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.