What it does
drawthe.net draws network diagrams dynamically from a text file describing the placement, layout and icons. Given a yaml file describing the hierarchy of the network and it's connections, a resulting diagram will be created.
- Connects Instruction files the AI reads
- Account or key Not confirmed yet (README not read yet)
- Category Otros
Para autores: añade una insignia a tu README
Si lo creaste tú, pega este código en tu README. La insignia enlaza a esta página.
[](https://mcp.popnx.com/en/skills/cidrblock-drawthe-net)Skills parecidas
Mismo tipo de trabajo, ordenadas como la lista de Skills
| Este drawthe.net | llmfit | claude-video | VideoCaptioner | claude-cookbooks | |
|---|---|---|---|---|---|
| Autor | cidrblock | AlexsJones | bradautomates | WEIFENG2333 | anthropics |
| Skills | 1 | 1 | 1 | 1 | 4 |
| Estrellas de GitHub | 1184 | 39.036 | 21.085 | 16.557 | 54.799 |
| Último cambio de código | 13 nov 2026 | 16 nov 2026 | 25 sept 2026 | 12 sept 2026 | 5 nov 2026 |
| Licencia | MIT | MIT | MIT | GPL-3.0 | MIT |
1 skills (conjuntos de instrucciones) de cidrblock que la IA lee y sigue · no es un MCP server
En qué se diferencia un Skill de MCP
MCP = las manos
Conecta la IA a un servicio o dato externo, como leer Notion o crear una factura. Necesita un programa o servidor en marcha.
Skill = el manual
Un archivo de texto que enseña a la IA cómo hacer una tarea. No se conecta a nada.
A veces se parecen: algunas Skills ejecutan scripts que llaman herramientas y algunos MCP solo envían conocimiento. Empieza por la tarea que quieres hacer.
Funciona con
Codex
Según el README del autor y las carpetas del repo
Instalar
Is it safe?
- Who made it
GitHub account cidrblock (person), 10 years old
- Use and upkeep
★ 1184 stars · code last changed 13 nov 2026
- Any scripts?
75 scripts that can run on a computer: .eslintrc.cjs, bin/container-entrypoint.sh, bin/drawthe-net.js, mcp/dsl-reference.ts and 71 more
- Uses the internet?
Scripts that go online: src/renderer/icon-loader.ts
- Changes machine-wide settings?
No hooks or writes to machine settings found
Checked automatically from the repo files at commit 8aeeacc (read only, nothing was run). Not a safety guarantee: read it and decide for yourself
Primero: ¿qué IA usas?
Elige tu app y esta página mostrará solo cómo instalarlo en ella
Option 1Upload to claude.ai (web and app)
Uploading to claude.ai would fail: the description is over 200 characters (389). Use "Let the AI install it" instead
Option 1Deja que Claude Code lo instale
Copia esta frase y pégala en un chat de Claude Code
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Vuelve a abrir Claude Code y escribe /drawthe.net, o pide una tarea relacionada y Claude lo usará
Checked against official docs 12 nov 2026 · Source: code.claude.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.claude/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/cidrblock/drawthe.net.git /tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc && mkdir -p ~/.claude/skills && cp -R '/tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc/.' ~/.claude/skills/drawthe.netVuelve a abrir Claude Code y escribe /drawthe.net, o pide una tarea relacionada y Claude lo usará
App de escritorio de ChatGPT
La app de escritorio de ChatGPT incluye Codex, y Codex lee las skills de la carpeta ~/.agents/skills
Option 1Deja que ChatGPT lo instale
Abre Codex en la app de escritorio de ChatGPT y pega esta frase en el chat
The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Option 2Coloca la carpeta tú mismo
Coloca la carpeta drawthe-net en ~/.agents/skills/drawthe-net
~ es tu carpeta de inicio ($HOME)
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/cidrblock/drawthe.net.git /tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc/.' ~/.agents/skills/drawthe.net
Después de instalar
- App de escritorio de ChatGPT: abre Skills en la barra lateral para ver que la skill está
- Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
- Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
ChatGPT en la web y el móvil
Las skills que instalas tú no funcionan aquí; solo las que vienen con un plugin del directorio
Para usar esta skill con ChatGPT, usa la app de escritorio de ChatGPT como se indica arriba
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
Option 1Deja que Codex lo instale
Copia esta frase y pégala en un chat de Codex · Sirve en Codex dentro de la app de escritorio de ChatGPT, en Codex CLI y en la extensión del IDE
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Codex detecta solo las skills recién instaladas; si una no aparece, reinicia Codex · Para usarla: en ChatGPT escribe @ y elige la skill · en Codex CLI o la extensión del IDE ejecuta /skills o escribe $ y el nombre de la skill
Checked against official docs 15 nov 2026 · Source: learn.chatgpt.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.agents/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/cidrblock/drawthe.net.git /tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc && mkdir -p ~/.agents/skills && cp -R '/tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc/.' ~/.agents/skills/drawthe.netVuelve a abrir Codex y pide una tarea relacionada; Codex mostrará el skill
Option 1Deja que Cursor lo instale
Copia esta frase y pégala en un chat de Cursor
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
En el chat Agent de Cursor escribe / y elige drawthe.net
Checked against official docs 12 nov 2026 · Source: cursor.com
For Terminal users
Un Skill son instrucciones que la IA seguirá. Lee los archivos antes de instalar e instala solo de autores de confianza.
Abre la Terminal
Mac: pulsa Command+Espacio y escribe Terminal · Windows: el comando no funciona en PowerShell; usa «Que la IA lo instale» arriba
Copia la carpeta del skill a ~/.cursor/skills
Descarga el repo a una carpeta temporal y copia solo las carpetas con SKILL.md
git clone --depth 1 https://github.com/cidrblock/drawthe.net.git /tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc && mkdir -p ~/.cursor/skills && cp -R '/tmp/popnx-skill-cidrblock-drawthe-net-8aeeacc/.' ~/.cursor/skills/drawthe.netEn el chat Agent de Cursor escribe / y elige drawthe.net
Option 1Let the AI install it
Para otras apps que leen skills. La frase incluye las rutas de Claude Code, Codex y Cursor para que la IA elija la de tu app · Copy this sentence into the app’s chat
For one project, paste it into a chat that is open in that project’s folder · The AI always shows you the path before installing
The AI tells you what it will do first and asks your permission at every step
Checked against official docs 12 nov 2026 · Source: code.claude.com, learn.chatgpt.com, cursor.com
For Terminal users
Otras apps con Agent Skills (como Gemini CLI o GitHub Copilot) usan otras carpetas. Mira la guía de esa app y copia allí la carpeta con el SKILL.md.
Carpetas de skills comprobadas con las guías oficiales de Claude Code, Codex y Cursor el 11 nov 2026
✓ Comandos revisados el 18 nov 2026
Ver el SKILL.md original
El texto siguiente viene del repo del autor, no de PopNx MCP
Se muestran los primeros 8000 caracteres · Abrir el archivo completo en GitHub
---
name: drawthe.net
description: Draw network/architecture diagrams (AWS, Azure, Cisco) from a natural-language description or from a proposed system architecture, using the drawthe.net MCP server's YAML DSL and icon tools. Use this skill whenever the user asks to "draw a diagram", "create an architecture diagram", "visualize this infrastructure", "sketch the network", or asks you to propose/illustrate a system design.
---
# drawthe.net diagram authoring skill
This skill teaches an agent how to turn a description (or a proposed
architecture) into a drawthe.net YAML diagram and render it via the
drawthe.net MCP server's tools. The result should be a build blueprint:
someone reading it should understand what to provision, how traffic and
data move, what is required versus optional, and what to configure next.
### ARCHITECTURE DIAGRAM DESIGN SYSTEM & AESTHETIC DIRECTIVES
When authoring system architecture diagrams in YAML, adhere strictly to these architectural visual design principles:
#### 1. Architectural Layout & Directional Flow
* **Determine the Primary Axis:**
* **Top-to-Bottom (Layered Systems):** Use for Tiered/Client-Server architectures (Presentation → Processing/Logic → Storage → External Infrastructure).
* **Left-to-Right (Data & Workflow Pipelines):** Use for event-driven systems, ETL pipelines, integration flows, or user journey sequences.
* **Dedicated Cross-Cutting Rows/Columns:** Place auxiliary or cross-cutting services (e.g., Logging, Authentication, Telemetry, Storage) on a dedicated side column or bottom row rather than interspersing them within the core flow.
* **Spatial Breathability:** Always leave 1–2 empty grid steps between connected components to provide space for connection lines without crossing icons or text.
#### 2. Restrained Color System & Contrast
* **Canvas:** Use the established white canvas (`white`) unless the user requests another treatment.
* **Default Elements:** Use dark readable text and lines (`black` for labels and `#334155` for connections/borders). Do not use the historical orange renderer defaults for blueprint styling.
* **Containers:** Use light-gray or very lightly tinted fills with a consistent border, such as `#F1F5F9` with `#94A3B8`. Container color should establish hierarchy without competing with the topology.
* **Icons:** Preserve native vendor icon artwork. Do not impose a diagram-wide accent palette or override icon fills/strokes unless the selected icon has been previewed and the override is intentional.
#### 3. Domain Grouping & Boundaries
* **Container Enclosure:** Wrap related components in named groups (e.g., Services, Data Domain, External System, Core Boundary).
* **Line Style Rules:**
* **Solid Lines:** Direct synchronous calls, primary system processes, or hard structural boundaries.
* **Dashed Lines (`strokeDashArray: [4, 4]`):** Asynchronous events, metadata/telemetry flows, or logical/trust boundaries.
* **Group Headers:** Choose one placement for all group names, commonly `bottomMiddle` for north-to-south flows, and keep it consistent unless a collision is unavoidable.
#### 4. Typography & Label Symmetry
* **Unified Alignment:** Standardize `textLocation` across the entire diagram. Use the selected group/icon placement consistently; the established blueprint default is `bottomMiddle`. Never mix alignments within the same diagram unless a documented collision makes it unavoidable.
* **Readable Display Names:** Always use explicit, concise display text with the `text:` attribute (e.g., `text: "Auth Service"`) instead of raw technical identifiers (e.g., `auth_svc_node_01`).
#### 5. Connection Line Discipline
* Align connected components along straight grid lines to eliminate diagonal line clutter.
* Group multi-destination fan-outs neatly through shared alignment rather than overlapping multiple connection lines across the canvas.
## Prerequisites
The drawthe.net MCP server must be connected and expose these tools:
- `get_dsl_reference` — returns the full YAML DSL syntax reference.
- `list_icon_families` — lists available icon families and icon counts.
- `list_icons` — lists/searches icon names within a family.
- `get_icon` / `get_icon_svg` — preview a specific icon (PNG/SVG) to confirm it looks right before using it.
- `render_diagram` — renders a YAML diagram to PNG or SVG.
## Procedure
1. **Read the DSL reference first.** Call `get_dsl_reference` before
writing any YAML if you have not already seen it in this conversation.
Do not guess at the syntax — the `diagram`, `title`, `icons`, `notes`,
`groups`, and `connections` sections each have specific required and
optional fields.
2. **Identify the components in the description.** Break the request down
into concrete entities (servers, load balancers, databases, gateways,
VPCs/VNets, users, external services, etc.) and the connections between
them. If the user proposes an architecture rather than describing an
existing one, design a sensible one first (reasonable tiers, redundancy,
networking boundaries), then diagram it.
State the architecture assumption in the title or a note when the
request is ambiguous. For example, RHDH on ROSA is materially different
from RHDH on EKS or RHDH on EC2.
Design the blueprint before choosing icons. Organize it into these layers
where they apply:
- prerequisites and network foundation: account, region, VPC, AZs,
public/private subnets, routing, security groups, IAM, and certificates;
- request path: users, DNS, edge/load balancer, ingress, and application;
- platform: cluster, namespaces, operators, ingress controller, and
workload replicas;
- dependencies: identity, database, secrets, object storage, registries,
source control, and observability;
- build notes: required configuration, optional choices, and an ordered
implementation sequence.
Do not draw every plausible service. Include a component only when it
answers a deployment question, and mark it as required, optional, or
external in its label or notes.
3. **Choose the right icon family based on vendor keywords in the
request** — there is no fixed default family. Inspect the request for
vendor/platform signals:
- AWS services/terms → `aws2026` (preferred, current) or `aws` (legacy).
- Azure services/terms → `azure2026` (preferred), or `azureCloud` /
`azureEnterprise` (legacy).
- Cisco/network hardware terms → `cisco2026` (preferred) or `cisco` (legacy).
- Generic/vendor-neutral request → pick whichever family has the closest
conceptually matching icon; prefer the modern `*2026` families.
Call `list_icon_families` if you're unsure what's available.
4. **Never invent an icon name.** For every component, call `list_icons`
with the family and a keyword query (e.g. `query: "load_balanc"`) to find
the real icon name before writing an `icon:` reference in YAML. Use
`get_icon` or `get_icon_svg` to visually confirm an ambiguous match
before committing to it.
5. **Always prefer a meaningful, accurate icon over a generic
placeholder.** If an exact icon for a component doesn't exist in the
chosen family, search for the closest conceptually similar icon (e.g. a
generic "server" or "compute" icon for an unlisted service type) rather
than defaulting to a plain box or an unrelated icon. Only fall back to a
generic shape (e.g. via `notes`) if truly no reasonable icon exists in
any relevant family.
6. **Write the YAML diagram** using the DSL: define `diagram` (grid size,
background), optionally `title`, then `icons` (with `x`/`y` grid
coordinates, using relative positions like `x: "+1"` where convenient),
`groups` to box related components together, and `connections` between
icon keys. Use YAML anchors for repeated styling if helpful.
Start from the light, readable style below unless the user explicitly
requests a different visual treatment:
Conversación
Pregunta, comparte un consejo o avisa de que no funciona. Ordenado por lo que la gente marcó como útil.
Aún no hay publicaciones. Sé la primera persona en preguntar o compartir.
Lo publicado aquí lo escriben usuarios, no el equipo de PopNx.
Desde GitHub
- Estrellas en GitHub
- 1184
- Autor
- cidrblock
- Licencia
- MIT
- Último cambio de código
- 13 nov 2026
- Archivos SKILL.md del repo (con traducciones y plantillas)
- 2
- Temas
- diagram, icons, network