agentleFS
Sign inStart free
remigius-labsremigius-labs/terminal-charts/skills/chart/SKILL.md

chart

Skill0 starsChanged 2 months agoMITView on GitHub

Use when a user asks how something moved, trended, or changed over time (price, TVL, volume, commits, counts, any series of 8+ numbers), or when an answer would otherwise be a table or paragraph describing a time series.

14 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

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Check command -v chart. If it is missing, copy the chart file that sits next to this SKILL.md (the skill's base directory, shown when the …

    line 12
  2. Distinctive:

    Do not draw charts by hand with ▁▂▃ characters or ASCII art.

    line 56
  3. Distinctive:

    Do not tabulate a time series when a chart is possible.

    line 57
  4. Distinctive:

    Do not surround the chart with high / low / range / volume bullets unless asked.

    line 58
  5. Distinctive:

    Do not chart fewer than 8 points.

    line 59

“Common” is measured: kept by at least 6 in 10 of the 9 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

chart

chart turns numbers on stdin into a braille line chart.

Setup (first use only)

Check command -v chart. If it is missing, copy the chart file that sits next to this SKILL.md (the skill's base directory, shown when the skill loads) onto PATH:

install -m 755 <skill-dir>/chart ~/.local/bin/chart

Or fetch it from the repo and read it before making it executable: curl -fsSL https://raw.githubusercontent.com/remigius-labs/terminal-charts/master/chart -o ~/.local/bin/chart, then less ~/.local/bin/chart, then chmod +x ~/.local/bin/chart. Ask the user before installing anything.

Python 3 is the only requirement. If ~/.local/bin is not on PATH, use the full path.

Drawing

Draw the series instead of describing it. Do not hand-write sparklines with block characters; use the tool so every chart has the same resolution, scale rules and look.

Use

  1. Get the numbers (API, file, git log, whatever). Oldest first.
  2. Pipe them in. Any of these work: one per line, comma-separated, a JSON array, [x, y] pairs, or a raw CoinGecko / DefiLlama JSON response.
  3. Label with -s SYM -p PRICE -d PCT. This prints the standard row ( LINK 12.53 -2.0%) so every chart in the terminal lines up the same way. Use the source's 24h change if it has one (CoinGecko usd_24h_change); omit -p/-d to let the tool use the last point and last-vs-first.
curl -s '<coingecko market_chart url>' | chart -s ETH -p 2496.18 -d 0.07
git log --format=%ad --date=short | sort | uniq -c | awk '{print $1}' | chart -t "commits/day" -r 3
  1. Print the output inside one fenced code block, then at most one sentence of reading. Not five bullet stats. The chart is the answer.

Options you will actually use

  • -r ROWS height, default 5. Use 3 for something small inline, 5 for a proper look.
  • -c COLS width, default 36. Keep under 60 so it never wraps.
  • --labels first → last value on the right, when the title has no numbers.
  • --min/--max to put several charts on one scale so they can be compared by eye.
  • --blocks one-row bars, only when height is not available.
  • --flat when the chart is going to X, Telegram, or anywhere with a proportional font: label on its own line, rows unpadded, nothing depends on spaces.

Reading the picture honestly

  • Left is oldest, right is newest. Each cell is 2 time steps wide and 4 levels tall.
  • The scale fits the data with a floor of ±1% of the mid value. A flat line means the series moved less than 1%, not that nothing happened.
  • More points than width are averaged, fewer are interpolated. Say "smoothed" if the user asks about a spike that isn't visible.

Do not

  • Do not draw charts by hand with ▁▂▃ characters or ASCII art.
  • Do not tabulate a time series when a chart is possible.
  • Do not surround the chart with high / low / range / volume bullets unless asked. One title, one line.
  • Do not chart fewer than 8 points; state the numbers instead.

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.

Check your setup, free