agentleFS
seayniclabsseayniclabs/homelab-infra-mcp/skills/diagram/SKILL.md

diagram

Skill0 starsChanged 21 days agoMITView on GitHub

Create an editable draw.io (.drawio) diagram file from a description of a system, flow, sequence or architecture. Use when the user wants a diagram they can open and edit in draw.io or diagrams.net. For an animated diagram, use dashmotion; for a map of a homelab network, use network-diagram.

53 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use ios-sync, benchmark-models 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.
  • Saqlain-811Skill

    ios-sync

    Regenerate the iOS debug bridge against the latest upstream gstack templates. (gstack)

    Also in 4 projects that use this

  • ShreyRaviSkill

    benchmark-models

    Cross-model benchmark for gstack skills. Runs the same prompt through Claude, GPT (via Codex CLI), and Gemini side-by-side — compares latency, tokens, cost, and optionally quality via LLM judge. Answers "which model is actually best for this skill?" with data instead of vibes. Separate from /benchmark, which measures web page performance. Use when: "benchmark models", "compare models", "which model is best for X", "cross-model comparison", "model shootout". (gstack) Voice triggers (speech-to-text aliases): "compare models", "model shootout", "which model is best".

    Also in 5 projects that use this

  • ShreyRaviSkill

    landing-report

    Read-only queue dashboard for workspace-aware ship. Shows which VERSION slots are currently claimed by open PRs, which sibling Conductor workspaces have WIP work likely to ship soon, and what slot /ship would pick next. No mutations — just a snapshot. Use when asked to "landing report", "what's in the queue", "show me open PRs", or "which version do I claim next". (gstack)

    Also in 5 projects that use this

  • timurgaleevSkill

    document-generate

    Generate missing docs for a feature, module or project as tutorials, how-tos, reference and explanation.

    Also in 4 projects that use this

  • Saqlain-811Skill

    ios-clean

    Remove the DebugBridge SPM package and all #if DEBUG wiring from an iOS app. (gstack)

    Also in 3 projects that use this

  • seek888Skill

    open-gstack-browser

    Launch GStack Browser — AI-controlled Chromium with the sidebar extension baked in. Opens a visible browser window where you can watch every action in real time. The sidebar shows a live activity feed and chat. Anti-bot stealth built in. Use when asked to "open gstack browser", "launch browser", "connect chrome", "open chrome", "real browser", "launch chrome", "side panel", or "control my browser". Voice triggers (speech-to-text aliases): "show me the browser".

    Also in 4 projects that use this

  • +2 more from ShreyRavi
  • +1 more from Saqlain-811

The file

We split this skill into the rules it gives an agent

11 rules. 0 are common, 8 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 44 edited versions we read keep these.

  • 8

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Get the description: Use the text the user gave.

    line 15
  2. Distinctive:

    Every file starts with this skeleton.

    line 23
  3. Very specific:

    When html=1 is in the style, write labels with entities: value="<b>Title</b><br>Detail".

    line 72
  4. Distinctive:

    Use orthogonal edges for architecture and network diagrams.

    line 106
  5. Distinctive:

    Use one palette per diagram.

    line 110
  6. Distinctive:

    Keep at least 40 px between shapes.

    line 124
  7. Distinctive:

    Prefer swimlanes when the diagram shows who owns each step.

    line 129
  8. Distinctive:

    Every cell ID is unique.

    line 138
  9. Very specific:

    Every vertex has vertex="1" and an mxGeometry.

    line 140
  10. Very specific:

    Every edge has edge="1", a source and a target that match vertex IDs.

    line 141
  11. Distinctive:

    No two shapes overlap.

    line 142

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

Create a draw.io diagram

This skill writes a .drawio file. The file is plain XML that draw.io, diagrams.net and the VS Code draw.io extension open and edit.

Steps

  1. Get the description. Use the text the user gave. If they gave none, ask what the diagram shows and what type it is: flowchart, network, architecture, swimlane, sequence, entity relationship, org chart or free-form.
  2. Plan the layout. List every shape, connection, label and group before you write XML. Count the shapes. Above 15 shapes, split the diagram into pages.
  3. Write the XML using the structure and style rules below.
  4. Name and save the file. Slugify the title: lowercase, hyphens for spaces, no symbols. "Network Topology" becomes network-topology.drawio. Save it in the current working directory. If the file exists, ask before overwriting.
  5. Report the path as a Markdown link. Do not open the file.

File structure

Every file starts with this skeleton. Each page has its own cell IDs.

<mxfile host="Homelab" modified="2026-10-27T00:00:00.000Z" agent="AI assistant" version="1.0" type="device">
  <diagram id="page1" name="Overview">
    <mxGraphModel dx="1200" dy="800" grid="1" gridSize="10" guides="1" tooltips="1" connect="1" arrows="1" fold="1" page="1" pageScale="1" pageWidth="1100" pageHeight="850" background="#ffffff" math="0" shadow="0">
      <root>
        <mxCell id="0"/>
        <mxCell id="1" parent="0"/>
        <!-- shapes and edges go here, all with parent="1" or a container id -->
      </root>
    </mxGraphModel>
  </diagram>
