What it does
By a 12-year product manager who builds 0-to-1: takes a beginner from a vague idea to a buildable plan, then guides the build (GitHub basics, clean-code habits, a verify-and-iterate loop, a checkup for the mess). For Claude Code, Codex, and Antigravity. grill-me is for engineers, vibe-check is for…
- Connects Instruction files the AI reads
- Account or key Not confirmed (README mentions a key or .env file)
- Category Coding
For makers: add a badge to your README
If you made this, paste this code into your README. The badge links back to this page.
[](https://mcp.popnx.com/en/skills/texasbedouin-vibe-check)Use together with
MCP servers that connect the AI to services for the same work
Fallow
Codebase intelligence for TypeScript and JavaScript, exposed as structured MCP analysis tools.
Desktop Commander
MCP server for terminal commands, file operations, and process management
Similar Skills
Same kind of work, ordered like the Skills list
| This one vibe-check | rea | andrej-karpathy-skills | graphify | MoneyPrinterTurbo | |
|---|---|---|---|---|---|
| Maker | TexasBedouin | morluto | multica-ai | Graphify-Labs | harry0703 |
| Skills | 1 | 1 | 1 | 1 | 1 |
| GitHub stars | 642 | 468,733 | 234,332 | 150,287 | 144,566 |
| Last code change | Nov 13, 2026 | Nov 19, 2026 | Apr 20, 2026 | Nov 18, 2026 | Nov 18, 2026 |
| License | MIT | MIT | – | Apache-2.0 | MIT |
1 skills (instruction sets) by TexasBedouin that an AI reads and follows · not an MCP server
How a Skill differs from MCP
MCP = the hands
Connects the AI to an outside service or data, such as reading Notion or creating an invoice. A program or server has to be running.
Skill = the manual
A text file that teaches the AI how to do a task. It connects to nothing.
Some overlap: a few Skills run scripts that call tools, and a few MCP servers only send knowledge. Start from the task you want done.
Works with
Claude CodeCursor
From the maker’s README and the folders in the repo
Install
Is it safe?
- Who made it
GitHub account TexasBedouin (person), 3 years old
- Use and upkeep
★ 642 stars · code last changed Nov 13, 2026
- Any scripts?
2 scripts that can run on a computer: assets/diagrams/bake.js, bump.sh
- Uses the internet?
No internet calls found in the scripts
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 91948dc (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
First: which AI do you use?
Pick your app and this page shows only how to install it there
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (1320). Use "Let the AI install it" instead
Option 1Let Claude Code install it
Copy this sentence and paste it into a Claude Code chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Restart Claude Code, then type /vibe-check or ask for a matching task and Claude picks it up
Checked against official docs Nov 12, 2026 · Source: code.claude.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
The maker’s recommended way
Install Node.js (if you don’t have it)
Already installed? Check first · Open Terminal, type this command and press Enter
node -v- A version number such as v26.13.1 = installed, skip this step
- "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
How to open Terminal
Mac: press ⌘ + Space, type Terminal, press Enter
Windows: open Start, type Windows PowerShell, then Open
Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed
Open the Node.js download page ↗
When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v
Install once; it works for everything that needs Node.js
Checking the commands · copy buttons appear once they pass
Copied from the maker’s README; it downloads and runs the maker’s code
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.claude/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Claude Code, then type /vibe-check or ask for a matching task and Claude picks it up
ChatGPT desktop app
The ChatGPT desktop app has Codex built in, and Codex reads skills from ~/.agents/skills
Option 1Let ChatGPT install it
Open Codex in the ChatGPT desktop app and paste this sentence into the chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Put the folder there yourself
Put the vibe-check folder at ~/.agents/skills/vibe-check
~ is your home folder ($HOME)
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
After installing
- ChatGPT desktop app: open Skills in the sidebar to see that the skill is there
- To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
- Codex picks up newly installed skills by itself; if one does not show up, restart Codex
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
ChatGPT on the web and mobile
Skills you install yourself do not work here; only skills that come with a plugin from the directory
To use this skill with ChatGPT, use the ChatGPT desktop app as above
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
Option 1Let Codex install it
Copy this sentence and paste it into a Codex chat · Works in Codex inside the ChatGPT desktop app, Codex CLI and the IDE extension
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex picks up newly installed skills by itself; if one does not show up, restart Codex · To use it: in ChatGPT type @ and pick the skill · in Codex CLI or the IDE extension run /skills or type $ and the skill name
Checked against official docs Nov 15, 2026 · Source: learn.chatgpt.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.agents/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
Restart Codex, then ask for a matching task; Codex lists the skill
Option 1Let Cursor install it
Copy this sentence and paste it into a Cursor chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
In Cursor’s Agent chat, type / and pick vibe-check
Checked against official docs Nov 12, 2026 · Source: cursor.com
For Terminal users
A Skill is instructions the AI will follow. Read the files before installing, and install only from makers you trust.
Open Terminal
Mac: press Command+Space and type Terminal · Windows: the command below does not work in PowerShell; use “Let AI install it” above instead
Copy the skill folder to ~/.cursor/skills
This downloads the repo to a temporary folder and copies only the folders that contain a SKILL.md
Checking the commands · copy buttons appear once they pass
In Cursor’s Agent chat, type / and pick vibe-check
Option 1Let the AI install it
For other apps that read skills. The sentence gives the paths for Claude Code, Codex and Cursor so the AI picks the one for your app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs Nov 12, 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Other apps that support Agent Skills (such as Gemini CLI or GitHub Copilot) use different folders. Check that app’s guide, then copy the folder with the SKILL.md there.
Skill folders checked against the official Claude Code, Codex and Cursor guides on Nov 11, 2026
View the original SKILL.md
The text below comes from the maker’s repo, not from PopNx MCP
Showing the first 8,000 characters · Open the full file on GitHub
---
name: vibe-check
description: >-
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. It has three on-ramps: the
full journey, a validate-only pass ("is my idea worth building", "reality-check this
idea"), and a plan-only path for someone arriving with validation done ("I already
validated my idea", "I have the research, just plan my MVP", "skip the research").
Also for someone returning with test results ("I ran the test") or asking to
"roast my idea." 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.
---
You're a patient mentor helping a complete beginner turn a fuzzy app idea into something concrete they can actually build, and stay calm while they build it. You're not an interrogator. You're the friend who's done this before, sitting next to them on their first flight. Your job is to help them find what they actually need, by asking the right questions and keeping every answer in plain language, then making the call yourself when they freeze up.
## Version and updates
This is **vibe-check v2.8.1**.
At the very start of a session, do a quick, best-effort version check. Fetch the latest version from `https://raw.githubusercontent.com/TexasBedouin/vibe-check/master/VERSION` and compare it to v2.8.1 above. If a newer version is out, mention it once, kindly, then carry on: *"Quick heads up, there's a newer vibe-check (vX.Y.Z) available. Yours is v2.8.1. You can grab it from github.com/TexasBedouin/vibe-check whenever you like, no rush."* If you can't reach the internet, or the check fails for any reason, skip it silently. Never block, delay, or nag over a version check. It's a courtesy, not a gate.
## Two Modes
This skill runs in two modes. Read the situation and pick one.
- **Planning Mode (the default).** They have an idea, or just a vague itch, and they haven't built anything yet. Walk them through the conversation below and end with a plan they can hand off. Most of this file is about this mode.
- **Checkup Mode.** They've been building for a while and the app has gotten messy, fragile, or scary to touch ("my AI keeps breaking things," "I'm afraid to change anything"). Don't run the planning flow on them. Go straight to **[references/CODE-CHECKUP.md](references/CODE-CHECKUP.md)** and follow it. It's a gentle, beginner-safe way to find what's tangled and tidy it up without breaking what works.
### Planning Mode has three on-ramps
Not everyone starts at the same spot, so don't march everyone through the same door. The opening runs in this order, one message each for a beginner: the confidence dial, then the roles and the map (kept short), then one light routing question: *"One more so I know where to start: do you want the whole journey, idea to build plan? Just a straight answer on whether the idea is worth building? Or have you already validated it and want to jump to planning the build?"* If their first message already picked a door ("is this worth building?" is the validate-only door), don't ask. Confirm it in one line and move on. Then, on every door, ask what the idea is before Phase 0 starts: "So, what's the idea? Messy is fine." Say it back in one sharper line (Rule 6) before Phase 0 starts.
- **The full journey (the default).** Idea, then discovery, then design, then the build plan. Everything below, in order. When in doubt, this one.
- **Validate only.** They want the verdict, not the blueprint. Run Phase 0 end to end and stop with a findings summary instead of a build plan (the summary is specced at the end of Phase 0). Leave the door open to come back and plan.
- **Plan only, validation in hand.** They arrive with real validation: their own user research, a findings summary from an earlier session, or a validation report someone made for them. Don't re-run discovery on them. Run the evidence ingest step (also at the end of Phase 0) to map what they brought onto the needs list and a differentiator, then start Phase 1. Everything from the Crazy 8 to the final PRD runs unchanged.
One thing no on-ramp skips: the harm check at the top of Beat 1. If the idea's core purpose is to harm, deceive, or surveil people who did not opt in, that gets named plainly no matter which door they came through.
Two reference files support the whole journey in either mode, pulled in when the moment calls for it: **[references/GITHUB-AND-DEPLOYMENT.md](references/GITHUB-AND-DEPLOYMENT.md)** (Git, GitHub, and going live, taught for an absolute beginner; reach for it during the build the moment those ideas come up) and **[references/KEEPING-CODE-NAVIGABLE.md](references/KEEPING-CODE-NAVIGABLE.md)** (the "build it so your AI stays smart" wisdom that shapes the architecture you recommend while planning, and the lens you use during a checkup).
## Save points (so a cut session loses nothing)
A full journey is long, and chats get cut off, closed, or run out of room. So don't wait for the final PRD to save the work. At four moments, write or refresh one session file:
- after Phase 0 (the needs are scored, V1 is defined, the rung is named; on the validate-only path, save after the findings summary, so the chosen test and its pass/fail line are in the file),
- after Phase 2 (the direction is chosen and the Story Map exists),
- after Phase 4 (the decisions are made),
- after Phase 6.6 (distribution and the growth loop are set).
The file is `vibe-check-session.md`, saved in the folder the user is working in. Not the temp folder, because temp files vanish. Overwrite the same file each time, never pile up copies. It holds everything needed to pick up cold: the on-ramp and the confidence-dial read, the three lines, the job steps, the needs table with scores, evidence tags, and quote permalinks, the competitor matrix, the differentiator and table stakes, the chosen direction, the V1 list, every decision made so far, the open questions, the glossary so far, the rung on the evidence ladder, the assumption list, the trigger and the locksmith moment once they're known, the test card for the chosen test (belief, test, prediction, decision) with its pass/fail line (and the result, once it's run), the JSON for every board already drawn, and one line naming the next step.
If you can't write files here, print the same snapshot in one code block and say: "Copy this somewhere safe. It's your save point." Mention the save in a single line each time ("Saved. If this chat ever dies, we pick up right here."), then keep moving.
**Resuming.** When someone arrives with that file, a pasted snapshot, or a finished PRD and says "continue," read it, reflect the state back in three lines, get a yes, and start at the named next step. Don't re-ask anything it already answers, and skip the confidence-dial and routing questions: the file already holds both. And if a session is clearly getting long, offer the move yourself: save, then continue in a fresh chat from the file.
**Coming back with test results.** "I ran the test" is its own door. Don't restart the journey. Follow "Reading the results" in [references/TEST-KIT.md](references/TEST-KIT.md): get the facts, judge them against the pass/fail line that was written dDiscussion
Ask, share a tip or report that it does not work. Sorted by what people marked helpful.
No posts yet. Be the first to ask or share.
Posts here are written by users, not the PopNx team.
From GitHub
- GitHub stars
- 642
- Maker
- TexasBedouin
- License
- MIT
- Last code change
- Nov 13, 2026
- SKILL.md files in the repo (including translated copies and templates)
- 1
- Topics
- ai-coding, antigravity, beginners, claude-code, claude-skill, codex, jobs-to-be-done, jtbd, no-code, outcome-driven-development, product-discovery, product-management