agentleFS
ryanmacleanryanmaclean/skills/gantt/SKILL.md

gantt

Skill1 starsChanged 50 days agoMITView on GitHub

Generate and view a Gantt timeline of bop card runs — ANSI terminal (default) or HTML. Use when discussing execution history, parallelism, throughput, or agent performance. Trigger words — gantt, timeline, parallelism, throughput, duration, how long, when did.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Files
SKILL.md

bop gantt — agent execution timeline

Shows horizontal bars per card run, clustered by session, with state colours and duration labels. Default output is ANSI terminal art that fills the current pane.

Quick use

bop gantt              # ANSI chart in terminal (auto-fits pane width)
bop gantt -w 80        # force 80-column width (useful in Zellij panes)
bop gantt --html       # write .cards/bop-gantt.html
bop gantt -o           # write HTML and open in browser

Output modes

FlagModeWhere
(none)ANSI ▓-blocksstdout, fits current terminal/pane
--htmlHTML file.cards/bop-gantt.html
-oHTML + openbrowser

ANSI mode details

  • Auto-detects terminal width via ioctl(TIOCGWINSZ) — works in Zellij panes, tmux, SSH
  • Falls back to $COLUMNS, then 100
  • -w N overrides auto-detection
  • 2-char padding per side for breathing room
  • State colours use ANSI 256-colour palette
  • Bars use ▓ fill blocks with matched foreground+background colour

What it shows

  • Horizontal bars — one per card run, width ∝ wall-clock duration
  • Clusters — runs separated by >30 min gap get their own time axis
  • State colours — pending (blue), running (amber), done (green), failed (red), merged (violet)
  • Duration labels — e.g. 2.7m, 4.8m next to each bar
  • Stats footer — total runs, compute minutes, tokens, cost
  • Legend — coloured dots with state names

Data source

Reads meta.json from every .jobcard/ in .cards/{pending,running,done,failed,merged}/. Uses runs[].started_at and runs[].ended_at for bar placement. Cards with no runs or <2s duration are excluded.

Open-ended runs (no ended_at) are capped at duration_s if available, otherwise 10 minutes.

Complementary views

ViewCommandShows
Gantt (terminal)bop ganttANSI bars in current pane
Gantt (browser)bop gantt -oHTML with hover tooltips
Card listbop list --state allCurrent state of all cards
Events logbop events --limit 50OpenLineage event stream
Calendaropen .cards/bop-agents.icsVEVENTs in Apple Calendar
Inspectbop inspect <id>Single card detail + cost

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.