</mxfile>

Cell 0 is the invisible root. Cell 1 is the default layer. Both are required.

Shape

<mxCell id="server_web1" value="Web server" style="rounded=1;whiteSpace=wrap;html=1;arcSize=10;fillColor=#dae8fc;strokeColor=#6c8ebf;" vertex="1" parent="1">
  <mxGeometry x="120" y="80" width="120" height="60" as="geometry"/>
</mxCell>

Edge

<mxCell id="edge_web_to_db" value="SQL" style="edgeStyle=orthogonalEdgeStyle;rounded=0;html=1;endArrow=classic;labelBackgroundColor=#ffffff;" edge="1" parent="1" source="server_web1" target="db1">
  <mxGeometry relative="1" as="geometry"/>
</mxCell>

Group and container

Children use the container's ID as their parent. Child coordinates are relative to the container's top-left corner.

<mxCell id="zone_dmz" value="DMZ" style="swimlane;whiteSpace=wrap;html=1;startSize=30;fillColor=#f5f5f5;strokeColor=#666666;" vertex="1" parent="1">
  <mxGeometry x="100" y="60" width="320" height="200" as="geometry"/>
</mxCell>
<mxCell id="proxy" value="Reverse proxy" style="whiteSpace=wrap;html=1;" vertex="1" parent="zone_dmz">
  <mxGeometry x="20" y="50" width="120" height="60" as="geometry"/>
</mxCell>

Escape HTML

When html=1 is in the style, write labels with entities: value="&lt;b&gt;Title&lt;/b&gt;&lt;br&gt;Detail".

Shape styles

UseStyle
ProcesswhiteSpace=wrap;html=1;
Rounded boxrounded=1;whiteSpace=wrap;html=1;arcSize=10;
Terminator (start, end)rounded=1;whiteSpace=wrap;html=1;arcSize=50;
Decisionshape=rhombus;whiteSpace=wrap;html=1;
Data (input, output)shape=parallelogram;perimeter=parallelogramPerimeter;whiteSpace=wrap;html=1;
Databaseshape=cylinder3;whiteSpace=wrap;html=1;boundedLbl=1;stencilColors=1;size=15;
Cloud or internetshape=cloud;whiteSpace=wrap;html=1;
Documentshape=document;whiteSpace=wrap;html=1;
Noteshape=note;whiteSpace=wrap;html=1;backgroundOutline=1;
Person (actor)shape=mxgraph.basic.person;whiteSpace=wrap;html=1;
Swimlaneswimlane;whiteSpace=wrap;html=1;startSize=30;
Servershape=mxgraph.cisco.servers.standard_server;whiteSpace=wrap;html=1;
Routershape=mxgraph.cisco.routers.router;whiteSpace=wrap;html=1;
Firewallshape=mxgraph.cisco.firewalls.firewall;whiteSpace=wrap;html=1;

Edge styles

UseStyle
Straight arrowendArrow=classic;html=1;
Orthogonal (architecture, network)edgeStyle=orthogonalEdgeStyle;rounded=0;html=1;endArrow=classic;
Curvedcurved=1;html=1;endArrow=classic;
Dashed (optional or async)dashed=1;html=1;endArrow=classic;
Two-wayendArrow=classic;startArrow=classic;html=1;
No arrowendArrow=none;html=1;

Arrow names: classic, block, open, oval, diamond, dash, cross, none, ERone, ERmany.

Use orthogonal edges for architecture and network diagrams. Use straight or curved edges for simple flowcharts.

Palette

Use one palette per diagram. Use no more than four or five colors.

RoleFillStroke
Primary#dae8fc#6c8ebf
Success#d5e8d4#82b366
Warning#fff2cc#d6b656
Danger#f8cecc#b85450
Neutral#f5f5f5#666666
Accent#e1d5e7#9673a6

Layout

  • Snap every coordinate to a multiple of 10.
  • Keep at least 40 px between shapes. Use 80 to 120 px between columns and rows.
  • Typical sizes: box 120 by 60, decision 80 by 80, database 60 by 80, cloud 120 by 80.
  • Pick one flow direction, top to bottom or left to right, and keep it for the whole diagram.
  • Align shapes on their centers.
  • Give every cell a descriptive ID such as server_web1 or edge_web_to_db. Never use bare numbers.
  • Prefer swimlanes when the diagram shows who owns each step.
  • Split a diagram above 15 shapes into pages, with an overview page first.

Connection points

To control where an edge attaches, set exitX, exitY, entryX and entryY in the edge style. Top center is 0.5 and 0. Bottom center is 0.5 and 1. Left center is 0 and 0.5. Right center is 1 and 0.5.

Quality check before you save

  • Every cell ID is unique.
  • Cells 0 and 1 are present.
  • Every vertex has vertex="1" and an mxGeometry.
  • Every edge has edge="1", a source and a target that match vertex IDs.
  • No two shapes overlap.
  • Labels are short. Escaped HTML is valid.
  • The XML is well formed: every tag closes, every attribute is quoted, every &, < and > in labels is escaped.

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.