agentleFS
Sign inStart free
limyuquanlimyuquan/planner/skills/visualise/SKILL.md

visualise

Skill1 starsChanged 37 days agoMITView on GitHub

Produce a self-contained HTML page in the house style — implementation plans, post-implementation recaps, codebase explorations, concept explainers, standalone ELI5 picture pages, and diff/audit reviews. Use when the user types /visualise or /eli5, asks for a plan/recap/explainer/diagram page, or another skill calls for plan.html, eli5.html, or recap.html.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. bentossell/visualise★ 478same name
    2. atomicinnovation/accelerator★ 34same name
    3. SHYXIN/skills★ 6same name
    4. sidp-2003/Claude_Skills★ 0same name

    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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 0

    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:

    Do not read render/GUIDE.md or the files beside it yourself.

    line 19

“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

visualise

The main thread never writes the HTML. It briefs one render subagent and links the result.

  1. Pick the mode: plan (before implementation), recap (after), explore (codebase map), explain (one concept), eli5 (standalone picture page), diff-review (selectable findings).
  2. Resolve the output path. In a Planner docs folder: plan.html, eli5.html, recap.html in the phase folder; whole-task pages in the task's plans/ folder; anything else where the user says. Existing files are updated in place.
  3. Spawn one subagent (a capable model; the page is long and the guide is detailed). Its prompt contains, in this order:
    • "Read render/GUIDE.md in the visualise skill folder first and follow it." (give the absolute path)
    • the mode, the title, the exact output path
    • the sources: plan paths, diff range or commands, files to read, and any decisions or context from the conversation the sources do not contain
    • "Return the output path, the title, and anything you could not verify."
  4. Show it with the link-plan skill (a dashboard link, not a file path), and relay the subagent's unverified items in one line.

Do not read render/GUIDE.md or the files beside it yourself; they are written for the subagent and are long on purpose. If your agent cannot spawn subagents, read the guide and write the page yourself.

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