Skip to content
Back to skills

Vibe Help

ASecurity

Routes to the right vibe-engineering skill for the current task and lists the full catalog. Use when the user asks which skill to use, asks what vibe-engineering can do, or is unsure how to approach a task.

  • 163 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 28, 2026
ai-agentsgotesting

Works with

  • claude code
  • cli

Security analysis

A100/100

Scanned October 7, 2026

npx -y skills add ash1794/vibe-engineering --skill vibe-help --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vibe Help?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Vibe Help
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/ash1794-vibe-help/badge)](https://www.skillsdirectory.com/skills/ash1794-vibe-help)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: vibe-help
description: Routes to the right vibe-engineering skill for the current task and lists the full catalog. Use when the user asks which skill to use, asks what vibe-engineering can do, or is unsure how to approach a task.
user-invocable: true
---

# vibe-help

The vibe-engineering skill router. Skills are normally picked automatically from their descriptions; this skill is for when the user wants to browse, or isn't sure which one fits.

## When to Use This Skill

- User asks "what skill should I use?", "help", or "what can vibe-engineering do?"
- User is starting an unfamiliar type of task and wants a recommended workflow
- You are unsure which of two similar skills applies

## When NOT to Use This Skill

- A specific skill was already invoked, or obviously applies
- In the middle of executing another skill's workflow
- Trivially simple tasks (e.g., "fix this typo")

## How to Route

Ask what the user is trying to do (unless it's already clear), then recommend **one** starting skill and at most two follow-ups. Don't recite the whole catalog unless asked.

### "I'm about to build something new"
→ Before: `vibe-research-before-design`, then `vibe-requirements-validator` if there's a PRD
→ During: `vibe-scope-guard`, `vibe-production-mindset` (production code)
→ After: `vibe-quality-loop`, `vibe-acceptance-gate`

### "I need to fix bugs / issues"
→ 1–5 bugs: fix directly, then `vibe-reflect-and-compound` for any non-trivial one
→ Intermittent / "flaky" failure: `vibe-flake-root-cause`
→ 10+ bugs or findings: `vibe-gap-closure-loop`
→ Prevent recurrence: `vibe-adversarial-test-generation`

### "I'm reviewing code, a design, or docs"
→ Design or large change: `vibe-devil-advocate-review` (panel mode for multi-agent release candidates)
→ Spec compliance: `vibe-spec-sync --audit`
→ "Tear this apart" (any artifact, any domain): `vibe-devil-advocate-review`
→ Docs: `vibe-doc-quality-gate` · Requirements: `vibe-requirements-validator`
→ Prose that reads as machine-written: `vibe-slop-filter`

### "I need to test something"
→ Planning: `vibe-scenario-matrix` · Coverage: `vibe-coverage-enforcer`
→ Edge cases: `vibe-adversarial-test-generation` · Parsers: `vibe-fuzz-parser-inputs`
→ Snapshots: `vibe-golden-file-testing` · Concurrency: `vibe-concurrent-test-safety`

### "I'm committing, deploying, or shipping"
→ Commit: `vibe-pre-commit-audit`, `vibe-spec-sync`
→ Deploy: `vibe-safe-deploy` · Risky change: `vibe-rollback-plan`
→ Publishing drafted or privately sourced content: `vibe-publication-leak-guard`
→ Running services: `vibe-service-health-dashboard`

### "I have a lot of parallel work"
→ One-shot fan-out: `vibe-parallel-task-decomposition` → Integrate: `vibe-cherry-pick-integration`
→ Multi-phase project with long-lived agents: `vibe-workstream-orchestration`

### "Is this production-ready?"
→ Audit: `vibe-gap-analysis` → Close gaps: `vibe-gap-closure-loop`

### "I need to make or record a decision"
→ Research: `vibe-research-before-design` → Record: `vibe-decision-journal` → Challenge: `vibe-devil-advocate-review`

### "I want to capture what just happened"
→ Learnings, bugs, patterns: `vibe-reflect-and-compound`
→ Handing off, or winding down at a usage limit: `vibe-handover-doc`
→ End of sprint: `vibe-iteration-review`

### "Am I actually done?"
→ `vibe-acceptance-gate`, then `vibe-anti-rationalization-check`

## Full Catalog

| Area | Skills |
|------|--------|
| Research & decisions | `vibe-research-before-design`, `vibe-decision-journal`, `vibe-devil-advocate-review` |
| Quality gates | `vibe-acceptance-gate`, `vibe-quality-loop`, `vibe-anti-rationalization-check`, `vibe-spec-sync`, `vibe-doc-quality-gate`, `vibe-requirements-validator`, `vibe-coverage-enforcer`, `vibe-slop-filter` |
| Knowledge & continuity | `vibe-reflect-and-compound`, `vibe-handover-doc` |
| Parallel work | `vibe-parallel-task-decomposition`, `vibe-workstream-orchestration`, `vibe-cherry-pick-integration` |
| Testing | `vibe-scenario-matrix`, `vibe-adversarial-test-generation`, `vibe-fuzz-parser-inputs`, `vibe-golden-file-testing`, `vibe-concurrent-test-safety`, `vibe-flake-root-cause` |
| Deployment & ops | `vibe-pre-commit-audit`, `vibe-publication-leak-guard`, `vibe-safe-deploy`, `vibe-rollback-plan`, `vibe-service-health-dashboard` |
| Gap analysis | `vibe-gap-analysis`, `vibe-gap-closure-loop` |
| Process | `vibe-scope-guard`, `vibe-production-mindset`, `vibe-iteration-review` |
| Meta | `vibe-help` |

## Invocation

- **Claude Code**: `/vibe-engineering:<skill-name>` (plugin install) or `/<skill-name>`
- **OpenAI Codex**: `$<skill-name>`
- **Gemini CLI**: activated automatically from the description; `/skills` lists what's installed

## Output Format

**Recommended**: `vibe-[skill]` — [one line on why it fits]
**Then**: `vibe-[skill]`, `vibe-[skill]` (optional follow-ups)

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.