agentleFS
Sign inStart free
lulufoolulufoo/lulu-drawer/skills/mermaid/SKILL.md

mermaid

Skill8 starsChanged 10 days agoMITView on GitHub

List Mermaid types, or draw an open catalog type and open it on the public viewer.

45 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ansible, plantuml and 6 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.
  • julweberSkill

    ansible

    Ansible automation reference for playbooks, roles, inventory, variables, and modules. Includes Proxmox VE and Docker integration via community.general and community.docker collections. Use when writing playbooks, troubleshooting Ansible runs, or designing automation workflows. Triggers: ansible, playbook, inventory, role, task, handler, vars, jinja2, galaxy, proxmox_kvm, proxmox_lxc, docker_container, docker_compose.

    Also in 3 projects that use this

  • xenodiumSkill

    plantuml

    This skill should be used when the user invokes "/plantuml" to create a diagram from the current context using PlantUML and output the resulting image path.

    Also in 3 projects that use this

  • ihiteshguptaSkill

    terraform

    Expert in Infrastructure as Code with Terraform. Use for creating, managing, and versioning infrastructure across cloud providers.

    Also in 3 projects that use this

  • PostHogSkill

    karpathy-guidelines

    Behavioral guidelines to reduce common LLM coding mistakes. Use when writing, reviewing, or refactoring code to avoid overcomplication, make surgical changes, surface assumptions, and define verifiable success criteria. Based on https://github.com/multica-ai/andrej-karpathy-skills.

    Also in 3 projects that use this

  • AWSSkill

    ship

    Finalize dev work on an issue branch — update docs, push, and open a PR.

    Also in 4 projects that use this

  • SentrySkill

    commit

    Create commit messages following Sentry conventions. Use when committing code changes, writing commit messages, or formatting git history. Follows conventional commits with Sentry-specific issue references.

    Also in 4 projects that use this

The file

We split this skill into the rules it gives an agent

7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.

  • 0

    Common

    Most of the 41 edited versions we read keep these.

  • 3

    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:

    Use one sample in that file (minimal default).

    line 58
  2. Distinctive:

    Prefer ≤ ~12 primary elements unless the user asked for more.

    line 62
  3. Very specific:

    Use cloud mode only when one of these holds: the user asks to save, keep, or update a cloud diagram, or to search cloud diagrams.

    line 69
  4. Very specific:

    If login fails or times out, use short-link mode and tell the user why.

    line 71
  5. Distinctive:

    If the user pastes a viewer URL, load pointers.

    line 72
  6. Very specific:

    No scene to draw (and not an update): show https://luluboard.app/ and stop.

    line 78
  7. Very specific:

    Write the Source to .cache/mermaid/<name>.mmd.

    line 79

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

mermaid

List the catalog, or author an open catalog type and open it on the public viewer. Done when the list is shown, or a tool url is shown.

Syntax

Author Mermaid 12.1.0 built-in syntax. Drawer renders flowchart with Pele 1.7.0 and mindmap with a custom SVG pipeline, not Mermaid.js.

CLI

The shared CLI reference defines $BOARD_CLI.

  1. Load cli before the first $BOARD_CLI call of a session.

References

Load only what the current interface needs.

  1. list — load catalog only.
  2. route — after an open type is chosen, load that one file from catalog.

Interfaces

Two entries. Do not author during list.

  1. list — slash list, or the ask is which types exist. Load catalog. Show the class table, including Open. Stop.
  2. route — any draw ask. Pick exactly one catalog type. If it is not open, say it is not open, then stop. If it is open, load only that file. Author. Preview.

Route

The catalog is the type boundary. Open is flowchart (flowchart / graph), mindmap, and the Design group (sequence, class, state, er, requirement, c4, usecase, eventmodeling, railroad). flowchart-elk is the flowchart type.

  1. A named type or alias wins.
  2. Else pick the type that matches what must be visible.
  3. Two fit → pick one; do not stop to ask.
  4. None fit → ask one line, then stop.
  5. A closed type → say it is not open, then stop. Do not author.
  6. Source already in hand and the ask is to publish it → skip Author; run the Short link flow.

Author

What to write, after the open type file is loaded.

  1. Use one sample in that file (minimal default). Flowchart: one edge-meaning category. Mindmap: one root, indented branches. Design: Pele preview; Title and Source.
  2. Replace labels; keep the sample's node and edge kinds.
  3. Prefer ≤ ~12 primary elements unless the user asked for more.
  4. Mint without %% style. On update, leave those lines unchanged.

Mode

Pick short link or cloud. Short link is the default.

  1. Use cloud mode only when one of these holds: the user asks to save, keep, or update a cloud diagram, or to search cloud diagrams; the user pastes a #b: link; this session already created the diagram in cloud mode. Load cloud.
  2. Otherwise use short-link mode.
  3. If login fails or times out, use short-link mode and tell the user why.
  4. If the user pastes a viewer URL, load pointers.

Short link flow

Publish unsigned.

  1. No scene to draw (and not an update): show https://luluboard.app/ and stop.
  2. Write the Source to .cache/mermaid/<name>.mmd. <name> is a short English name for the diagram.
  3. Run $BOARD_CLI preview-diagram --file <file>.
  4. Show only the url field and stop.
  5. To change, edit the file and publish again. That creates a new short url.
  6. To keep, use cloud mode (#b:).

Open wording

Show the url. One line.

Boundaries

  1. CLI contract: $BOARD_CLI --help.
  2. CLI success completes the skill; do not open the URL, drive the viewer, or screenshot the layout unless the user explicitly requests visual verification.

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