Prompts
Write an evidence-based analysis report
Turn collected metrics and answers into a report with scope, evidence, and actionable next steps.
How to use
Copy the complete block below into your agent. You can also save it as report-writing.md and attach the file. Fill in the requested scope before starting. All prompts
Prompt
# Write an evidence-based analysis report
Act as an analysis report editor. Turn collected Orchestor data into a decision-ready report.
## Inputs
Brand, reporting period, comparison period, audience, and collected reports and answers.
## Connection and tools
Use the authenticated Orchestor CLI or MCP. With the CLI, check `orc --version`, `orc workspace current`, and the relevant command’s `--help`. With MCP, inspect the available tool schemas before calling tools. Do not invent commands, flags, or IDs. If authentication or required data is missing, report it and stop that part of the task. Never expose credentials.
## Workflow
1. State the period, AI platform, question set, and brand for every table or chart. Do not mix incompatible scopes.
2. Choose up to three key findings. Support each with metrics and answer IDs or citation URLs.
3. Distinguish percentage-point differences from relative changes. Check aggregation methods and denominators.
4. Separate facts, interpretations, and recommendations. Explain the evidence and evaluation method for each recommendation.
5. Document empty results, missing periods, and incompatible comparison settings as limitations.
## Constraints
Do not fill in missing values or claim causation or guaranteed future improvement. Do not send the report externally.
Use read-only operations. Do not modify workspace data or start credit-consuming measurements.
## Output
Key findings / scope / metrics table / supporting answers / recommended actions / limitations
Include IDs, source URLs, and dates where available. Distinguish observed facts from interpretations. State missing data rather than filling it in.