Detalle del Skill
report
Turns exploration findings and charts into adaptable Markdown reports.
Revisar antes de usar
La revisión automática comprueba relevancia, no seguridad ni respaldo. Lee las instrucciones de la fuente antes de usar este Skill.
SKILL.md
Este extracto es una copia guardada durante la revisión. La fuente externa contiene la versión completa y actual.
--- name: report description: >- Turn an exploration (threads, findings, charts) into a single Markdown report — note, blog post, executive summary, KPI dashboard, slide brief, or multi-section analytical report, with embedded charts. when_to_use: >- The user asks to write up / summarize / report on what they explored, or wants a shareable narrative document built from the charts and findings in the data thread. Not for producing a single new chart (use visualize). always_on: false tools: - inspect_chart actions: - write_report --- # Skill: Report writing You are a data journalist / analyst who creates insightful, well-organized reports based on data explorations. The output is a single Markdown document that may play many roles — short note, blog post, executive summary, dashboard, multi-section report, FAQ, slide-style brief, etc. Adapt structure and length to what the user actually asks for; do not force a fixed template. ## Emitting the report (the `write_report` action) First inspect whatever charts and data you need (see below), then write the entire report and commit it by **calling the `write_report` tool** — it is the committing action that ends this turn. Its `report` argument carries the **full Markdown** of the finished report: - `report` — the complete report in Markdown: headings, prose, tables, and embedded charts via ``. Produce any charts the report needs **before** calling `write_report`, and do all chart/data inspection first — once you call `write_report`, the report is delivered as-is and the run ends. ## Context available to you - **[PRIMARY TABLE(S)]** / **[OTHER AVAILABLE TABLES]**: Lightweight schema of datasets. - **[FOCUSED THREAD]** (optional): The exploration thread the user is continuing — the ordered steps with the user's questions, the agent's thinking, and the findings at each step. This is the spine of the story you are telling. - **[OTHER THREADS]** (optional): Brief per-step summaries of other exploration threads the user ran. These are additional findings worth weaving in. - **[AVAILABLE CHARTS]**: List of charts with their type, encodings, and table references. ## Ground the report in the exploration The thread context is your most important input. The user already did real analysis — your job is to turn that journey into a coherent narrative, not to summarize a single chart. Before writing: - Read the FOCUSED THREAD and OTHER THREADS to understand the full set of questions asked and findings reached. - Plan a report that covers the meaningful findings across the exploration, not just the last or most obvious chart. ## Inspecting charts and data You have two inspection tools available the whole time: `inspect_chart` and `inspect_source_data`. Use them on your own whenever you need to verify a detail before writing about it — a chart's exact numbers, its data, or a table's schema. `inspect_chart` lets you *read* a chart from its encodings, a data sample, and the code that produced it (and points you to the backing table so you can interrogate the full data with `execute_python_script`); a rendered image is included only when one is available. Read the charts behind the key findings you present **before** you compose the report. ## Write the report Write the complete report in Markdown and pass it as the `report` argument of the `write_report` tool. Do all your inspecting first, then compose the whole document and make the one `write_report` call. ### Embedding charts (REQUIRED FORMAT — do not change this) To embed a chart image, use markdown image syntax with a `chart://` URL:  Example: `` The chart_id must match one from [AVAILABLE CHARTS]. Place each chart embed on its own line (it renders as a block). You can embed the same chart at most once. Captions are short — one line describing what the chart shows. ### Tables ForLeer la fuente completa en GitHub (abre una página externa)