Guide · Agent skill
How to use the Build Analytical Report agent skill (build-report)
Updated · written with AI from the project's own documentation and checked against our catalogue data
The build-report skill is an agent skill from the MiMo-Code project (MIT licence) that tells an AI agent how to package a finished analysis as a durable report. It leads with the main answer and decision implication, then sets out evidence-backed findings, caveats, recommendations and a sources section. This guide explains what the skill changes, how to install it, how to ask for it in plain language, and what it needs and touches.
Quick start
- 1Download the ZIP. Download the build-report ZIP from this page.
- 2Unzip into a skills folder. Unzip it into ~/.claude/skills/ for personal use, or into the project's .claude/skills/ folder.
- 3Or upload in the Claude apps. In the Claude apps, open Settings → Capabilities → Skills and upload the skill.
- 4Run your analysis first. Have the agent complete the underlying analysis or query work, since this skill structures the finished results.
- 5Ask for a report. Describe the audience, decision and format, for example HTML for a leadership team.
- 6Review the artifact. Check the headline numbers, charts, sources and caveats before sharing the file.
What is the build-report skill and what does it make the agent do?
An agent skill is a folder of instructions that an AI agent loads when a task matches the skill's description. This skill applies when you need a report that will outlast the chat, not a quick answer. The agent runs the analysis first, then uses this workflow to structure the reader-facing document.
The skill says the report should open with the answer, state the magnitude and the decision it implies, and only then cover methodology. Findings must be backed by evidence, and the agent is asked to separate verified facts from likely explanations, assumptions and open questions.
- Answer-first executive summary with decision implication
- Key findings with charts or tables only where they support a finding
- Recommendations tied to evidence, expected impact and an owner or next action
- Risks and limitations section covering data gaps and interpretation limits
- Sources and methodology section covering definitions, scope and source details
Which delivery format does the agent pick?
If you name a format, the agent honours it. Otherwise the skill defaults to Markdown, the most portable option. Self-contained plain HTML is used when a browser-readable report is useful and the host can render or inspect it. PDF, DOCX, slides or other formats are used only when you request them or the destination clearly requires them, and the host has suitable tools.
- Markdown (default)
- Self-contained plain HTML for a browser-readable report
- PDF, DOCX, or slides when requested or clearly required
How do you install the build-report skill?
You can install the skill in either of two ways. For a personal setup, download the ZIP from this page and unzip it into ~/.claude/skills/. For a single project, unzip it into the project's .claude/skills/ folder instead.
If you use the Claude apps, you can instead upload the skill under Settings → Capabilities → Skills.
- Personal: unzip into ~/.claude/skills/
- Per project: unzip into .claude/skills/ inside the project folder
- Claude apps: Settings → Capabilities → Skills, then upload
How do you trigger the skill with natural requests?
You do not need a special command. Ask for a durable deliverable in plain words, and name the format and audience if you have them. The skill is meant for cases where a manager or stakeholder needs to act on the result.
If you only want a quick answer, say so. The skill itself says that when no file is wanted, the agent should give the same answer-first structure concisely in chat.
- "Turn these query results into a report my manager can act on."
- "Write an analytical report on last quarter's churn as an HTML file for the leadership team."
- "Give me a short inline brief on this, no file needed."
What does a good result look like?
Before handing back the file, the skill asks the agent to recalculate headline values and comparisons from the reviewed evidence, check that every chart matches its source data, and check titles, labels, units, denominators, date ranges and sorting. For HTML, PDF, DOCX or slides, the agent should render or inspect the actual artifact when the host supports it.
The agent is also told to keep credentials, local temporary paths and placeholder provenance out of the report. It returns the primary artifact path plus only the supporting notebook, SQL, data or chart files that are relevant.
- Headline numbers recalculated from the reviewed evidence
- Chart values checked against source data
- Units, date ranges and sorting checked
- Rendered artifact inspected when the host supports it
What do the optional helpers need, and what do they touch?
The core skill is instructions only. The package includes companion helpers for converting reports. The report-to-Google-Doc helper converts an HTML report into a DOCX for upload to Google Drive. It needs Python with python-docx installed, and it needs a Google Drive connector in the host agent for the upload. It does not call Google APIs itself.
The package does include scripts, so the listing states that it runs scripts. It does not use the network, according to the listing. There are also companion skills for Google Slides and PDF conversion, which each start from an existing HTML report and are invoked only when you explicitly ask for that output.
- Runs scripts: yes (for the DOCX/Google Doc helper and related files)
- Uses network: no
- Python with python-docx: needed only for the DOCX/Google Doc helper
- Google Drive connector: needed only for Google Doc upload
- The helper does not call Google APIs itself
What people use it for
- Turning SQL query results into a findings report a manager can act on
- Producing a recurring written findings document for stakeholders
- Writing a report that separates verified facts from assumptions and open questions
- Converting an existing HTML analytics report into a Google Doc via the companion helper (requires the Drive connector)
Frequently asked questions
Is the build-report skill free to use?
The source is listed under the MIT licence, which governs use of the code. This page does not state any price, and the skill itself is a folder of instructions downloaded from this directory.
What do I need to install the build-report skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ or a project's .claude/skills/ folder. In the Claude apps you can instead upload it under Settings → Capabilities → Skills.
Does build-report need Python?
The core report workflow is instructions. Python with python-docx is needed only for the DOCX and Google Doc helper, not for writing a Markdown or HTML report.
Does the skill connect to Google Drive for me?
No. The report-to-Google-Doc helper converts an HTML report to DOCX. Uploading to Google Drive requires a Google Drive connector in the host agent, and the helper does not call Google APIs itself.
Can the skill guarantee the sources in my report are real?
No. The skill forbids inventing sources and asks the agent to list only real systems, tables and files, but it cannot verify provenance the agent does not have access to. Check the sources section yourself.
How is this different from just asking an AI for a summary?
A plain summary is often a quick chat answer. This skill adds a fixed structure for durable deliverables: answer first, evidence, caveats, recommendations and sources, plus a QA pass on numbers and charts.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use build-report if you are an analyst or team that needs finished analysis turned into a report that separates facts from assumptions and can be acted on. Skip it for one-line answers or when you need guaranteed source provenance that the agent cannot access.
Download the skill