Skip to content
Agentmart
Submit a tool

setup-vibe

Configure a repository so Vibe Engineering skills know where project context, decisions, issues, proof, and release rules live.

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-setup-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

Configure a repository so Vibe Engineering skills know where project context, decisions, issues, proof, and release rules live.

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/setup-vibe

What's inside

Skill name
setup-vibe
Description
Configure a repository so Vibe Engineering skills know where project context, decisions, issues, proof, and release rules live.
License
MIT
Instructions
18 lines in SKILL.md · view on GitHub

Files (1)

  • SKILL.md

SKILL.md (first lines)

# Setup Vibe

Inspect the repository before writing anything. Reuse existing `AGENTS.md`, project context, decision/ADR folders, issue tracking, CI, and deployment conventions when they already exist.

Settle these basics with the owner only where the repository cannot answer them:

1. Where work is tracked.
2. Where shared project language lives.
3. Where hard-to-reverse decisions are recorded.
4. Which checks prove a change is safe to merge.
5. Who can approve production release.
6. What the rollback path is.

Prefer the existing repository structure over adding parallel Vibe-only files. Add the smallest missing pointers needed so `grill`, `spec`, `tickets`, `review`, `proof`, and `ship` can work without guessing.

Do not overwrite existing owner decisions. Preview material setup changes that affect authority, release, or destructive actions, and require the owner's explicit approval before applying them.

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

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