[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MADRPTWKK7HW33PVS8BF37":3,"skill-same:01M6MADRPTWKK7HW33PVS8BF37":245},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":37,"publishedAt":58,"linkOnly":59,"markdownContent":60,"markdownBody":61,"frontMatter":62,"refName":73,"commitSha":74,"skillDirectory":75,"forksCount":76,"repositoryHtmlUrl":77,"repositoryHomepageUrl":78,"ownerHtmlUrl":79,"ownerBlogUrl":80,"ownerDescription":81,"updatedAt":82,"install":83,"resources":96},"01M6MADRPTWKK7HW33PVS8BF37","markdown-mermaid-writing",null,"Writes scientific documents and documentation as markdown with embedded Mermaid diagrams as the canonical, git-diffable source format. Covers a markdown style guide, a Mermaid style guide, 24 Mermaid diagram type references (flowchart, sequence, ER, Gantt, state, mindmap, radar, sankey, XY chart, and others), and 9 templates (research paper, status report, decision record, how-to, pull request, issue, kanban, presentation, project documentation). Use when writing a report, manuscript, README, or analysis in markdown. Use when adding a workflow, pipeline, timeline, or architecture diagram to a document. Use when choosing the right Mermaid diagram type or fixing Mermaid syntax such as radar-beta or xychart-beta. Use when starting from a document template or checking citations and heading rules. Not for scatter plots of real data or photorealistic images; use Python plotting or scientific-schematics for those.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002FSKILL.md",[18,23,26,29,34],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000033","数据分析师","PROFESSION","适用职业",{"categoryNo":35,"categoryName":36,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者",[38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54,55,56,57],"mermaid","markdown","markdown mermaid writing","writing","read","presentation","scientific","status report","chart","project","issue","guide","edit","write","how","git","architecture diagram","documents","status","architecture","2026-11-10 10:12:30",false,"---\nname: markdown-mermaid-writing\ndescription: Writes scientific documents and documentation as markdown with embedded Mermaid diagrams as the canonical, git-diffable source format. Covers a markdown style guide, a Mermaid style guide, 24 Mermaid diagram type references (flowchart, sequence, ER, Gantt, state, mindmap, radar, sankey, XY chart, and others), and 9 templates (research paper, status report, decision record, how-to, pull request, issue, kanban, presentation, project documentation). Use when writing a report, manuscript, README, or analysis in markdown. Use when adding a workflow, pipeline, timeline, or architecture diagram to a document. Use when choosing the right Mermaid diagram type or fixing Mermaid syntax such as radar-beta or xychart-beta. Use when starting from a document template or checking citations and heading rules. Not for scatter plots of real data or photorealistic images; use Python plotting or scientific-schematics for those.\nlicense: Apache-2.0\nallowed-tools: Read Write Edit Bash\nmetadata:\n  version: '1.1'\n  category: research-writing\n  maintainer: Kalaris Labs\n  skill-source: https:\u002F\u002Fgithub.com\u002FSuperiorByteWorks-LLC\u002Fagent-project\n  skill-version: 1.0.0\n  skill-contributors: Clayton Young (Superior Byte Works, LLC \u002F @borealBytes; Author and originator)\n  contributor: Clayton Young \u002F Superior Byte Works, LLC (@borealBytes)\n  tags: Markdown, Mermaid diagrams, technical writing, documentation, diagrams\n---\n\n# Markdown and Mermaid Writing\n\n## Overview\n\nThis skill teaches you — and enforces a standard for — creating scientific documentation\nusing **markdown with embedded Mermaid diagrams as the default and canonical format**.\n\nThe core bet: a relationship expressed as a Mermaid diagram inside a `.md` file is more\nvaluable than any image. It is text, so it diffs cleanly in git. It requires no build step.\nIt renders natively on GitHub, GitLab, Notion, VS Code, and any markdown viewer. It uses\nfewer tokens than a prose description of the same relationship. And it can always be\nconverted to a polished image later — but the text version remains the source of truth.\n\n> \"The more you get your reports and files in .md in just regular text, which mermaid is\n> as well as being a simple 'script language'. This just helps with any downstream rendering\n> and especially AI generated images (using mermaid instead of just long form text to\n> describe relationships \u003C tokens). Additionally mermaid can render along with markdown for\n> easy use almost anywhere by humans or AI.\"\n>\n> — Clayton Young (@borealBytes), 2026-02-19\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Creating **any scientific document** — reports, analyses, manuscripts, methods sections\n- Writing **any documentation** — READMEs, how-tos, decision records, project docs\n- Producing **any diagram** — workflows, data pipelines, architectures, timelines, relationships\n- Generating **any output that will be version-controlled** — if it's going into git, it should be markdown\n- Working with **any other skill** — this skill defines the documentation layer that wraps every other output\n- Someone asks you to \"add a diagram\" or \"visualize the relationship\" — Mermaid first, always\n\nDo NOT start with Python matplotlib, seaborn, or AI image generation for structural or relational diagrams.\nThose are Phase 2 and Phase 3 — only used when Mermaid cannot express what's needed (e.g., scatter plots with real data, photorealistic images).\n\n## ? The Source Format Philosophy\n\n### Why text-based diagrams win\n\n| What matters | Mermaid in Markdown | Python \u002F AI Image |\n| ----------------------------- | :-----------------: | :---------------: |\n| Git diff readable | ✅ | ❌ binary blob |\n| Editable without regenerating | ✅ | ❌ |\n| Token efficient vs. prose | ✅ smaller | ❌ larger |\n| Renders without a build step | ✅ | ❌ needs hosting |\n| Parseable by AI without vision | ✅ | ❌ |\n| Works in GitHub \u002F GitLab \u002F Notion | ✅ | ⚠️ if hosted |\n| Accessible (screen readers) | ✅ accTitle\u002FaccDescr | ⚠️ needs alt text |\n| Convertible to image later | ✅ anytime | — already image |\n\n### The three-phase workflow\n\n```mermaid\nflowchart LR\n    accTitle: Three-Phase Documentation Workflow\n    accDescr: Phase 1 Mermaid in markdown is always required and is the source of truth. Phases 2 and 3 are optional downstream conversions for polished output.\n\n    p1[\"? Phase 1\u003Cbr\u002F>Mermaid in Markdown\u003Cbr\u002F>(ALWAYS — source of truth)\"]\n    p2[\"? Phase 2\u003Cbr\u002F>Python Generated\u003Cbr\u002F>(optional — data charts)\"]\n    p3[\"? Phase 3\u003Cbr\u002F>AI Generated Visuals\u003Cbr\u002F>(optional — polish)\"]\n    out[\"? Final Deliverable\"]\n\n    p1 --> out\n    p1 -.->|\"when needed\"| p2\n    p1 -.->|\"when needed\"| p3\n    p2 --> out\n    p3 --> out\n\n    classDef required fill:#dbeafe,stroke:#2563eb,stroke-width:2px,color:#1e3a5f\n    classDef optional fill:#fef9c3,stroke:#ca8a04,stroke-width:2px,color:#713f12\n    classDef output fill:#dcfce7,stroke:#16a34a,stroke-width:2px,color:#14532d\n\n    class p1 required\n    class p2,p3 optional\n    class out output\n```\n\n**Phase 1 is mandatory.** Even if you proceed to Phase 2 or 3, the Mermaid source stays committed.\n\n### What Mermaid can express\n\nMermaid covers 24 diagram types. Almost every scientific relationship fits one:\n\n| Use case | Diagram type | File |\n| -------------------------------------------- | ---------------- | ---------------------------------------------------- |\n| Experimental workflow \u002F decision logic | Flowchart | `references\u002Fdiagrams\u002Fflowchart.md` |\n| Service interactions \u002F API calls \u002F messaging | Sequence | `references\u002Fdiagrams\u002Fsequence.md` |\n| Data model \u002F schema | ER diagram | `references\u002Fdiagrams\u002Fer.md` |\n| State machine \u002F lifecycle | State | `references\u002Fdiagrams\u002Fstate.md` |\n| Project timeline \u002F roadmap | Gantt | `references\u002Fdiagrams\u002Fgantt.md` |\n| Proportions \u002F composition | Pie | `references\u002Fdiagrams\u002Fpie.md` |\n| System architecture (zoom levels) | C4 | `references\u002Fdiagrams\u002Fc4.md` |\n| Concept hierarchy \u002F brainstorm | Mindmap | `references\u002Fdiagrams\u002Fmindmap.md` |\n| Chronological events \u002F history | Timeline | `references\u002Fdiagrams\u002Ftimeline.md` |\n| Class hierarchy \u002F type relationships | Class | `references\u002Fdiagrams\u002Fclass.md` |\n| User journey \u002F satisfaction map | User Journey | `references\u002Fdiagrams\u002Fuser_journey.md` |\n| Two-axis comparison \u002F prioritization | Quadrant | `references\u002Fdiagrams\u002Fquadrant.md` |\n| Requirements traceability | Requirement | `references\u002Fdiagrams\u002Frequirement.md` |\n| Flow magnitude \u002F resource distribution | Sankey | `references\u002Fdiagrams\u002Fsankey.md` |\n| Numeric trends \u002F bar + line charts | XY Chart | `references\u002Fdiagrams\u002Fxy_chart.md` |\n| Component layout \u002F spatial arrangement | Block | `references\u002Fdiagrams\u002Fblock.md` |\n| Work item status \u002F task columns | Kanban | `references\u002Fdiagrams\u002Fkanban.md` |\n| Cloud infrastructure \u002F service topology | Architecture | `references\u002Fdiagrams\u002Farchitecture.md` |\n| Multi-dimensional comparison \u002F skills radar | Radar | `references\u002Fdiagrams\u002Fradar.md` |\n| Hierarchical proportions \u002F budget | Treemap | `references\u002Fdiagrams\u002Ftreemap.md` |\n| Binary protocol \u002F data format | Packet | `references\u002Fdiagrams\u002Fpacket.md` |\n| Git branching \u002F merge strategy | Git Graph | `references\u002Fdiagrams\u002Fgit_graph.md` |\n| Code-style sequence (programming syntax) | ZenUML | `references\u002Fdiagrams\u002Fzenuml.md` |\n| Multi-diagram composition patterns | Complex Examples | `references\u002Fdiagrams\u002Fcomplex_examples.md` |\n\n> ? **Pick the right type, not the easy one.** Don't default to flowcharts for everything.\n> A timeline beats a flowchart for chronological events. A sequence beats a flowchart for\n> service interactions. Scan the table and match.\n\n---\n\n## ? Core workflow\n\n### Step 1: Identify the document type\n\nCheck if a template exists before writing from scratch:\n\n| Document type | Template |\n| ------------------------------ | ----------------------------------------------- |\n| Pull request record | `templates\u002Fpull_request.md` |\n| Issue \u002F bug \u002F feature request | `templates\u002Fissue.md` |\n| Sprint \u002F project board | `templates\u002Fkanban.md` |\n| Architecture decision (ADR) | `templates\u002Fdecision_record.md` |\n| Presentation \u002F briefing | `templates\u002Fpresentation.md` |\n| Research paper \u002F analysis | `templates\u002Fresearch_paper.md` |\n| Project documentation | `templates\u002Fproject_documentation.md` |\n| How-to \u002F tutorial | `templates\u002Fhow_to_guide.md` |\n| Status report | `templates\u002Fstatus_report.md` |\n\n### Step 2: Read the style guide\n\nBefore writing any `.md` file: read `references\u002Fmarkdown_style_guide.md`.\n\nKey rules to internalize:\n\n- **One H1 per document** — the title. Never more.\n- **Emoji on H2 headings only** — one emoji per H2, none in H3\u002FH4\n- **Cite everything** — every external claim gets a footnote `[^N]` with full URL\n- **Bold sparingly** — max 2-3 bold terms per paragraph, never full sentences\n- **Horizontal rule after every `\u003C\u002Fdetails>`** — mandatory\n- **Tables over prose** for comparisons, configurations, structured data\n- **Diagrams over walls of text** — if it describes flow, structure, or relationships, add Mermaid\n\n### Step 3: Pick the diagram type and read its guide\n\nBefore creating any Mermaid diagram: read `references\u002Fmermaid_style_guide.md`.\n\nThen open the specific type file (e.g., `references\u002Fdiagrams\u002Fflowchart.md`) for the exemplar, tips, and copy-paste template.\n\nMandatory rules for every diagram:\n\n```\naccTitle: Short Name 3-8 Words\naccDescr: One or two sentences explaining what this diagram shows.\n```\n\n- **No `%%{init}` directives** — breaks GitHub dark mode\n- **No inline `style`** — use `classDef` only\n- **One emoji per node max** — at the start of the label\n- **`snake_case` node IDs** — match the label\n\n### Step 4: Write the document\n\nStart from the template. Apply the markdown style guide. Place diagrams inline with related text — not in a separate \"Figures\" section.\n\n### Step 5: Commit as text\n\nThe `.md` file with embedded Mermaid is what gets committed. If you also generated a PNG or AI image, those are supplementary — the markdown is the source.\n\n---\n\n## ⚠️ Common pitfalls\n\n### Radar chart syntax (`radar-beta`)\n\n**WRONG:**\n```mermaid\nradar\ntitle Example\nx-axis [\"A\", \"B\", \"C\"]\n\"Series\" : [1, 2, 3]\n```\n\n**CORRECT:**\n```mermaid\nradar-beta\ntitle Example\naxis a[\"A\"], b[\"B\"], c[\"C\"]\ncurve series[\"Series\"]{1, 2, 3}\nmax 3\n```\n\n- **Use `radar-beta`** not `radar` (the bare keyword doesn't exist)\n- **Use `axis`** to define dimensions, **not** `x-axis`\n- **Use `curve`** to define data series, **not** quoted labels with colon\n- **No `accTitle`\u002F`accDescr`** — radar-beta doesn't support accessibility annotations; always add a descriptive italic paragraph above the diagram\n\n### XY Chart vs Radar confusion\n\n| Diagram | Keyword | Axis syntax | Data syntax |\n| ------- | ------- | ----------- | ----------- |\n| **XY Chart** (bars\u002Flines) | `xychart-beta` | `x-axis [\"Label1\", \"Label2\"]` | `bar [10, 20]` or `line [10, 20]` |\n| **Radar** (spider\u002Fweb) | `radar-beta` | `axis id[\"Label\"]` | `curve id[\"Label\"]{10, 20}` |\n\n### Forgetting `accTitle`\u002F`accDescr` on supported types\n\nOnly some diagram types support `accTitle`\u002F`accDescr`. For those that don't, always place a descriptive italic paragraph directly above the code block:\n\n> _Radar chart comparing three methods across five performance dimensions. Note: Radar charts do not support accTitle\u002FaccDescr._\n\n```mermaid\nradar-beta\n...\n```\n\n---\n\n## ? Integration with other skills\n\n### With `scientific-schematics`\n\n`scientific-schematics` generates AI-powered publication-quality images (PNG). Use the Mermaid diagram as the **brief** for the schematic:\n\n```\nWorkflow:\n1. Create the concept as Mermaid in .md (this skill — Phase 1)\n2. Describe the same concept to scientific-schematics for a polished PNG (Phase 3)\n3. Commit both — the .md as source, the PNG as a supplementary figure\n```\n\n### With `scientific-writing`\n\nWhen `scientific-writing` produces a manuscript, all diagrams and structural figures should use this skill's standards. The writing skill handles prose and citations; this skill handles visual structure.\n\n```\nWorkflow:\n1. Use scientific-writing to draft the manuscript\n2. For every figure that shows a workflow, architecture, or relationship:\n   - Replace placeholder with a Mermaid diagram following this skill's guide\n3. Use scientific-schematics only for figures that truly need photorealistic\u002Fcomplex rendering\n```\n\n### With `literature-review`\n\nLiterature review produces summaries with lots of relationship data. Use this skill to:\n\n- Create concept maps (Mindmap) of the literature landscape\n- Show publication timelines (Timeline or Gantt)\n- Compare methodologies (Quadrant or Radar)\n- Diagram data flows described in papers (Sequence or Flowchart)\n\n### With any skill that produces output documents\n\nBefore finalizing any document from any skill, apply this skill's checklist:\n\n- [ ] Does the document use a template? If so, did I start from the right one?\n- [ ] Are all diagrams in Mermaid with `accTitle` + `accDescr`?\n- [ ] No `%%{init}`, no inline `style`, only `classDef`?\n- [ ] Are all external claims cited with `[^N]`?\n- [ ] One H1, emoji on H2 only?\n- [ ] Horizontal rules after every `\u003C\u002Fdetails>`?\n\n---\n\n## ? Reference index\n\n### Style guides\n\n| Guide | Path | Lines | What it covers |\n| ----------------------- | ------------------------------------------- | ----- | -------------------------------------------------- |\n| Markdown Style Guide | `references\u002Fmarkdown_style_guide.md` | ~733 | Headings, formatting, citations, tables, Mermaid integration, templates, quality checklist |\n| Mermaid Style Guide | `references\u002Fmermaid_style_guide.md` | ~458 | Accessibility, emoji set, color classes, theme neutrality, type selection, complexity tiers |\n\n### Diagram type guides (24 types)\n\nEach file contains: production-quality exemplar, tips specific to that type, and a copy-paste template.\n\n`references\u002Fdiagrams\u002F` — architecture, block, c4, class, complex\\_examples, er, flowchart, gantt, git\\_graph, kanban, mindmap, packet, pie, quadrant, radar, requirement, sankey, sequence, state, timeline, treemap, user\\_journey, xy\\_chart, zenuml\n\n### Document templates (9 types)\n\n`templates\u002F` — decision\\_record, how\\_to\\_guide, issue, kanban, presentation, project\\_documentation, pull\\_request, research\\_paper, status\\_report\n\n### Examples\n\n`assets\u002Fexamples\u002Fexample-research-report.md` — a complete scientific research report demonstrating proper heading hierarchy, multiple diagram types (flowchart, sequence, gantt), tables, footnote citations, collapsible sections, and all style guide rules applied.\n\n---\n\n## ? Attribution\n\nAll style guides, diagram type guides, and document templates in this skill are ported from the `SuperiorByteWorks-LLC\u002Fagent-project` repository under the Apache-2.0 License.\n\n- **Source**: https:\u002F\u002Fgithub.com\u002FSuperiorByteWorks-LLC\u002Fagent-project\n- **Author**: Clayton Young \u002F Superior Byte Works, LLC (@borealBytes)\n- **License**: Apache-2.0\n\nThis skill (as part of research-agent-skills) is distributed under the MIT License. The included Apache-2.0 content is compatible for downstream use with attribution retained, as preserved in the file headers throughout this skill.\n\n---\n\n[^1]: GitHub Blog. (2022). \"Include diagrams in your Markdown files with Mermaid.\" https:\u002F\u002Fgithub.blog\u002F2022-02-14-include-diagrams-markdown-files-mermaid\u002F\n\n[^2]: Mermaid. \"Mermaid Diagramming and Charting Tool.\" https:\u002F\u002Fmermaid.js.org\u002F\n\n## Agent operating procedure\n\n1. **Check the environment.** Collect the user's draft, data, figures and target venue before writing anything.\n2. **Pin down the inputs.** Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.\n3. **Run a small version first.** Draft one section or paragraph and confirm tone, structure and terminology with the user.\n4. **Execute the full task** using the instructions and references above.\n5. **Validate the result.** Every claim traces to the user's data or a verified source; numbers match tables and figures; citations are real (`citation-verification`).\n6. **Report.** State what was run (versions, commands, parameters), what was checked, and what is still uncertain.\n\n| If this happens | Do this |\n|---|---|\n| A claim has no supporting data or citation | Flag it in the text (e.g. `[citation needed]`) instead of inventing support. |\n| A function, flag or endpoint in these instructions is missing in the installed version | Check the installed version's own documentation (`help()`, `--help`, official docs), adapt, and tell the user. Never invent an API. |\n| A required input, identifier or parameter is ambiguous | Ask the user, or state the assumption explicitly before running. |\n\n**Integrity rules**\n\n- Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.\n- The user is the author: never add results, references or claims they did not provide or approve.\n- Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.\n- Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.\n\n## Related skills\n\n- `literature-review`: Runs systematic literature reviews by searching PubMed, arXiv, bioRxiv, and Semantic Scholar (plus web search via parallel-cli), screening…\n- `academic-plotting`: Generates publication-quality figures for ML papers from research context.\n","# Markdown and Mermaid Writing\n\n## Overview\n\nThis skill teaches you — and enforces a standard for — creating scientific documentation\nusing **markdown with embedded Mermaid diagrams as the default and canonical format**.\n\nThe core bet: a relationship expressed as a Mermaid diagram inside a `.md` file is more\nvaluable than any image. It is text, so it diffs cleanly in git. It requires no build step.\nIt renders natively on GitHub, GitLab, Notion, VS Code, and any markdown viewer. It uses\nfewer tokens than a prose description of the same relationship. And it can always be\nconverted to a polished image later — but the text version remains the source of truth.\n\n> \"The more you get your reports and files in .md in just regular text, which mermaid is\n> as well as being a simple 'script language'. This just helps with any downstream rendering\n> and especially AI generated images (using mermaid instead of just long form text to\n> describe relationships \u003C tokens). Additionally mermaid can render along with markdown for\n> easy use almost anywhere by humans or AI.\"\n>\n> — Clayton Young (@borealBytes), 2026-02-19\n\n## When to Use This Skill\n\nUse this skill when:\n\n- Creating **any scientific document** — reports, analyses, manuscripts, methods sections\n- Writing **any documentation** — READMEs, how-tos, decision records, project docs\n- Producing **any diagram** — workflows, data pipelines, architectures, timelines, relationships\n- Generating **any output that will be version-controlled** — if it's going into git, it should be markdown\n- Working with **any other skill** — this skill defines the documentation layer that wraps every other output\n- Someone asks you to \"add a diagram\" or \"visualize the relationship\" — Mermaid first, always\n\nDo NOT start with Python matplotlib, seaborn, or AI image generation for structural or relational diagrams.\nThose are Phase 2 and Phase 3 — only used when Mermaid cannot express what's needed (e.g., scatter plots with real data, photorealistic images).\n\n## ? The Source Format Philosophy\n\n### Why text-based diagrams win\n\n| What matters | Mermaid in Markdown | Python \u002F AI Image |\n| ----------------------------- | :-----------------: | :---------------: |\n| Git diff readable | ✅ | ❌ binary blob |\n| Editable without regenerating | ✅ | ❌ |\n| Token efficient vs. prose | ✅ smaller | ❌ larger |\n| Renders without a build step | ✅ | ❌ needs hosting |\n| Parseable by AI without vision | ✅ | ❌ |\n| Works in GitHub \u002F GitLab \u002F Notion | ✅ | ⚠️ if hosted |\n| Accessible (screen readers) | ✅ accTitle\u002FaccDescr | ⚠️ needs alt text |\n| Convertible to image later | ✅ anytime | — already image |\n\n### The three-phase workflow\n\n```mermaid\nflowchart LR\n    accTitle: Three-Phase Documentation Workflow\n    accDescr: Phase 1 Mermaid in markdown is always required and is the source of truth. Phases 2 and 3 are optional downstream conversions for polished output.\n\n    p1[\"? Phase 1\u003Cbr\u002F>Mermaid in Markdown\u003Cbr\u002F>(ALWAYS — source of truth)\"]\n    p2[\"? Phase 2\u003Cbr\u002F>Python Generated\u003Cbr\u002F>(optional — data charts)\"]\n    p3[\"? Phase 3\u003Cbr\u002F>AI Generated Visuals\u003Cbr\u002F>(optional — polish)\"]\n    out[\"? Final Deliverable\"]\n\n    p1 --> out\n    p1 -.->|\"when needed\"| p2\n    p1 -.->|\"when needed\"| p3\n    p2 --> out\n    p3 --> out\n\n    classDef required fill:#dbeafe,stroke:#2563eb,stroke-width:2px,color:#1e3a5f\n    classDef optional fill:#fef9c3,stroke:#ca8a04,stroke-width:2px,color:#713f12\n    classDef output fill:#dcfce7,stroke:#16a34a,stroke-width:2px,color:#14532d\n\n    class p1 required\n    class p2,p3 optional\n    class out output\n```\n\n**Phase 1 is mandatory.** Even if you proceed to Phase 2 or 3, the Mermaid source stays committed.\n\n### What Mermaid can express\n\nMermaid covers 24 diagram types. Almost every scientific relationship fits one:\n\n| Use case | Diagram type | File |\n| -------------------------------------------- | ---------------- | ---------------------------------------------------- |\n| Experimental workflow \u002F decision logic | Flowchart | `references\u002Fdiagrams\u002Fflowchart.md` |\n| Service interactions \u002F API calls \u002F messaging | Sequence | `references\u002Fdiagrams\u002Fsequence.md` |\n| Data model \u002F schema | ER diagram | `references\u002Fdiagrams\u002Fer.md` |\n| State machine \u002F lifecycle | State | `references\u002Fdiagrams\u002Fstate.md` |\n| Project timeline \u002F roadmap | Gantt | `references\u002Fdiagrams\u002Fgantt.md` |\n| Proportions \u002F composition | Pie | `references\u002Fdiagrams\u002Fpie.md` |\n| System architecture (zoom levels) | C4 | `references\u002Fdiagrams\u002Fc4.md` |\n| Concept hierarchy \u002F brainstorm | Mindmap | `references\u002Fdiagrams\u002Fmindmap.md` |\n| Chronological events \u002F history | Timeline | `references\u002Fdiagrams\u002Ftimeline.md` |\n| Class hierarchy \u002F type relationships | Class | `references\u002Fdiagrams\u002Fclass.md` |\n| User journey \u002F satisfaction map | User Journey | `references\u002Fdiagrams\u002Fuser_journey.md` |\n| Two-axis comparison \u002F prioritization | Quadrant | `references\u002Fdiagrams\u002Fquadrant.md` |\n| Requirements traceability | Requirement | `references\u002Fdiagrams\u002Frequirement.md` |\n| Flow magnitude \u002F resource distribution | Sankey | `references\u002Fdiagrams\u002Fsankey.md` |\n| Numeric trends \u002F bar + line charts | XY Chart | `references\u002Fdiagrams\u002Fxy_chart.md` |\n| Component layout \u002F spatial arrangement | Block | `references\u002Fdiagrams\u002Fblock.md` |\n| Work item status \u002F task columns | Kanban | `references\u002Fdiagrams\u002Fkanban.md` |\n| Cloud infrastructure \u002F service topology | Architecture | `references\u002Fdiagrams\u002Farchitecture.md` |\n| Multi-dimensional comparison \u002F skills radar | Radar | `references\u002Fdiagrams\u002Fradar.md` |\n| Hierarchical proportions \u002F budget | Treemap | `references\u002Fdiagrams\u002Ftreemap.md` |\n| Binary protocol \u002F data format | Packet | `references\u002Fdiagrams\u002Fpacket.md` |\n| Git branching \u002F merge strategy | Git Graph | `references\u002Fdiagrams\u002Fgit_graph.md` |\n| Code-style sequence (programming syntax) | ZenUML | `references\u002Fdiagrams\u002Fzenuml.md` |\n| Multi-diagram composition patterns | Complex Examples | `references\u002Fdiagrams\u002Fcomplex_examples.md` |\n\n> ? **Pick the right type, not the easy one.** Don't default to flowcharts for everything.\n> A timeline beats a flowchart for chronological events. A sequence beats a flowchart for\n> service interactions. Scan the table and match.\n\n---\n\n## ? Core workflow\n\n### Step 1: Identify the document type\n\nCheck if a template exists before writing from scratch:\n\n| Document type | Template |\n| ------------------------------ | ----------------------------------------------- |\n| Pull request record | `templates\u002Fpull_request.md` |\n| Issue \u002F bug \u002F feature request | `templates\u002Fissue.md` |\n| Sprint \u002F project board | `templates\u002Fkanban.md` |\n| Architecture decision (ADR) | `templates\u002Fdecision_record.md` |\n| Presentation \u002F briefing | `templates\u002Fpresentation.md` |\n| Research paper \u002F analysis | `templates\u002Fresearch_paper.md` |\n| Project documentation | `templates\u002Fproject_documentation.md` |\n| How-to \u002F tutorial | `templates\u002Fhow_to_guide.md` |\n| Status report | `templates\u002Fstatus_report.md` |\n\n### Step 2: Read the style guide\n\nBefore writing any `.md` file: read `references\u002Fmarkdown_style_guide.md`.\n\nKey rules to internalize:\n\n- **One H1 per document** — the title. Never more.\n- **Emoji on H2 headings only** — one emoji per H2, none in H3\u002FH4\n- **Cite everything** — every external claim gets a footnote `[^N]` with full URL\n- **Bold sparingly** — max 2-3 bold terms per paragraph, never full sentences\n- **Horizontal rule after every `\u003C\u002Fdetails>`** — mandatory\n- **Tables over prose** for comparisons, configurations, structured data\n- **Diagrams over walls of text** — if it describes flow, structure, or relationships, add Mermaid\n\n### Step 3: Pick the diagram type and read its guide\n\nBefore creating any Mermaid diagram: read `references\u002Fmermaid_style_guide.md`.\n\nThen open the specific type file (e.g., `references\u002Fdiagrams\u002Fflowchart.md`) for the exemplar, tips, and copy-paste template.\n\nMandatory rules for every diagram:\n\n```\naccTitle: Short Name 3-8 Words\naccDescr: One or two sentences explaining what this diagram shows.\n```\n\n- **No `%%{init}` directives** — breaks GitHub dark mode\n- **No inline `style`** — use `classDef` only\n- **One emoji per node max** — at the start of the label\n- **`snake_case` node IDs** — match the label\n\n### Step 4: Write the document\n\nStart from the template. Apply the markdown style guide. Place diagrams inline with related text — not in a separate \"Figures\" section.\n\n### Step 5: Commit as text\n\nThe `.md` file with embedded Mermaid is what gets committed. If you also generated a PNG or AI image, those are supplementary — the markdown is the source.\n\n---\n\n## ⚠️ Common pitfalls\n\n### Radar chart syntax (`radar-beta`)\n\n**WRONG:**\n```mermaid\nradar\ntitle Example\nx-axis [\"A\", \"B\", \"C\"]\n\"Series\" : [1, 2, 3]\n```\n\n**CORRECT:**\n```mermaid\nradar-beta\ntitle Example\naxis a[\"A\"], b[\"B\"], c[\"C\"]\ncurve series[\"Series\"]{1, 2, 3}\nmax 3\n```\n\n- **Use `radar-beta`** not `radar` (the bare keyword doesn't exist)\n- **Use `axis`** to define dimensions, **not** `x-axis`\n- **Use `curve`** to define data series, **not** quoted labels with colon\n- **No `accTitle`\u002F`accDescr`** — radar-beta doesn't support accessibility annotations; always add a descriptive italic paragraph above the diagram\n\n### XY Chart vs Radar confusion\n\n| Diagram | Keyword | Axis syntax | Data syntax |\n| ------- | ------- | ----------- | ----------- |\n| **XY Chart** (bars\u002Flines) | `xychart-beta` | `x-axis [\"Label1\", \"Label2\"]` | `bar [10, 20]` or `line [10, 20]` |\n| **Radar** (spider\u002Fweb) | `radar-beta` | `axis id[\"Label\"]` | `curve id[\"Label\"]{10, 20}` |\n\n### Forgetting `accTitle`\u002F`accDescr` on supported types\n\nOnly some diagram types support `accTitle`\u002F`accDescr`. For those that don't, always place a descriptive italic paragraph directly above the code block:\n\n> _Radar chart comparing three methods across five performance dimensions. Note: Radar charts do not support accTitle\u002FaccDescr._\n\n```mermaid\nradar-beta\n...\n```\n\n---\n\n## ? Integration with other skills\n\n### With `scientific-schematics`\n\n`scientific-schematics` generates AI-powered publication-quality images (PNG). Use the Mermaid diagram as the **brief** for the schematic:\n\n```\nWorkflow:\n1. Create the concept as Mermaid in .md (this skill — Phase 1)\n2. Describe the same concept to scientific-schematics for a polished PNG (Phase 3)\n3. Commit both — the .md as source, the PNG as a supplementary figure\n```\n\n### With `scientific-writing`\n\nWhen `scientific-writing` produces a manuscript, all diagrams and structural figures should use this skill's standards. The writing skill handles prose and citations; this skill handles visual structure.\n\n```\nWorkflow:\n1. Use scientific-writing to draft the manuscript\n2. For every figure that shows a workflow, architecture, or relationship:\n   - Replace placeholder with a Mermaid diagram following this skill's guide\n3. Use scientific-schematics only for figures that truly need photorealistic\u002Fcomplex rendering\n```\n\n### With `literature-review`\n\nLiterature review produces summaries with lots of relationship data. Use this skill to:\n\n- Create concept maps (Mindmap) of the literature landscape\n- Show publication timelines (Timeline or Gantt)\n- Compare methodologies (Quadrant or Radar)\n- Diagram data flows described in papers (Sequence or Flowchart)\n\n### With any skill that produces output documents\n\nBefore finalizing any document from any skill, apply this skill's checklist:\n\n- [ ] Does the document use a template? If so, did I start from the right one?\n- [ ] Are all diagrams in Mermaid with `accTitle` + `accDescr`?\n- [ ] No `%%{init}`, no inline `style`, only `classDef`?\n- [ ] Are all external claims cited with `[^N]`?\n- [ ] One H1, emoji on H2 only?\n- [ ] Horizontal rules after every `\u003C\u002Fdetails>`?\n\n---\n\n## ? Reference index\n\n### Style guides\n\n| Guide | Path | Lines | What it covers |\n| ----------------------- | ------------------------------------------- | ----- | -------------------------------------------------- |\n| Markdown Style Guide | `references\u002Fmarkdown_style_guide.md` | ~733 | Headings, formatting, citations, tables, Mermaid integration, templates, quality checklist |\n| Mermaid Style Guide | `references\u002Fmermaid_style_guide.md` | ~458 | Accessibility, emoji set, color classes, theme neutrality, type selection, complexity tiers |\n\n### Diagram type guides (24 types)\n\nEach file contains: production-quality exemplar, tips specific to that type, and a copy-paste template.\n\n`references\u002Fdiagrams\u002F` — architecture, block, c4, class, complex\\_examples, er, flowchart, gantt, git\\_graph, kanban, mindmap, packet, pie, quadrant, radar, requirement, sankey, sequence, state, timeline, treemap, user\\_journey, xy\\_chart, zenuml\n\n### Document templates (9 types)\n\n`templates\u002F` — decision\\_record, how\\_to\\_guide, issue, kanban, presentation, project\\_documentation, pull\\_request, research\\_paper, status\\_report\n\n### Examples\n\n`assets\u002Fexamples\u002Fexample-research-report.md` — a complete scientific research report demonstrating proper heading hierarchy, multiple diagram types (flowchart, sequence, gantt), tables, footnote citations, collapsible sections, and all style guide rules applied.\n\n---\n\n## ? Attribution\n\nAll style guides, diagram type guides, and document templates in this skill are ported from the `SuperiorByteWorks-LLC\u002Fagent-project` repository under the Apache-2.0 License.\n\n- **Source**: https:\u002F\u002Fgithub.com\u002FSuperiorByteWorks-LLC\u002Fagent-project\n- **Author**: Clayton Young \u002F Superior Byte Works, LLC (@borealBytes)\n- **License**: Apache-2.0\n\nThis skill (as part of research-agent-skills) is distributed under the MIT License. The included Apache-2.0 content is compatible for downstream use with attribution retained, as preserved in the file headers throughout this skill.\n\n---\n\n[^1]: GitHub Blog. (2022). \"Include diagrams in your Markdown files with Mermaid.\" https:\u002F\u002Fgithub.blog\u002F2022-02-14-include-diagrams-markdown-files-mermaid\u002F\n\n[^2]: Mermaid. \"Mermaid Diagramming and Charting Tool.\" https:\u002F\u002Fmermaid.js.org\u002F\n\n## Agent operating procedure\n\n1. **Check the environment.** Collect the user's draft, data, figures and target venue before writing anything.\n2. **Pin down the inputs.** Confirm formats, identifiers and parameters from the data or the user. Ask rather than guess any value that changes the result.\n3. **Run a small version first.** Draft one section or paragraph and confirm tone, structure and terminology with the user.\n4. **Execute the full task** using the instructions and references above.\n5. **Validate the result.** Every claim traces to the user's data or a verified source; numbers match tables and figures; citations are real (`citation-verification`).\n6. **Report.** State what was run (versions, commands, parameters), what was checked, and what is still uncertain.\n\n| If this happens | Do this |\n|---|---|\n| A claim has no supporting data or citation | Flag it in the text (e.g. `[citation needed]`) instead of inventing support. |\n| A function, flag or endpoint in these instructions is missing in the installed version | Check the installed version's own documentation (`help()`, `--help`, official docs), adapt, and tell the user. Never invent an API. |\n| A required input, identifier or parameter is ambiguous | Ask the user, or state the assumption explicitly before running. |\n\n**Integrity rules**\n\n- Never fabricate results, parameters, identifiers, citations or statistics. If something cannot be run or verified, say so plainly.\n- The user is the author: never add results, references or claims they did not provide or approve.\n- Treat version-specific details here as possibly outdated: confirm them against the official documentation for the installed version.\n- Ask before actions that cost money, consume shared GPUs or cloud quota, touch personal or patient data, or cannot be undone.\n\n## Related skills\n\n- `literature-review`: Runs systematic literature reviews by searching PubMed, arXiv, bioRxiv, and Semantic Scholar (plus web search via parallel-cli), screening…\n- `academic-plotting`: Generates publication-quality figures for ML papers from research context.\n",{"name":5,"license":15,"metadata":63,"description":7,"allowed-tools":72},{"tags":64,"version":65,"category":66,"maintainer":67,"contributor":68,"skill-source":69,"skill-version":70,"skill-contributors":71},"Markdown, Mermaid diagrams, technical writing, documentation, diagrams","1.1","research-writing","Kalaris Labs","Clayton Young \u002F Superior Byte Works, LLC (@borealBytes)","https:\u002F\u002Fgithub.com\u002FSuperiorByteWorks-LLC\u002Fagent-project","1.0.0","Clayton Young (Superior Byte Works, LLC \u002F @borealBytes; Author and originator)","Read Write Edit Bash","main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":84,"prompt":94,"zipAvailable":95},[85,88,91],{"tool":86,"command":87},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill markdown-mermaid-writing",{"tool":89,"command":90},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill markdown-mermaid-writing",{"tool":92,"command":93},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill markdown-mermaid-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002FSKILL.md",true,[97,103,109,113,117,121,125,129,133,137,141,145,149,153,157,161,165,169,173,177,181,185,189,193,197,201,205,209,213,217,221,225,229,233,237,241],{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"assets\u002Fexamples\u002Fexample-research-report.md","ASSET","资产文件",9010,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Fassets\u002Fexamples\u002Fexample-research-report.md",{"path":104,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":107,"sourceHtmlUrl":108},"references\u002Fdiagrams\u002Farchitecture.md","REFERENCE","参考文档",4369,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Farchitecture.md",{"path":110,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":111,"sourceHtmlUrl":112},"references\u002Fdiagrams\u002Fblock.md",4825,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fblock.md",{"path":114,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":115,"sourceHtmlUrl":116},"references\u002Fdiagrams\u002Fc4.md",6201,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fc4.md",{"path":118,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":119,"sourceHtmlUrl":120},"references\u002Fdiagrams\u002Fclass.md",8521,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fclass.md",{"path":122,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":123,"sourceHtmlUrl":124},"references\u002Fdiagrams\u002Fcomplex_examples.md",17079,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fcomplex_examples.md",{"path":126,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":127,"sourceHtmlUrl":128},"references\u002Fdiagrams\u002Fer.md",7601,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fer.md",{"path":130,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":131,"sourceHtmlUrl":132},"references\u002Fdiagrams\u002Fflowchart.md",6961,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fflowchart.md",{"path":134,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":135,"sourceHtmlUrl":136},"references\u002Fdiagrams\u002Fgantt.md",5851,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fgantt.md",{"path":138,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":139,"sourceHtmlUrl":140},"references\u002Fdiagrams\u002Fgit_graph.md",2009,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fgit_graph.md",{"path":142,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":143,"sourceHtmlUrl":144},"references\u002Fdiagrams\u002Fkanban.md",3544,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fkanban.md",{"path":146,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":147,"sourceHtmlUrl":148},"references\u002Fdiagrams\u002Fmindmap.md",2232,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fmindmap.md",{"path":150,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":151,"sourceHtmlUrl":152},"references\u002Fdiagrams\u002Fpacket.md",1721,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fpacket.md",{"path":154,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":155,"sourceHtmlUrl":156},"references\u002Fdiagrams\u002Fpie.md",1560,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fpie.md",{"path":158,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":159,"sourceHtmlUrl":160},"references\u002Fdiagrams\u002Fquadrant.md",2163,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fquadrant.md",{"path":162,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":163,"sourceHtmlUrl":164},"references\u002Fdiagrams\u002Fradar.md",2176,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fradar.md",{"path":166,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":167,"sourceHtmlUrl":168},"references\u002Fdiagrams\u002Frequirement.md",2463,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Frequirement.md",{"path":170,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":171,"sourceHtmlUrl":172},"references\u002Fdiagrams\u002Fsankey.md",2143,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fsankey.md",{"path":174,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":175,"sourceHtmlUrl":176},"references\u002Fdiagrams\u002Fsequence.md",5510,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fsequence.md",{"path":178,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":179,"sourceHtmlUrl":180},"references\u002Fdiagrams\u002Fstate.md",5464,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fstate.md",{"path":182,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":183,"sourceHtmlUrl":184},"references\u002Fdiagrams\u002Ftimeline.md",4181,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Ftimeline.md",{"path":186,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":187,"sourceHtmlUrl":188},"references\u002Fdiagrams\u002Ftreemap.md",2039,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Ftreemap.md",{"path":190,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":191,"sourceHtmlUrl":192},"references\u002Fdiagrams\u002Fuser_journey.md",5049,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fuser_journey.md",{"path":194,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":195,"sourceHtmlUrl":196},"references\u002Fdiagrams\u002Fxy_chart.md",1887,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fxy_chart.md",{"path":198,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":199,"sourceHtmlUrl":200},"references\u002Fdiagrams\u002Fzenuml.md",2285,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fzenuml.md",{"path":202,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":203,"sourceHtmlUrl":204},"references\u002Fmarkdown_style_guide.md",34845,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fmarkdown_style_guide.md",{"path":206,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":207,"sourceHtmlUrl":208},"references\u002Fmermaid_style_guide.md",26241,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fmermaid_style_guide.md",{"path":210,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":211,"sourceHtmlUrl":212},"templates\u002Fdecision_record.md",6976,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fdecision_record.md",{"path":214,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":215,"sourceHtmlUrl":216},"templates\u002Fhow_to_guide.md",6811,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fhow_to_guide.md",{"path":218,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":219,"sourceHtmlUrl":220},"templates\u002Fissue.md",12305,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fissue.md",{"path":222,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":223,"sourceHtmlUrl":224},"templates\u002Fkanban.md",10921,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fkanban.md",{"path":226,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":227,"sourceHtmlUrl":228},"templates\u002Fpresentation.md",7979,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fpresentation.md",{"path":230,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":231,"sourceHtmlUrl":232},"templates\u002Fproject_documentation.md",11419,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fproject_documentation.md",{"path":234,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":235,"sourceHtmlUrl":236},"templates\u002Fpull_request.md",12340,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fpull_request.md",{"path":238,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":239,"sourceHtmlUrl":240},"templates\u002Fresearch_paper.md",10098,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fresearch_paper.md",{"path":242,"resourceType":105,"resourceTypeDesc":106,"sizeBytes":243,"sourceHtmlUrl":244},"templates\u002Fstatus_report.md",6989,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002FKalarisLabs\u002Fresearch-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fstatus_report.md",[246,256,264,272,280,288],{"skillNo":247,"name":248,"nameZh":6,"description":249,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":250,"licenseFileUrl":251,"sourceHtmlUrl":252,"categories":253,"keywords":254,"publishedAt":255},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":257,"name":258,"nameZh":6,"description":259,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":250,"licenseFileUrl":260,"sourceHtmlUrl":261,"categories":262,"keywords":263,"publishedAt":255},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":265,"name":266,"nameZh":6,"description":267,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":250,"licenseFileUrl":268,"sourceHtmlUrl":269,"categories":270,"keywords":271,"publishedAt":255},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":273,"name":274,"nameZh":6,"description":275,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":250,"licenseFileUrl":276,"sourceHtmlUrl":277,"categories":278,"keywords":279,"publishedAt":255},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":281,"name":282,"nameZh":6,"description":283,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":250,"licenseFileUrl":284,"sourceHtmlUrl":285,"categories":286,"keywords":287,"publishedAt":255},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":289,"name":290,"nameZh":6,"description":291,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":250,"licenseFileUrl":292,"sourceHtmlUrl":293,"categories":294,"keywords":295,"publishedAt":255},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]