Skip to content
Agentmart
Submit a tool

vibe

Route work through Vibe Engineering.

Skill by executiveusa

IndexedMIT★ 1
Write a review

Install

Works with Claude Code, Claude apps, Codex, Cursor, Gemini CLI, GitHub Copilot, VS Code, OpenCode, Goose, Windsurf. Read the repository before you give any tool access to your data.

npx agentmarket install skill/executiveusa-vibe

Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.

Get the weekly diff

The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.

We use your email only for this newsletter. Privacy

About

Route work through Vibe Engineering. Use when someone wants to build with AI without slop, needs a Vibe skill, or wants a plain-language process from idea to proof.

No reviews yet. Installed it? Reviews come from verified installers only. How reviews work

Permissions

What this skill can do and what it asks for, from its SKILL.md. Checked Oct 25, 2026.

Tools
No tools found
Secrets
None asked for
Install scripts
None found

Network hosts it talks to 1

  • codeload.github.com · found in install command

Files it touches

  • ~/.claude/skills/vibe

What's inside

Skill name
vibe
Description
Route work through Vibe Engineering. Use when someone wants to build with AI without slop, needs a Vibe skill, or wants a plain-language process from idea to proof.
License
MIT
Instructions
17 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Vibe Engineering

AI makes it easy to make a lot of stuff quickly. Vibe Engineering helps you make the right thing, make it well, and prove it works before you call it done.

Read `src/skills/index.mjs` as the canonical skill list. Pick the smallest skill that fits. Keep the user's words and goal visible.

For substantial software work, do not jump straight to implementation. Follow the required lifecycle:

`DEFINE → PLAN → BUILD → VERIFY → REVIEW → SHIP`

Use `proof` during VERIFY to attach evidence. Use independent review before SHIP. Use `ship` only after an authorized owner, Judge, or human records `SHIP`; stop on `HOLD`.

Common routes: `grill`, `language`, `spec`, `tickets`, `build`, `test-first`/`test`, `debug`, `review`, `architecture-check`/`architecture`, `stop-slop`, `deep-work`, `taste`, `proof`, `ship`, `handoff`.

Do not bury the user in internal process names. Explain what you are doing in normal language.

From executiveusa/vibe-engineering, MIT.

More from executiveusa/vibe-engineering

Signals

Stars
1
Forks
0
Open issues
7
Last commit (this folder)
Sep 1, 2026 (1 month ago)

From GitHub (fetched Oct 24, 2026).

Details

License
MIT
First seen
Oct 24, 2026
Last checked
Oct 24, 2026

More from executiveusa

Cite this page

vibe skill. Agent Mart. https://agentmart.dev/skills/executiveusa-vibe (last updated 2026-10-24)