vibe-agents
Create project agent instructions and tool configuration from agreed product and technical decisions. Not for ordinary incremental feature changes.
How do I install this agent skill?
npx skills add https://github.com/khazp/vibe-coding-prompt-template --skill vibe-agentsIs this agent skill safe to install?
- Gen Agent Trust Hubpass
The skill facilitates project setup by reading documentation and running the vibeworkflow CLI. It contains a surface for indirect prompt injection and executes external code via npx.
- Socketpass
No alerts
- Snykwarn
Risk: MEDIUM · 1 issue
- Runlayerpass
1 file scanned · No issues
What does this agent skill do?
Project agent instructions
Use agreed requirements, technical decisions, and the existing repository to write only stable, non-obvious guidance. For a targeted AGENTS.md edit, update the affected instructions directly; do not require an installer, new PRD, or full interview. Keep progress in the project's memory/handoff file rather than the always-loaded rules.
For initial Vibe Workflow setup, read the PRD and Tech Design from
vibe.project.json documents paths when present, otherwise
docs/PRD-*-MVP.md and docs/TechDesign-*-MVP.md. If the PRD, Tech Design,
and Handoff Context disagree (app, stack, or scope), show the conflict and ask
which is correct before generating files; never silently pick one. If the
vibeworkflow CLI is available, inspect npx vibeworkflow --dry-run --json and
initialize within the user's authorization. Preserve existing files; replacement
flags are for intentional replacements whose affected files have been reviewed.
The CLI installs files directly, not into a new templates/ directory.
Fill relevant placeholders from known decisions. Keep task-specific procedures in skills or references and load them only when relevant. Distinguish local implementation from external sends, production changes, and new access. Do not enable broad tool permissions just to make setup convenient.
Use npx vibeworkflow doctor for CLI-generated setup when available; it checks
configuration, not a working build or user journey. In a chat without filesystem
access, use the repository's docs/context-pack.md and supplied product decisions
to produce separated files to save. State absent template/context limitations
instead of inventing them. Continue into implementation only when that is part
of the user's request.
How can the creator link this skill?
Add the canonical catalog link to the repository README so users can inspect current installs and available audits. The publishing guide covers the complete discovery path.
<a href="https://skillzs.dev/skills/khazp/vibe-coding-prompt-template/vibe-agents">View vibe-agents on skillZs</a>