Create a Revenue Report
AnalyzeRevOpsSales
A revenue report with trends, analysis, and visuals that the AI drafts, grades against your criteria, and revises, ready for a leadership review.
This is the skill file version. It carries the prompt text unchanged and adds the inputs to collect, the process, decision rules, quality checks, and guardrails. The one-off prompt lives on its prompt page.
The file
---
name: create-a-revenue-report
description: >-
A revenue report with trends, analysis, and visuals that the AI drafts, grades against your criteria, and revises, ready for a leadership review.
Task type: Analyze. Built for RevOps, Sales.
Use when the request sounds like "Create a Revenue Report".
Do NOT use it to invent numbers, customer names, or quotes that were not supplied.
license: MIT
metadata:
author: The Revenue AI Report
suite: Pipeline, Forecast, and Operations
version: "1.0"
source: https://www.therevenueaireport.com/prompts/create-a-revenue-report
---
# Create a Revenue Report
A revenue report with trends, analysis, and visuals that the AI drafts, grades against your criteria, and revises, ready for a leadership review.
One job only: a revenue report with trends, analysis, and visuals that the AI drafts, grades against your criteria, and revises, ready for a leadership review. Anything outside that job belongs in another file in the Pipeline, Forecast, and Operations 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
- department
- role
- task description
- key references
- criteria
- initial draft
- evaluation
- revised report
- change log
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 an AI assistant tasked with creating a revenue report for the {$DEPARTMENT} department in your role as a {$ROLE}. The goal is to produce a high-quality revenue report that provides valuable insights to inform sales strategies and drive revenue growth. Here are the steps to follow:
1. Review the task description: {$TASK_DESCRIPTION}
2. Familiarize yourself with the key references provided:
<key_references>
{$KEY_REFERENCES}
</key_references>
These references contain important insights and best practices for creating data-driven sales reports. As you work on the revenue report, draw upon the key takeaways from these sources to enhance the accuracy, analytical depth, and visual presentation of your work.
3. Understand the criteria for evaluating the revenue report:
<criteria>
{$CRITERIA}
</criteria>
Your revenue report will be evaluated based on these criteria, so keep them in mind throughout the process.
4. Create an initial draft of the revenue report:
<scratchpad>
Think through the essential components and structure of the report. Consider the data you need to include, the analytical insights you want to highlight, and the visual elements that would effectively present the information.
</scratchpad>
<initial_draft>
Write your initial draft of the revenue report here, drawing upon the key references and incorporating relevant data, analysis, and visuals.
</initial_draft>
5. Evaluate your initial draft against the criteria:
<evaluation>
For each criterion, provide a justification explaining how well the initial draft meets or falls short of that criterion. Then, assign a rating from 1 to 10 based on the provided evaluation rubric.
</evaluation>
6. Refine and iterate on the revenue report:
<scratchpad>
Based on the evaluation, identify areas for improvement and consider ways to enhance the report's data accuracy, analytical insights, visual presentation, and alignment with the key references and industry best practices.
</scratchpad>
<revised_report>
Incorporate your refinements and improvements into a revised version of the revenue report.
</revised_report>
<evaluation>
Evaluate the revised report against the criteria, providing justifications and ratings as before.
</evaluation>
<change_log>
Document the specific changes and updates made in this iteration.
</change_log>
Repeat steps 5 and 6 until you are satisfied with the quality of the revenue report, continuously refining and evaluating against the criteria.
Remember, your goal is to create a comprehensive and insightful revenue report that accurately presents data, offers valuable analytical insights, and effectively communicates information through visuals, all while aligning with industry best practices from the key references.
```
## 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/create-a-revenue-report
- Suite: https://www.therevenueaireport.com/agent-skills/suites/pipeline-forecast-and-operations
- Publication: The Revenue AI Report, https://www.therevenueaireport.com
Install this skill
- For Claude Code, copy the command below into your terminal. It creates the skill folder and saves the file as SKILL.md.
- For another assistant that supports skills, download the file above and place it in a folder named
create-a-revenue-reportinside that assistant's skills directory. - Start a new conversation and ask for the job named on this page. Review the result before using it.
For the supporting files, download the full Pipeline, Forecast, and Operations package too. The single-file command only installs SKILL.md.
mkdir -p "$HOME/.claude/skills/create-a-revenue-report" && curl -fL "https://www.therevenueaireport.com/agent-skills/prompt/create-a-revenue-report/SKILL.md" -o "$HOME/.claude/skills/create-a-revenue-report/SKILL.md"