agentleFS
Sign inStart free
liormeshliormesh/trestle/skills/visualize/SKILL.md

visualize

Skill2 starsChanged 11 days agoMITView on GitHub

Turn a plan, report, dataset, or explanation into a self-contained visual artifact - a single offline HTML file (default) or a PDF. Use on demand when a wall of markdown is hard to read, when a plan or spec needs reviewing before approval, when data needs a chart or dashboard, or when the deliverable must be a PDF. Triggers on 'visualize', 'visualise', 'render this as HTML', 'make an HTML page', 'make a report page', 'turn this into a page', 'make a visual', 'chart this', 'dashboard for', 'PDF of this', 'export to PDF', 'make this readable'. Do NOT trigger for: editing an existing slide deck or document, generating photos or marketing imagery, or plain prose the user wants to keep as text.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use exp-pilot-eval, exp-pilot-run and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • skyllwtSkill

    exp-pilot-eval

    Pilot result evaluation — read pilot results, apply success criteria, update idea page (pilot_result, failure_reason if failed), generate PILOT_VERDICT_REPORT. Called by /ideate Phase 5 after /exp-pilot-run.

    Also in 4 projects that use this

  • skyllwtSkill

    exp-pilot-run

    Pilot experiment execution — read Pilot Spec YAML, write pilot code, run experiment(Confirm with the user before operation and require the applicant to conduct manual inspection), return results. Called by /ideate Phase 5. Does NOT modify wiki pages or judge pass/fail.

    Also in 4 projects that use this

  • LambenthanSkill

    daily-arxiv

    每日从 arXiv 拉取新论文，过滤相关性，auto-ingest 高优先级论文，检测 SOTA 更新

    Also in 4 projects that use this

  • LambenthanSkill

    exp-eval

    实验判决门：Review LLM 独立评判实验结果 → 4 种判决路径 → 自动更新 claims confidence、ideas status、graph edges

    Also in 4 projects that use this

  • phanghonghaoSkill

    poster

    HTML/CSS A4 海报生成。从沙龙/活动 Markdown 文件生成科技风 A4 海报 PDF/PNG。Use when user mentions: poster, 海报, 海报生成, make poster, generate poster, 活动海报, 沙龙海报.

    Also in 4 projects that use this

  • +1 more from skyllwt
  • +6 more from Lambenthan
  • Other versions45 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 45

    1. moltbot/clawdbot★ 394ksame name
    2. steipete/warelay★ 394ksame name
    3. steipete/clawdis★ 394ksame name
    4. moltbot/moltbot★ 394ksame name
    5. clawdbot/clawdbot★ 394ksame name
    6. openclaw/openclaw★ 394ksame name
    7. molt-bot/clawdbot★ 391ksame name
    8. amosblomqvist/learn★ 3.4ksame name
    9. skyllwt/OmegaWiki★ 1.7ksame name
    10. DAIR-AutoResearch/AutoSci★ 1.7ksame name

    35 more not listed

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository3 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 43 edited versions we read keep these.

  • 5

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read the visualization book's table of contents, then pull only the chapters this request needs:

    line 12
  2. Very specific:

    Always load ch02-self-contained-html.md - the core craft.

    line 14
  3. Very specific:

    Check ch05-gotchas.md before shipping.

    line 18
  4. Distinctive:

    Read the book and apply it - don't reproduce it here.

    line 20
  5. Very specific:

    Save it somewhere sensible and open it: Default: a visualizations/ folder in the current project (create it), or the path the user names.

    line 26
  6. Distinctive:

    Iterate: if the user marks up or asks for changes, keep editing the same file.

    line 28
  7. Very specific:

    If you hit a rendering gotcha worth remembering (a layout that broke, a print-CSS quirk, a data-URI size limit), append it to …

    line 33
  8. Distinctive:

    One file, fully offline: No CDN links, no external fonts, no fetch/XHR.

    line 37
  9. Distinctive:

    On demand only: Don't turn every plan into HTML by reflex - build when asked.

    line 38

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

/visualize - build a visual artifact (HTML or PDF)

Produce ONE self-contained file the user can open by double-clicking - no server, no internet, no build step. HTML by default; PDF when the deliverable has to be a PDF. This is an on-demand skill: run it when asked, don't auto-convert things the user didn't ask to see visually.

First action - load context

Read the visualization book's table of contents, then pull only the chapters this request needs:

  • Book: books/dataviz/_toc.md in the knowledge base (the canonical, writable copy). If it isn't there, fall back to book/dataviz/_toc.md beside this skill (the copy shipped with the installer).
  • Always load ch02-self-contained-html.md - the core craft; every artifact is one self-contained file.
  • Load ch03-charts-and-data.md if the request involves numbers, metrics, or charts.
  • Load ch04-pdf-output.md if the output must be a PDF.
  • Skim ch01-when-and-format.md if it's unclear whether to build at all, or which format fits.
  • Check ch05-gotchas.md before shipping.

Read the book and apply it - don't reproduce it here.

Flow

  1. Decide what, and whether. Per ch01: is a visual actually the right call, or is markdown fine? If yes, pick the artifact type - plan/spec, report, data dashboard, or explainer - and the format (HTML unless the user asked for PDF).
  2. Build one self-contained file per ch02: inline all CSS and JS, embed images/fonts as data: URIs, no external requests, responsive, readable in both light and dark, print-friendly. For data, apply ch03 (right chart, accessible color, labels/legend, tables that scroll).
  3. Save it somewhere sensible and open it. Default: a visualizations/ folder in the current project (create it), or the path the user names. Use a clear filename ({topic}-{kind}.html). Then open it so the user sees it right away.
  4. PDF, if asked: build the HTML first (steps 2-3), then produce the PDF per ch04. Default is print-to-PDF from the browser (zero dependency); use an automated tool only if one is already installed, and say which.
  5. Iterate: if the user marks up or asks for changes, keep editing the same file.

After the task

  • Append a one-line entry to _analytics/usage.log (per the analytics rule).
  • If you hit a rendering gotcha worth remembering (a layout that broke, a print-CSS quirk, a data-URI size limit), append it to books/dataviz/ch05-gotchas.md. That write-back is how the book compounds instead of rotting.

Constraints

  • One file, fully offline. No CDN links, no external fonts, no fetch/XHR. If it needs the internet to render, it's wrong.
  • On demand only. Don't turn every plan into HTML by reflex - build when asked.
  • It's a local file, not a hosted link. The user opens it from disk; where it goes after is their call.

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