malloy-analysis-report · git:20261012.55216ae · 2026-10-12 · sha256 203fe73836d5bd8f
malloy-analysis-report git:20261012.55216aeA
Immutable. This exact content never changes and is served at /api/v1/blob/203fe73836d5bd8f.
No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_y3norkf2xu3dvwgd/203fe73836d5bd8f45557e5e3ec861276dfd60bd1819ea8385d2335f9f29784e.json
Then /plugin install malloy-analysis-report@markdownregistry-y3norkf2xu3dvwgd in Claude Code. It installs this exact version, the one graded A here, pinned to the commit it was graded at, and leaves it there.
---
name: malloy-analysis-report
description: Combine validated Malloy queries into a report (a linear report, read top to bottom). Use when the user asks to "create a report", "combine these into a report", or wants a persistent multi-query artifact.
---
<!--
Copyright (c) Credible Data Inc.
SPDX-License-Identifier: MIT
-->
# Creating Reports
An ad-hoc report is a Publisher **report** with `layout=linear`: a `.malloy` file at the package root, `<slug>.malloy` (unless the user asks for another location), that combines markdown narrative with live Malloy queries. An ad-hoc report is written as `run:` cells, which Publisher reads and which convert to tiles when saved in the Console; when the queries are views on a source, or the report will be kept and edited, `skill:malloy-reports` describes the tile form (`tiles=[…]`) to author instead. Load `skill:malloy-reports` for the full format and authoring rules; this skill covers when to build one and how to design good report content (cells, chart annotations, narrative structure). Never write a new `.malloynb`, and do not create a `notebooks/` or `dashboards/` directory for it.
> **Tool names** are written bare here - `get_context`, `execute_query`, `search_malloy_docs`. The exact prefixed name depends on the host surface; match each against the tools you actually have.
## Before building a report
1. **Run each query first** via `execute_query` to verify it works and returns expected results.
2. **Explain the results** to the user as you go: walk through the analysis step by step.
3. **Then assemble the report** once the analysis is validated.
Do NOT build the report in the same turn as `execute_query`. Explain first, then build.
## Filters are inherited from the model, don't declare them in the report
Do not declare filters in an ad-hoc report. If the source declares `given:` parameters (or legacy `#(filter)` annotations), Publisher renders the controls, parses caller parameters, and applies them server-side automatically: the report inherits and displays them with no extra work. If the analysis needs a knob the source doesn't expose, the right move is to add a `given:` to the source itself, not to wedge a filter widget into the report. `#(filter)` is deprecated in favour of native Malloy `given:` parameters. Never add a `#(filter)` annotation: every use, including `required`, `implicit`, and date/number ranges, has a `given:` form. The `malloy-model` skill covers this under § Legacy: Parameterizable Filters. For a curated report with its own filter controls on top of the model, see `skill:malloy-reports` instead.
## What goes in the report
Do NOT add an H1 heading in any markdown (use H2 and below for sections); the `title` in the `## artifact` tag serves as the title. To redo the structure rather than tweak one cell, rewrite the report file end-to-end.
Markdown cells own narrative; query cells own a single Malloy query whose chart annotation tells the renderer how to display the result. Markdown supports H2 headings, lists, bold, and inline code. Keep narrative cells short, one idea per cell, so the rendered output reads as a story instead of a wall of text.
The file starts with `## artifact { layout=linear title="..." }`, then the `import` for the model file (relative to the report's own location: `"order_analysis.malloy"` from the package root). Definitions (`import`, `source:`, `query:`, `given:`) come before the first markdown or `run:`. Prose is `##|(markdown)` ... `|##` for a block (body on the lines between) or `##(markdown) text` for one line. Each `run:` is a query cell, and its tags sit directly above it with nothing between. A `#"` directly above the `run:` is its caption. Trailing prose is `##(markdown)`, never `#(markdown)` or `#"`.
This is the cell format, the quick form for an ad-hoc report; for a report that will be kept and edited, write the tile form in `skill:malloy-reports` (`## artifact { layout=linear tiles=[…] }`) instead.
Each `run:` must be a standalone query (for example `run: source -> { ... }`). The `import` is file-wide: query cells never repeat it. Compile the file with `/compile` (`"scope": "file"`, at the path `<slug>.malloy`) before saving; a report compiles as a model, so its errors come back there. A complete report:
```malloy
## artifact { layout=linear title="Sales report" }
import "order_analysis.malloy"
##|(markdown)
## Overview
What is driving sales, and which categories carry it? The queries below cover every order in the model.
|##
# big_value
run: order_analysis -> {
aggregate:
# label="Revenue"
# currency
total_revenue
# label="Orders"
# number=auto
order_count
}
##(markdown) ## Trend: how does revenue move over time?
#" Revenue by month
# line_chart
run: order_analysis -> {
group_by: order_date.month
aggregate: total_revenue
order_by: 1
}
##|(markdown)
## Breakdown
Which categories account for the most revenue?
|##
#" Top ten categories by revenue
# bar_chart
run: order_analysis -> {
group_by: category
aggregate: total_revenue
order_by: total_revenue desc
limit: 10
}
##(markdown) ## Key takeaways: what to look at next.
```
A well-structured report typically follows this pattern:
```
[Markdown] ## Overview: what question are we answering, what data is in scope (date range, entity count)
[Malloy] KPI cell: headline numbers (e.g., # big_value, or # dashboard with nested # big_value cells)
[Markdown] ## Trend: describe what we should look for over time
[Malloy] Time-series cell (e.g., # line_chart on a date dimension)
[Markdown] ## Breakdown: where the signal is
[Malloy] Categorical cell (e.g., # bar_chart on a categorical dimension)
[Markdown] ## Key takeaways: what the user should walk away with
```
Use this as a default; deviate when the analysis warrants. A grounded report names the time range and entity count up front so every number that follows has context.
## Choosing chart types and annotations
Read `skill:malloy-charts` before picking visualizations: it owns chart-type selection, properties, and the placement rules for chart annotations. `skill:malloy-queries` covers Malloy query patterns and the critical placement rules for chart-annotation tags.
When in doubt:
- KPIs / single numbers -> `# big_value`, often nested inside `# dashboard`.
- Trend over time -> `# line_chart`, usually on the primary date dimension.
- Category comparisons -> `# bar_chart`, ordered by the metric.
- Tabular data with many columns -> a plain table cell with `# table.size=fill`.
- Multiple coordinated charts -> `# dashboard` with `nest:` blocks.
Annotations go **before** `run:`, never inside curly braces:
```malloy
# bar_chart
run: source -> {
group_by: category
aggregate: revenue
order_by: revenue desc
limit: 10
}
```
A `# dashboard` cell composes nested views, useful for KPIs alongside a trend in a single cell. Each `nest:` is a tile; any top-level `aggregate:` measures render as KPI cards. For a fixed grid, use `# dashboard { columns=N }` with `# colspan` on each tile (see `skill:malloy-charts`):
```malloy
# dashboard { columns=2 }
run: source -> {
nest:
# colspan=2
# big_value
kpis is {
aggregate:
# label="Revenue"
# currency
total_revenue
# label="Orders"
# number=auto
order_count
}
nest:
# line_chart
trend is {
group_by: order_date.month
aggregate: total_revenue
order_by: 1
}
}
```
Key rendering rules to keep in mind when shaping a cell:
- FIRST `group_by` = x-axis, FIRST `aggregate` = y-axis.
- Override field roles with `# x`, `# y`, `# series` on individual fields.
- For multiple measure series, place `# y` above the `aggregate:` keyword.
- One aggregate per chart view: use `# dashboard` with nested views for multiple charts.
- Use `# table.size=fill` for standalone table queries.
## Editing an existing report
For small targeted changes (fix one cell, insert one new cell), edit the cell's statement or markdown in place rather than recreating the whole report. For structural rewrites (reordering many cells, changing the narrative arc), rewrite the report file. An existing `.malloynb` is read, not edited: to change its story, write a `.malloy` report. An existing report's tag that says `kind=notebook` is the deprecated spelling of `layout=linear`; fix it when you edit the file.
## IMPORTANT
You CANNOT see the rendered output of report cells. Do not claim to see charts, values, or patterns from report cells you haven't explicitly executed via `execute_query`. If you need to analyze results, run the query via `execute_query` first.