القائمة
Must read guide on creating/editing mermaid charts with validation tools
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | mermaid |
| description | Must read guide on creating/editing mermaid charts with validation tools |
Use this skill to quickly validate Mermaid diagrams by parsing + rendering them with the official Mermaid CLI.
npx).PUPPETEER_EXECUTABLE_PATH../tools/validate.sh diagram.mmd [output.svg]
beautiful-mermaid (best-effort; not all diagram types are supported).output.svg is omitted, the SVG is rendered to a temp file and discarded.Mermaid has its own entity syntax using # (NOT &-prefixed HTML entities). Backslash escaping does NOT work.
| Character | Mermaid escape | Example |
|---|---|---|
# | #35; | Issue #35;42 → Issue #42 |
" | #quot; | #quot;hello#quot; → "hello" |
; | #59; | a #59; b → a ; b |
| Line break in node | #lt;br/#gt; | Node#lt;br/#gt;subtitle |
When to use escapes: Always use #quot; instead of raw " inside node labels and subgraph titles. Use #35; for literal hash/pound signs. This is especially critical when embedding in HTML <pre class="mermaid"> blocks, where raw " terminates the HTML attribute and # starts an entity.
Node labels with special chars: Use [#quot;label text#quot;] syntax:
A[#quot;PluginHost#lt;br/#gt;interface#quot;]
subgraph S[#quot;my subgraph (with parens)#quot;]
Edge labels: Simple text without special chars can be unquoted: A -->|receives| B. If the label contains special chars, use entity escapes.
diagram.mmd first (the tool only validates plain Mermaid files).diagram.mmd../tools/validate.sh diagram.mmd.Generate a standalone HTML report from a markdown file with d2 diagrams, SVGs, and syntax-highlighted code blocks. Use when the user asks for a report, a visual writeup, or a document with diagrams.
Interact with GitLab REST API using GITLAB_TOKEN - use for TODOs, repositories, CI/pipelines, MRs, issues, and other API queries
GitLab Development Kit is a folder and set of utilities that contain most of the GitLab production systems. This skill is useful for testing with local GitLab deployment and when researching how feature works in the GitLab monolith, AIGW, workhorse and other services
CRUD GitLab issues,MRs,pipelines,jobs,epics,issue comments
my projects — gitlab namespace and ID, where they live on the local drive. Use whenever a question references a project by name, alias, or path, or when you need to locate a repo locally. Keywords - project, repo, where does X live, local path, gitlab-lsp, glab, cli, vscode extension, note, task, duo cli, dotfiles.
code changes review, use this skill any time I ask you to review a change