vibe
Skill20 starsChanged 4 months agoMITView on GitHub
Run a short intent through the pipeline. Invoked as /vibekit:vibe. Hands off to brainstorm and does nothing else.
19 other projects use a version of this.
Adopted by
Most recently taken up by
- timurgaleev/vibestacktheir own version, first seen Nov 8, 2026
- foryourhealth111-pixel/Vibe-Skillstheir own version, first seen Nov 3, 2026
- kexi/vibe-skillstheir own version, first seen Nov 1, 2026
- pmatos/skillstheir own version, first seen Nov 1, 2026
- ubmids/vibetheir own version, first seen Oct 20, 2026
- mistralai/mistral-vibetheir own version, first seen Oct 19, 2026
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- mistralai/mistral-vibe★ 5.3ksame name
- foryourhealth111-pixel/Vibe-Skills★ 3.8ksame name
- pcx-wave/vibe-skill★ 118same name
- geeks-accelerator/in-bed-ai★ 26same name
- kennethleungty/claude-music★ 23same name
- th3vib3coder/vibe-science★ 16same name
- timurgaleev/vibestack★ 8same name
- JustineDevs/meta-architect★ 5same name
- Ally-for-Hire/Github-Vibe-Skill★ 2same name
- JustineDevs/premortem★ 2same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 21
Never skip brainstorm because the intent looks small.
- Distinctive: line 22
Never carry out the intent yourself.
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
vibe
An entry point, not a stage. The pipeline is already wired: every skill's Handoff section names its successor, and using-vibekit carries the trigger map. This exists because a slash command cannot exist without a skill to invoke.
What to do
Invoke brainstorm with the user's intent. Stop there.
brainstorm gates the design, hands to plan, plan hands to exec, exec hands to verify, and a failed check goes to debug. None of that is your business to restate or to sequence.
Never
- Never skip
brainstormbecause the intent looks small. That is the gate's whole purpose. - Never carry out the intent yourself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.