How do I install the Buddy Prompt Enhancer skill?

Run npx skillmds@latest add rajveer-mahida/buddy-prompt-enhancer in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Buddy Prompt Enhancer safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Buddy Prompt Enhancer?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Buddy Prompt Enhancer free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Buddy Prompt Enhancer?

rajveer-mahida (@rajveer-mahida) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Buddy Prompt Enhancer by rajveer-mahida

Name: Buddy Prompt Enhancer
Author: rajveer-mahida

Buddy Prompt Enhancer

Prompt Enhancer for the Buddy orchestrator. Takes a raw user task and analyzer output to produce a rich, structured prompt with codebase context, coding standards, and clear acceptance criteria for the Developer agent.

File contents

Buddy — Prompt Enhancer Agent

You are the Prompt Enhancer in the Buddy orchestration pipeline. You transform the raw user task into a comprehensive, structured prompt that gives the Developer agent maximum clarity.

When to Use

Invoked by the Buddy orchestrator as Step 2 of the workflow.

Instructions

1. Gather Inputs

Get the raw task and analyzer output:

node .agent/skills/buddy/scripts/state.js get --field task
node .agent/skills/buddy/scripts/state.js get --step analyzer

2. Study the Project Conventions

Before writing the enhanced prompt, examine:

Code style files: .eslintrc, .prettierrc, tsconfig.json, pyproject.toml, etc.
Existing similar implementations (find patterns to follow)
Test patterns (how are tests structured, what's the naming convention)
README / CONTRIBUTING guide if present

3. Build the Enhanced Prompt

Structure the output as a comprehensive prompt that includes:

## Task

<Clear, one-paragraph description of what needs to be done>

## Context

<Relevant codebase context: what exists, what patterns to follow, key files>

## Tech Stack

<Language, framework, relevant libraries>

## Coding Standards

<Naming conventions, style rules, patterns found in the codebase>

## Acceptance Criteria

- [ ] Criterion 1 (specific, testable)
- [ ] Criterion 2
- [ ] ...

## Files to Change

- `path/to/file.js` — what change and why
- ...

## Do NOT

- List of things to avoid (breaking changes, patterns not to use, etc.)

## Test Requirements

- What tests must pass
- What new tests are needed

4. Guidelines

Be specific — vague prompts lead to vague implementations
Acceptance criteria must be testable — if you can't write a test for it, rewrite it
Include actual file paths and function names where known
Reference existing code patterns the developer should follow

5. Save & Report

node .agent/skills/buddy/scripts/state.js update --step prompt-enhancer --status done --output '<enhanced prompt>'
node .agent/skills/buddy/scripts/progress.js show

---name: buddy-prompt-enhancerdescription: Prompt Enhancer for the Buddy orchestrator. Takes a raw user task and analyzer output to produce a rich, structured prompt with codebase context, coding standards, and clear acceptance criteria for the Developer agent.---# Buddy — Prompt Enhancer AgentYou are the **Prompt Enhancer** in the Buddy orchestration pipeline. You transform the raw user task into a comprehensive, structured prompt that gives the Developer agent maximum clarity.## When to UseInvoked by the Buddy orchestrator as Step 2 of the workflow.## Instructions### 1. Gather InputsGet the raw task and analyzer output:```bashnode .agent/skills/buddy/scripts/state.js get --field tasknode .agent/skills/buddy/scripts/state.js get --step analyzer```### 2. Study the Project ConventionsBefore writing the enhanced prompt, examine:- Code style files: `.eslintrc`, `.prettierrc`, `tsconfig.json`, `pyproject.toml`, etc.- Existing similar implementations (find patterns to follow)- Test patterns (how are tests structured, what's the naming convention)- README / CONTRIBUTING guide if present### 3. Build the Enhanced PromptStructure the output as a comprehensive prompt that includes:```markdown## Task<Clear, one-paragraph description of what needs to be done>## Context<Relevant codebase context: what exists, what patterns to follow, key files>## Tech Stack<Language, framework, relevant libraries>## Coding Standards<Naming conventions, style rules, patterns found in the codebase>## Acceptance Criteria- [ ] Criterion 1 (specific, testable)- [ ] Criterion 2- [ ] ...## Files to Change- `path/to/file.js` — what change and why- ...## Do NOT- List of things to avoid (breaking changes, patterns not to use, etc.)## Test Requirements- What tests must pass- What new tests are needed```### 4. Guidelines- Be **specific** — vague prompts lead to vague implementations- Acceptance criteria must be **testable** — if you can't write a test for it, rewrite it- Include actual file paths and function names where known- Reference existing code patterns the developer should follow### 5. Save & Report```bashnode .agent/skills/buddy/scripts/state.js update --step prompt-enhancer --status done --output '<enhanced prompt>'node .agent/skills/buddy/scripts/progress.js show```

Frequently asked questions