agentleFS
tatashbartatashbar/Economic-Modeling-Studio/.agents/skills/chart-pack/SKILL.md

chart-pack

Skill4 starsChanged 6 days agoMITView on GitHub

Produces a chart pack from code: fan charts, shock decompositions, scenario comparisons, with consistent style and labelling.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 4 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    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. Very specific:

    If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it.

    line 25
  2. Very specific:

    Collaboration: Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and …

    line 27
  3. Distinctive:

    Check accessibility (colors, fonts) and consistency

    line 46
  4. Distinctive:

    After the chart list: confirm messages

    line 51
  5. Distinctive:

    After drafts: review readability

    line 52
  6. Distinctive:

    Every chart shows units, sources and vintage

    line 66

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “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
<!-- Generated from .claude/skills/chart-pack/SKILL.md by tools/sync_agents.py. Edit the source, then run the script. -->

/chart-pack — Chart Pack

Category: Documentation · Primary agent: visualization-dashboard-specialist

Produces a chart pack from code: fan charts, shock decompositions, scenario comparisons, with consistent style and labelling.

Arguments: whatever the user wrote after the command name.

Purpose

Produce a chart pack for a forecast round, brief or presentation, generated entirely from code: fan charts, shock decompositions, scenario comparisons and supporting charts, each labeled with units, sources and vintage, accessible and consistent in style. The output regenerates from one command when data change.

Use it when model results must be communicated visually to decision-makers or in publications.

Do not use it when an interactive monitoring tool is needed rather than static charts; design a dashboard with the visualization specialist.

Before you start

  1. Check required inputs. For each input below record FOUND or ABSENT (never 'assumed'):
    • Results files If a required input is ABSENT, that part is NOT ASSESSED — NO DATA: do not estimate or invent it; name what is missing and which skill produces it. If all required inputs are absent, stop and say so.
  2. Check confidentiality. Identify the data classification level of the inputs (.claude/docs/confidentiality-and-ai-use.md). Do not proceed with restricted or confidential data in a way the policy does not allow.
  3. Collaboration. Follow .claude/docs/collaboration-protocol.md: ask questions first, present options, get approval before writing files, and update production/session-state/active.md after each approved section.

Agents

  • visualization-dashboard-specialist — primary agent; coordinates the work and integrates results
  • forecast-evaluation-specialist — Evaluates forecasts

Each agent is defined in .claude/agents/<name>.md. If your tool runs subagents, run these agents as subagents, in parallel where the steps are independent; otherwise read each agent's file and apply its instructions in turn. Subagents only write to the paths named in your instructions.

Key design decisions (present options, let the user choose)

DecisionTypical optionsWhat it changes
Chart listone chart per messageFocus
Uncertaintyfan charts, bands, scenario linesHonesty
Formatpublication, slides, webSizes and fonts
Stylestudio template, institutional templateConsistency

Workflow

  1. Choose a chart list matching the message
  2. Generate charts from scripts (never by hand), with units, sources and vintage in the footer
  3. Check accessibility (colors, fonts) and consistency
    • Color-blind-safe palettes; avoid dual axes and truncated axes that mislead
  4. Archive scripts and outputs together

Checkpoints with the user

  • After the chart list: confirm messages
  • After drafts: review readability

Common pitfalls

  • Too many series per chart
  • Forecast charts without uncertainty
  • Hand-edited charts that cannot be updated

Output

docs/briefs/<name>-charts/; a Word file with the charts and their captions on request (python tools/report.py docx <index.md> --out <file.docx>)

The folder holds the scripts, the data behind each chart and the rendered charts.

Gate / verdict

  • Charts regenerate from one command; uncertainty is visible
  • Every chart shows units, sources and vintage

Suggested next steps

  • /policy-brief

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.