agentleFS
cgoinglovecgoinglove/thursday-agent/skills/data-report/SKILL.md

data-report

Skill56 starsChanged 46 days agoMITView on GitHub

Answers questions that turn on real numbers, taken from where they are published. Use it for a cost, a trend, a market size, a company, which to pick, buy or wait, the weather on given days, or an amount in another currency, with a chart when it helps.

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Every form opens with the answer and its two or three numbers.

    line 28
  2. Very specific:

    When the form calls for a page, it is a document: write it in Markdown in a file of your own and put it, with the artifact skill's script — …

    line 61
  3. Very specific:

    Run it again to replace a figure, and after every later put.

    line 82

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Data report

The form comes from the question

Pick one form and read only its file in references/ before collecting anything: it says what to collect, what the final text holds, and when a page earns its place.

The questionForm
Anything else with numbers in itbrief.md
Which of these (products, plans, places, companies)?comparison.md
How big is this market, how much could we sell?market-size.md
How has X moved, and why?trend.md
How is this company doing, how were its results?company.md
Where is it cheapest to buy X right now?price-check.md
Should I buy / sign / switch — or wait?decision.md

Their own figures, to keep and go on with — a ledger or a budget, receipts, a bank's or a card's export, a list they add to — are not a form here: they are a sheet, a real .xlsx (the artifact skill, references/sheet.md), totals and summaries by formula, with a page only when they also ask for one.

Every form opens with the answer and its two or three numbers; a reader who stops after the first lines has what they asked for. A title says the finding ("Rent rose faster than pay"), not the topic.

Numbers by script, not by hand

The skill's script is in scripts/ of this skill's folder. node runs it; nothing to install.

S=<this skill's folder>/scripts
# A series into CSV, with its source written into the file. It prints the rows' shape and both ends.
node $S/fetch.mjs fred DGS10,MORTGAGE30US --from 2020 \
  --label "10-year Treasury,30-year mortgage" --out <scratch>/rates.csv
node $S/fetch.mjs fred SP500,NASDAQCOM --from 2025-01 --label "S&P 500,Nasdaq" --out <scratch>/px.csv

A --label names the columns in the order you asked for them, so give one for every column or none. node $S/fetch.mjs with no arguments lists every source and option.

Two more answer in a line, with no CSV and no page:

# The forecast a line a day; past the 16 days it reaches, the same days over the last five years
node $S/weather.mjs "<place>[, <country code>]" <from YYYY-MM-DD> [<to>]   # --f for °F
# An amount at today's rate, with the rate's date and source; fetch.mjs fx is the rate over time
node $S/fx.mjs 150 USD EUR,JPY

references/sources.md says which source holds what, the series ids worth knowing, and what the script cannot reach. A CSV you build from a page or a file you were given takes the same shape: a # source: <url> line (and # fetched: YYYY-MM-DD) above a header row.

A page: a document, with charts drawn into it

When the form calls for a page, it is a document: write it in Markdown in a file of your own and put it, with the artifact skill's script — the first put makes it, styled, in your folder under artifacts/. Never write chart SVG by hand: leave an empty <figure id="…"></figure> where each chart goes in the Markdown, put the document, then fill every figure in one bash call. Both scripts ship with the app:

node "$THURSDAY_SKILLS/artifact/scripts/document.mjs" put <page> <scratch>/<page>.md
C="$THURSDAY_SKILLS/artifact/scripts/chart.mjs"
node $C "$THURSDAY_ARTIFACTS/<page>.html" rates <scratch>/rates.csv \
  --title "Mortgage rates followed the 10-year down" --unit "%" --mark "2024-09=First Fed cut"
node $C "$THURSDAY_ARTIFACTS/<page>.html" px <scratch>/px.csv --index --title "…"

Each figure carries its source link, the fetch date and the rows behind it with a CSV download, so the page needs no separate data section. A line for dates, bars for categories (largest first, --highlight the one that matters, named exactly as the row is); --kind column for a value per period, --kind donut for one whole split in five parts or fewer, --kind stacked for what each row is made of (--share to compare the make-up rather than the size); --index when series in different units are compared; --mark for each dated event the text explains, inside the range drawn; --locale with the reader's language tag (de, ja, pt-BR) writes numbers and dates their way. Run it again to replace a figure, and after every later put. node $C with no arguments lists every option.

A table a form asks for — the comparison matrix, a results table, the driver rows — is a Markdown table in the document, number columns aligned right (---:) and the best cell in each row in **bold**. Never type a number into one by hand: paste what a script printed, or the figure from the page you read, and keep its source in the row or under the table.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.