SkillA skill gives Relay a specialist method it can reuse on your work.ResearchCommunity
Low riskSecurity review passed

vibe-check

Turn a complete beginner's app idea into a buildable plan, then keep them oriented while they build.

How it works

What vibe-check does

ALSO use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, "commit and push," local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe.

AND use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask "is my code organized" or "can you clean it up." Built for people who don't know what an API, database, or GitHub is, so reach for it when they never say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or setting up CI/CD.

Use it when

Whenever someone who has never coded wants to build or "vibe code" an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint.

Inputs and results

What goes in, what comes back

  1. You give

    A short brief describing what you need

    Add a specialist method to the work.

  2. You get

    A finished result to review

    The method guides the work with your files and context.

  3. You check

    The sources and open questions

    Review the output against your brief.

Questions and answers

Questions about vibe-check

Updated Jun 14, 2026.

What does vibe-check do?

Turn a complete beginner's app idea into a buildable plan, then keep them oriented while they build. Use it whenever someone who has never coded wants to build or "vibe code" an app, has an idea but no idea where to start, or wants it turned into a plan, MVP scope, tech stack, user flows, or blueprint. ALSO use it when a non-coder needs build-time basics: what Git and GitHub are, making an account, "commit and push," local vs. staging vs. production, putting an app online (deploy/ship), or keeping API keys safe. AND use it in Checkup Mode when someone who built with AI says it became a mess, the AI keeps breaking things or going in circles, they're scared to touch their code, or they ask "is my code organized" or "can you clean it up." Built for people who don't know what an API, database, or GitHub is, so reach for it when they never say "plan" or "architecture." Not for an experienced dev debugging, refactoring, or setting up CI/CD.

Who is vibe-check for?

It is designed for teams that want to hand off recurring work and review the result before it is used.

What do I need to use it?

Nothing extra is needed. Sign in to Relay to run it with your own files and context.

What does vibe-check produce?

A finished result to review. Results come back with their sources and any open questions for you to check before anything is used.

How much does vibe-check cost?

It is free to use. Paid model usage, if any, is shown before a run.

Can an AI agent use it?

Yes. Agents can read its public definition through the Relay API and run it with a person’s authorization. See the For Agents page for how to connect.

Details

Trust, access and technical details

Trust and access

Visibility
Public: anyone can view
Status
Published and maintained
Pricing
Free
Low riskSecurity review passedBehavior not evaluated
Reviewed version
cmqdrxiq50002…
Reviewed
Jun 14, 2026
Static signals
8 signals
Source provenance
Commit pinned

Security review is a static package assessment, not a guarantee of safety or a behavioral qualification.

Use it from code or an agent

Read the public definition, then check cost and inputs with a preflight before a run.

Open definition

POST /api/v1/runs/preflight

How agents connect to Relay →

Tags and source

Repo
TexasBedouin/vibe-check
License
MIT

Connections

Where vibe-check fits

Similar skills5

Skill · Research

Application View Mapper

Derive a complete, source-traceable inventory of applications, views, subviews, overlays, modes, and required states from a PRD or functional requirements. Use for product-surface planning, information architecture, UX scope, wireframe coverage, or design handoff. Do not use when the requested output is the wireframes or a design-tool generation prompt.Free
Skill · Research

incremental-implementation

Delivers changes incrementally. Use when implementing any feature or change that touches more than one file. Use when you're about to write a large amount of code at once, or when a task feels too big to land in one step.FreeCommunity
Skill · Research

Kpi Tree

Creates a KPI tree that connects company goals to product outcomes, input metrics, leading indicators, and instrumentation needs.Free
Skill · Research

KPI Tree

Build a KPI tree that connects a strategic goal to an outcome metric, controllable input metrics, guardrails, owners, and instrumentation. Use for product strategy, metric design, OKR measurement, north-star decomposition, initiative prioritization, or diagnosing why a business outcome is moving.Free
Skill · Research

observability-and-instrumentation

Instruments code so production behavior is visible and diagnosable. Use when adding logging, metrics, tracing, or alerting. Use when shipping any feature that runs in production and you need evidence it works. Use when production issues are reported but you can't tell what happened from the available data.FreeCommunity

Have a task this would help with?

Describe it. Relay plans the work, picks the right playbook and shows the cost before anything runs.

Loading request box