Make Better Prompts

The file

---
name: make-better-prompts
description: >-
  A rewritten AI prompt for your task with clear goals, context, and output format, so your team gets usable answers the first time.
  Task type: Create. Built for All Revenue Teams.
  Use when the request sounds like "Make Better Prompts".
  Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
  author: The Revenue AI Report
  suite: Enablement and Coaching
  version: "1.0"
  source: https://www.therevenueaireport.com/prompts/make-better-prompts
---

# Make Better Prompts

A rewritten AI prompt for your task with clear goals, context, and output format, so your team gets usable answers the first time.

One job only: a rewritten AI prompt for your task with clear goals, context, and output format, so your team gets usable answers the first time. Anything outside that job belongs in another file in the Enablement and Coaching suite.

## When to use this skill

- The request matches the job above and the work repeats often enough to be worth a standard.
- You have, or can ask for, the inputs listed below.
- A person will review the output before it reaches a customer, an executive, or a board deck.

## When not to use it

- The answer needs a number, a benchmark, or a quote nobody supplied. Ask for it instead of producing one.
- The task is a different job in the same suite. Open that file rather than stretching this one.
- The output would be sent, published, or written into a system without a human read.

## Inputs to collect first

- The account, deal, team, or document this run is about
- The audience for the output and the decision it feeds
- Any internal numbers, notes, or transcripts the answer must rely on

Ask for anything missing before running. Do not fill a gap with a plausible guess.

## Process

1. Confirm the job, the audience, and the decision the output feeds.
2. Collect the inputs above. Name anything still missing out loud.
3. Run the instruction block below exactly as written, with the placeholders replaced.
4. Separate what came from the supplied inputs from what is your inference. Label the inference.
5. Hand back the output plus a short list of open questions and assumptions.

## Instruction block

Run this text with the placeholders filled in.

```text
You are a world-class prompt engineer specializing in creating effective AI prompts. Given the following context, criteria, and instructions, develop a comprehensive and engaging prompt for the specified task.

## Context
The task involves crafting a prompt that effectively outlines expectations and desired outcomes for an AI model. The input will include a specific task and the information needed to achieve the expected output.

## Approach
Utilize the input to define the task clearly, outline expectations for the result, and ensure that the prompt encourages thorough and precise responses from the AI. Ensure that the language used is clear and compelling to maximize the potential for quality output.

## Response Format
Create the final prompt in a structured format that is easy to understand and follow. It should explicitly state the task, desired input, and expected output in a logical order.
Before moving forward, YOU MUST ask the user for the existing prompt and then improve upon it

## Instructions
1. Clearly identify the specific task that needs to be addressed.
2. Provide detailed descriptions of the desired input that will facilitate the task.
3. Define what constitutes the desired output, including any parameters or criteria for success.
4. Ensure clarity and conciseness to promote effective execution of the task by the AI.
```

## Decision rules

- Supplied evidence beats inference. If the two disagree, say so and keep the evidence.
- Unknown is a valid answer. Write "unknown" rather than estimating.
- Keep one recommendation per output. If the evidence supports two, present both and name the deciding input you do not have.
- Match the reading level of a working operator. Short sentences. Explain any term the reader may not use daily.

## Quality checks

- Every number, name, date, and quote traces to an input the user supplied.
- No vendor claim is repeated as fact without naming the source.
- Assumptions are listed separately from findings.
- The output answers the original request and nothing else.
- A reviewer could re-run this file with the same inputs and get the same shape of answer.

## Guardrails

- Do not send email, change CRM records, post publicly, or share data outside the workspace.
- Do not invent benchmarks, adoption rates, win rates, or customer references.
- Flag anything that needs a human decision instead of deciding it.

## Source

- Prompt page: https://www.therevenueaireport.com/prompts/make-better-prompts
- Suite: https://www.therevenueaireport.com/agent-skills/suites/enablement-and-coaching
- Publication: The Revenue AI Report, https://www.therevenueaireport.com