Report Builder
AnthropicOfficialPublished by Anthropic
- Skill
- Workflow
- Business and productivity
- Apache-2.0
- No issues found
AutoGineer summary
Written by AutoGineer from the skill’s own files, not by the author
Report Builder transforms natural-language requests into repeatable, scheduled business reports. It bridges the gap between raw data and actionable insights by defining metrics, fetching data from various business tools or uploaded files, and generating both a concise chat summary and a structured XLSX workbook. The skill prioritizes consistency by saving report definitions, ensuring that recurring requests are handled efficiently without redundant re-interviews.
What it does
- Converts plain-English descriptions into formal report specifications.
- Fetches data from connected business platforms like accounting software, CRM, and payment processors.
- Supports manual data ingestion via CSV or XLSX uploads when no connectors are available.
- Generates a chat-based summary highlighting key insights and comparisons.
- Produces a multi-tab XLSX workbook including raw data for verification.
- Saves report definitions to enable automated, recurring execution on demand or on a schedule.
When to use it
- When you need to generate a recurring KPI dashboard or metrics summary.
- When an owner asks for specific business numbers on a weekly, monthly, or quarterly basis.
- When you need to consolidate data from multiple sources into a single, repeatable report.
- When you have raw data files (CSV/XLSX) that need to be processed into a formal report format.
Advantages
- Reduces manual effort by automating the data retrieval and report generation process.
- Ensures consistency by saving and reusing report definitions for future runs.
- Provides clear, insight-driven summaries rather than just raw data dumps.
- Flexible data ingestion supports both direct tool integrations and manual file uploads.
Usage examples
- “Can you track sales by location versus last year every Monday?”
- The agent defines the report, pulls the necessary sales data, presents a summary of performance, and saves the definition for future weekly runs.
- “I need to see our AR aging and labor percentage of revenue monthly.”
- The agent confirms the metrics and period, retrieves the financial data, and delivers a formatted report with a summary and an XLSX file.
Install
Download the skill as a ZIP:
https://autogineer.com/agent-skills/anthropics/report-builder/downloadUnzip it into the cross-client skills folder of your project:
mkdir -p .agents/skills && unzip report-builder.zip -d .agents/skills
Documentation by Anthropic
Report Builder
The owner describes a report once. You build it, run it, and save the definition so it never has to be described again.
Owners are pulling numbers out of three dashboards by hand and trying to find the story themselves. The job is to end that.
Step 1 — Check for an existing definition
Before anything else, read reference/saved_reports.md and check whether this report already exists. Also check for a report-definitions.md in the working directory — that's where definitions land when the skill folder isn't writable (see Step 7).
If the owner says "same report as last time," "run the weekly one," or names a report you have a definition for, skip straight to Step 4 and run it. Re-interviewing someone about a report they already defined is the fastest way to make this skill feel broken.
If nothing matches, continue.
Step 2 — Turn the description into a spec
Owners describe reports loosely: "every Monday, sales by location versus last year, AR aging, and labor percent." That sentence contains four separate decisions. Resolve them into a spec using the format in reference/report_spec.md:
Metrics — each one named, with its formula and source
Grouping — by location, product, customer, channel, rep
Comparison — versus prior period, versus last year, versus target
Period — the window each run covers
Cadence — one-off, weekly, monthly, quarterly
Infer what you reasonably can. "Sales by location vs last year" gives you the metric, the grouping, and the comparison — don't ask about those. Ask only about what's genuinely ambiguous, and ask it in one batch rather than one question at a time.
The two questions worth asking almost every time:
Which period does each run cover — calendar month, trailing 30 days, month-to-date?
Is a number like "labor percent" measured against revenue or against total costs?
Getting these wrong produces a report that looks right and is quietly wrong, which is worse than asking.
Step 3 — Confirm the spec, once
Show the resolved spec back in a compact block. Ask for one confirmation, then build. Do not walk the owner through the spec field by field — they described this in one sentence and expect one answer.
If they correct something, apply it and go. Do not re-confirm a second time.
Step 4 — Pull the data
Dispatch every source call in a single parallel batch. See reference/data_sources.md for the metric-to-tool mapping.
Sources, tried simultaneously:
The ledger — MYOB, NetSuite, QuickBooks, Xero, or Zoho Books, whichever is connected; peers per
../../shared/connector-neutrality.md. P&L lines, revenue, expenses, AR aging, AP, class and location splits. MYOB is P&L, AR, and payables only, three financial years back. If two ledgers are connected, ask which is the source of record and take totals from that oneHubSpot — deals, stages, owners, close dates, pipeline value
PayPal, Square, Stripe — settlements, fees, refunds, transaction detail
Shopify — orders, SKU-level revenue, fulfillment status
Ramp, Expensify — card spend and expense detail. Both are read sources here; Expensify is read-only search
If a source errors or returns nothing, record it and move on. Never block the whole report on one bad connector.
No connectors at all is a supported path, not a failure. Ask for a CSV or XLSX export, read it, and build the identical report from the file. Say so plainly: "I don't see a connected data source. Export the sales report from your system and drop it here — I'll build the same report from that." Owners with tool sprawl live in this mode, and the report is just as good.
Step 5 — Compute and sanity-check
Compute every metric named in the spec. Then check the results before showing them. Read reference/gotchas.md for the failure modes that actually happen.
The checks that catch real errors:
Period boundaries. A partial current month compared against a full prior month always looks like a collapse. Either compare like-for-like or label the partial period explicitly.
Double-counting. A Shopify order and its Stripe settlement are one sale. If both sources are connected, pick one as the revenue source and note which.
Empty groups. A location with no sales this period should appear with a zero, not vanish. A disappearing row reads as a data problem.
Totals that don't tie. If the grouped rows don't sum to the total, say so rather than publishing a number you can't defend.
Step 6 — Deliver
Two artifacts, always, in this order.
The chat summary comes first. Follow reference/output_template.md. Lead with what changed and what it means, not with a table dump. The owner asked for a report because they want a decision, not a spreadsheet.
Writing rules, same as every reporting skill in this plugin:
Numbers lead, words follow. Not "sales were strong" — "USD 43,200, up 8% versus last year."
Every number carries its comparison. A figure with no baseline is a missed insight.
Name the outlier. "Portland is down 22%, the only location below last year" beats "results were mixed."
Three findings maximum in the summary. The workbook holds everything else.
Then the XLSX. One tab per metric group, a summary tab first, raw pulled data on a final tab so the owner can check your math. Build it with a script rather than by hand.
Then the report page, per the owner's stored output preference — never default to a markdown file. Check the ## Business context block's Output preference (shared style guide rule, ../../shared/artifact-style.md):
Visual artifact (the default): render the report as an HTML page in the house style — each headline metric is a stat tile with its comparison as the context line; the grouped rows (by location, product, rep) are a table with right-aligned tabular-nums; any metric versus target carries a status pill (good on target, warn slipping, critical missed); the three findings open the page in their own panel; "n/a" sources go in one quiet footer line. Additive to the chat summary and the workbook, never a replacement.
docx / md / notion / canva preference: deliver the same content in that form — a DOCX or markdown file, a Notion page created via the connector (named destination, never overwriting), or a Canva Doc created via the Canva connector (a new design each run, named with the date; tables become lists); fall back to the visual artifact if Notion or Canva is not connected — and say that is why. The XLSX still ships alongside.
Best for skill: use the visual artifact — a report is read on screen and compared week to week.
Step 7 — Save the definition
Append the spec to reference/saved_reports.md with the date it was created and the cadence. This is what makes the report recurring instead of one-off.
If that file can't be written — the skill folder is read-only in most installed runtimes — write the definition to report-definitions.md in the owner's working directory instead and say where it went. A definition that silently failed to save is the same bug as never saving it.
If the owner asked for a cadence, confirm it in one line: "Saved. I'll run this the first Monday of each month." Scheduling is a property of this skill — no separate command needed.
After the run
One line: the report ran and the definition is saved. Then the single most relevant next step, with at most two others nearby:
"The weekly pack, on schedule" runs
/report-packto wrap this in context on a cadence."How's the business doing?" runs
business-pulsefor the picture around these numbers."Cash forecast" runs
cash-flow-snapshotwhen the report raised a cash question.
Max three offers. Never repeat an offer the owner declined this session.
What not to do
Do not interview the owner about a report they already defined. Check
saved_reports.mdfirst, every time.Do not ask permission to pull data. The skill was invoked. Run it.
Do not invent a number. If a source returned nothing, write "n/a" and name the source. A plausible-looking guess in a report the owner forwards to their bank is a serious failure.
Do not lead with the table. The summary is the product; the workbook is the appendix.
Do not treat "no connectors" as a blocker. The CSV path is a first-class mode.
Reference files
reference/report_spec.md— the spec format, with worked examplesreference/data_sources.md— metric to connector mapping, with fallbacksreference/output_template.md— exact structure for the chat summary and the workbookreference/saved_reports.md— stored report definitions, appended to over timereference/gotchas.md— the failure modes that produce confidently wrong reports
Using a tool that isn't listed
The connectors named in this skill are the tested paths, not a wall. If the owner wants this flow to use a tool that isn't connected or listed, offer build-connector — it checks the connector directory first and connects through Zapier otherwise, never hand-building against a raw API. Once the connection exists, the tool joins this skill like any other optional connector, under the same approval gates.
Files
- ATTRIBUTION.mdAdded by AutoGineer909 B
- LICENSELicence file added by AutoGineer11.3 KiB
- SKILL.md10.0 KiB
- reference/data_sources.md9.9 KiB
- reference/gotchas.md3.9 KiB
- reference/output_template.md3.3 KiB
- reference/report_spec.md3.8 KiB
- reference/saved_reports.md1.9 KiB
LICENSE
Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/
TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
1. Definitions.
"License" shall mean the terms and conditions for use, reproduction,
and distribution as defined by Sections 1 through 9 of this document.
"Licensor" shall mean the copyright owner or entity authorized by
the copyright owner that is granting the License.
"Legal Entity" shall mean the union of the acting entity and all
other entities that control, are controlled by, or are under common
control with that entity. For the purposes of this definition,
"control" means (i) the power, direct or indirect, to cause the
direction or management of such entity, whether by contract or
otherwise, or (ii) ownership of fifty percent (50%) or more of the
outstanding shares, or (iii) beneficial ownership of such entity.
"You" (or "Your") shall mean an individual or Legal Entity
exercising permissions granted by this License.
"Source" form shall mean the preferred form for making modifications,
including but not limited to software source code, documentation
source, and configuration files.
"Object" form shall mean any form resulting from mechanical
transformation or translation of a Source form, including but
not limited to compiled object code, generated documentation,
and conversions to other media types.
"Work" shall mean the work of authorship, whether in Source or
Object form, made available under the License, as indicated by a
copyright notice that is included in or attached to the work
(an example is provided in the Appendix below).
"Derivative Works" shall mean any work, whether in Source or Object
form, that is based on (or derived from) the Work and for which the
editorial revisions, annotations, elaborations, or other modifications
represent, as a whole, an original work of authorship. For the purposes
of this License, Derivative Works shall not include works that remain
separable from, or merely link (or bind by name) to the interfaces of,
the Work and Derivative Works thereof.
"Contribution" shall mean any work of authorship, including
the original version of the Work and any modifications or additions
to that Work or Derivative Works thereof, that is intentionally
submitted to Licensor for inclusion in the Work by the copyright owner
or by an individual or Legal Entity authorized to submit on behalf of
the copyright owner. For the purposes of this definition, "submitted"
means any form of electronic, verbal, or written communication sent
to the Licensor or its representatives, including but not limited to
communication on electronic mailing lists, source code control systems,
and issue tracking systems that are managed by, or on behalf of, the
Licensor for the purpose of discussing and improving the Work, but
excluding communication that is conspicuously marked or otherwise
designated in writing by the copyright owner as "Not a Contribution."
"Contributor" shall mean Licensor and any individual or Legal Entity
on behalf of whom a Contribution has been received by Licensor and
subsequently incorporated within the Work.
2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of,
publicly display, publicly perform, sublicense, and distribute the
Work and such Derivative Works in Source or Object form.
3. Grant of Patent License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
(except as stated in this section) patent license to make, have made,
use, offer to sell, sell, import, and otherwise transfer the Work,
where such license applies only to those patent claims licensable
by such Contributor that are necessarily infringed by their
Contribution(s) alone or by combination of their Contribution(s)
with the Work to which such Contribution(s) was submitted. If You
institute patent litigation against any entity (including a
cross-claim or counterclaim in a lawsuit) alleging that the Work
or a Contribution incorporated within the Work constitutes direct
or contributory patent infringement, then any patent licenses
granted to You under this License for that Work shall terminate
as of the date such litigation is filed.
4. Redistribution. You may reproduce and distribute copies of the
Work or Derivative Works thereof in any medium, with or without
modifications, and in Source or Object form, provided that You
meet the following conditions:
(a) You must give any other recipients of the Work or
Derivative Works a copy of this License; and
(b) You must cause any modified files to carry prominent notices
stating that You changed the files; and
(c) You must retain, in the Source form of any Derivative Works
that You distribute, all copyright, patent, trademark, and
attribution notices from the Source form of the Work,
excluding those notices that do not pertain to any part of
the Derivative Works; and
(d) If the Work includes a "NOTICE" text file as part of its
distribution, then any Derivative Works that You distribute must
include a readable copy of the attribution notices contained
within such NOTICE file, excluding those notices that do not
pertain to any part of the Derivative Works, in at least one
of the following places: within a NOTICE text file distributed
as part of the Derivative Works; within the Source form or
documentation, if provided along with the Derivative Works; or,
within a display generated by the Derivative Works, if and
wherever such third-party notices normally appear. The contents
of the NOTICE file are for informational purposes only and
do not modify the License. You may add Your own attribution
notices within Derivative Works that You distribute, alongside
or as an addendum to the NOTICE text from the Work, provided
that such additional attribution notices cannot be construed
as modifying the License.
You may add Your own copyright statement to Your modifications and
may provide additional or different license terms and conditions
for use, reproduction, or distribution of Your modifications, or
for any such Derivative Works as a whole, provided Your use,
reproduction, and distribution of the Work otherwise complies with
the conditions stated in this License.
5. Submission of Contributions. Unless You explicitly state otherwise,
any Contribution intentionally submitted for inclusion in the Work
by You to the Licensor shall be under the terms and conditions of
this License, without any additional terms or conditions.
Notwithstanding the above, nothing herein shall supersede or modify
the terms of any separate license agreement you may have executed
with Licensor regarding such Contributions.
6. Trademarks. This License does not grant permission to use the trade
names, trademarks, service marks, or product names of the Licensor,
except as required for reasonable and customary use in describing the
origin of the Work and reproducing the content of the NOTICE file.
7. Disclaimer of Warranty. Unless required by applicable law or
agreed to in writing, Licensor provides the Work (and each
Contributor provides its Contributions) on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
implied, including, without limitation, any warranties or conditions
of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
PARTICULAR PURPOSE. You are solely responsible for determining the
appropriateness of using or redistributing the Work and assume any
risks associated with Your exercise of permissions under this License.
8. Limitation of Liability. In no event and under no legal theory,
whether in tort (including negligence), contract, or otherwise,
unless required by applicable law (such as deliberate and grossly
negligent acts) or agreed to in writing, shall any Contributor be
liable to You for damages, including any direct, indirect, special,
incidental, or consequential damages of any character arising as a
result of this License or out of the use or inability to use the
Work (including but not limited to damages for loss of goodwill,
work stoppage, computer failure or malfunction, or any and all
other commercial damages or losses), even if such Contributor
has been advised of the possibility of such damages.
9. Accepting Warranty or Additional Liability. While redistributing
the Work or Derivative Works thereof, You may choose to offer,
and charge a fee for, acceptance of support, warranty, indemnity,
or other liability obligations and/or rights consistent with this
License. However, in accepting such obligations, You may act only
on Your own behalf and on Your sole responsibility, not on behalf
of any other Contributor, and only if You agree to indemnify,
defend, and hold each Contributor harmless for any liability
incurred by, or claims asserted against, such Contributor by reason
of your accepting any such warranty or additional liability.
END OF TERMS AND CONDITIONS
APPENDIX: How to apply the Apache License to your work.
To apply the Apache License to your work, attach the following
boilerplate notice, with the fields enclosed by brackets "[]"
replaced with your own identifying information. (Don't include
the brackets!) The text should be enclosed in the appropriate
comment syntax for the file format. We also recommend that a
file or class name and description of purpose be included on the
same "printed page" as the copyright notice for easier
identification within third-party archives.
Copyright [yyyy] [name of copyright owner]
Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
Syntax-file, code seperations,code vault integeted with css definition.
Pre-recordec, pre-tested, elements to capture elements into Packeted-User-Relations to capture - [
pre-requisites, statements, recorded-cams
, cams-data
, data, input()
]
Requirements and compatibility
Written for: Claude Code, Claude apps
Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta
“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.
Needs: Declares allowed tools
Security
No issues found by our static scan· No issues found
A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.
Attribution and licence
- Published by
- Anthropic
- Publisher
- Anthropic (Official)
- Source
- anthropics/knowledge-work-plugins · small-business/skills/report-builder · commit e050c2e
- Licence
- Apache License 2.0 (redistribution allowed)
- LICENSE (added by AutoGineer from LICENSE)
- ATTRIBUTION.md (written by AutoGineer)
- Synced
AutoGineer is not affiliated with or endorsed by Anthropic or Anthropic.
Download ZIP
The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download report-builder.zip