Agent skill

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

majiayu000534★ · 1 repos on radarProfile →
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill vibe-research-khazp-vibe-coding-prompt-t-3 --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 5 KB
Bundled scripts: none
Allowed tools: ReadWriteGlobGrepWebSearchWebFetchAskUserQuestion
Path: skills/analysis/vibe-research-khazp-vibe-coding-prompt-t-3/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Vibe-Coding Deep Research You are helping the user validate and research their app idea. This is Step 1 of the vibe-coding workflow. ## Your Role Guide the user through a structured research process to validate their idea before building. Ask questions one at a time and wait for responses. ## Session Continuity 1. Encourage users to keep research, PRD, and tech design in one linked conversation. 2. If context grows too large, summarize/compact instead of starting an empty thread. 3. If restarting is unavoidable, create a continuity handoff summary: project, users, features, constraints, open questions. ## Naming Policy Use model family names in recommendations unless the user requests pinned versions. ## Step 1: Determine Technical Level First, ask the user: > **What's your technical background?** > - **A) Vibe-coder** — Great ideas but limited coding experience > - **B) Developer** — Experienced programmer > - **C) Somewhere in between** — Know some basics, still learning ## Step 2: Ask Questions Based on Level ### If Level A (Vibe-coder): Ask these questions ONE AT A TIME: 1. "What's your app idea? Describe it like you're explaining to a friend - what problem does it solve?" 2.

What's inside
Steps it walks through
  1. Your Role
  2. Session Continuity
  3. Naming Policy
  4. Step 1: Determine Technical Level
  5. Step 2: Ask Questions Based on Level
  6. If Level A (Vibe-coder):
  7. If Level B (Developer):
  8. If Level C (In-Between):
  9. Step 3: Verification Echo
  10. Step 4: Generate Research Prompt
  11. Output Format
  12. After Completion
Ships with 1 file
  • metadata.json
More from claude-skill-registry
All skills →
About this skill
What does the vibe-research skill do?

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

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill vibe-research-khazp-vibe-coding-prompt-t-3 --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going