[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7166CF5HSR7SVZYZFWTDX55":3,"skill-same:01M7166CF5HSR7SVZYZFWTDX55":235},{"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":34,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":67,"commitSha":68,"skillDirectory":69,"forksCount":14,"repositoryHtmlUrl":70,"repositoryHomepageUrl":6,"ownerHtmlUrl":71,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":72,"install":73,"resources":86},"01M7166CF5HSR7SVZYZFWTDX55","markdown-mermaid-writing",null,"Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.","fadrienne\u002FMyGitHub","fadrienne","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F197874571?v=4","01M6X64V8VWCRSMFZ4EPS2BWXG","Francesca Adrienne","01M6X64VD5MW4F9PHDWQKS7ZAF",0,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002FSKILL.md",[18,23,26,29],{"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},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"markdown mermaid writing","mermaid","markdown","writing","read","scientific","diagram","references","documentation","text","guides","team","analysis","Bash","when","default","project","visualization","diagrams","community","2026-11-10 10:12:30",false,"---\nname: markdown-mermaid-writing\ndescription: Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.\nallowed-tools: Read Write Edit Bash\nlicense: Apache-2.0\nmetadata: {\"version\": \"1.1\", \"skill-author\": \"Clayton Young \u002F Superior Byte Works, LLC (@borealBytes)\", \"skill-source\": \"https:\u002F\u002Fgithub.com\u002FSuperiorByteWorks-LLC\u002Fagent-project\", \"skill-version\": \"1.0.0\", \"skill-contributors\": \"Clayton Young (Superior Byte Works, LLC \u002F @borealBytes; Author and originator); K-Dense Team (K-Dense Inc.; Integration target and community feedback)\"}\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), K-Dense Discord, 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 scientific-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","# 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), K-Dense Discord, 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 scientific-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",{"name":5,"license":15,"metadata":60,"description":7,"allowed-tools":66},{"version":61,"skill-author":62,"skill-source":63,"skill-version":64,"skill-contributors":65},"1.1","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); K-Dense Team (K-Dense Inc.; Integration target and community feedback)","Read Write Edit Bash","main","4aa39efd1cdab0b4657ecee16c92a92011a5b10f","scientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing","https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub","https:\u002F\u002Fgithub.com\u002Ffadrienne","2026-10-28 00:43:09",{"source":8,"skillName":5,"commands":74,"prompt":84,"zipAvailable":85},[75,78,81],{"tool":76,"command":77},"npx","npx skills add fadrienne\u002FMyGitHub --skill markdown-mermaid-writing",{"tool":79,"command":80},"bunx","bunx skills add fadrienne\u002FMyGitHub --skill markdown-mermaid-writing",{"tool":82,"command":83},"pnpm","pnpm dlx skills add fadrienne\u002FMyGitHub --skill markdown-mermaid-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002FSKILL.md",true,[87,93,99,103,107,111,115,119,123,127,131,135,139,143,147,151,155,159,163,167,171,175,179,183,187,191,195,199,203,207,211,215,219,223,227,231],{"path":88,"resourceType":89,"resourceTypeDesc":90,"sizeBytes":91,"sourceHtmlUrl":92},"assets\u002Fexamples\u002Fexample-research-report.md","ASSET","资产文件",9010,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Fassets\u002Fexamples\u002Fexample-research-report.md",{"path":94,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":97,"sourceHtmlUrl":98},"references\u002Fdiagrams\u002Farchitecture.md","REFERENCE","参考文档",4369,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Farchitecture.md",{"path":100,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fdiagrams\u002Fblock.md",4825,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fblock.md",{"path":104,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fdiagrams\u002Fc4.md",6201,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fc4.md",{"path":108,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fdiagrams\u002Fclass.md",8521,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fclass.md",{"path":112,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fdiagrams\u002Fcomplex_examples.md",17079,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fcomplex_examples.md",{"path":116,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fdiagrams\u002Fer.md",7601,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fer.md",{"path":120,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fdiagrams\u002Fflowchart.md",6961,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fflowchart.md",{"path":124,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fdiagrams\u002Fgantt.md",5851,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fgantt.md",{"path":128,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fdiagrams\u002Fgit_graph.md",2009,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fgit_graph.md",{"path":132,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fdiagrams\u002Fkanban.md",3544,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fkanban.md",{"path":136,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Fdiagrams\u002Fmindmap.md",2232,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fmindmap.md",{"path":140,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Fdiagrams\u002Fpacket.md",1721,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fpacket.md",{"path":144,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":145,"sourceHtmlUrl":146},"references\u002Fdiagrams\u002Fpie.md",1560,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fpie.md",{"path":148,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":149,"sourceHtmlUrl":150},"references\u002Fdiagrams\u002Fquadrant.md",2163,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fquadrant.md",{"path":152,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":153,"sourceHtmlUrl":154},"references\u002Fdiagrams\u002Fradar.md",2176,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fradar.md",{"path":156,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":157,"sourceHtmlUrl":158},"references\u002Fdiagrams\u002Frequirement.md",2463,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Frequirement.md",{"path":160,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":161,"sourceHtmlUrl":162},"references\u002Fdiagrams\u002Fsankey.md",2143,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fsankey.md",{"path":164,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":165,"sourceHtmlUrl":166},"references\u002Fdiagrams\u002Fsequence.md",5510,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fsequence.md",{"path":168,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":169,"sourceHtmlUrl":170},"references\u002Fdiagrams\u002Fstate.md",5464,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fstate.md",{"path":172,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":173,"sourceHtmlUrl":174},"references\u002Fdiagrams\u002Ftimeline.md",4181,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Ftimeline.md",{"path":176,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":177,"sourceHtmlUrl":178},"references\u002Fdiagrams\u002Ftreemap.md",2039,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Ftreemap.md",{"path":180,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":181,"sourceHtmlUrl":182},"references\u002Fdiagrams\u002Fuser_journey.md",5049,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fuser_journey.md",{"path":184,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":185,"sourceHtmlUrl":186},"references\u002Fdiagrams\u002Fxy_chart.md",1887,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fxy_chart.md",{"path":188,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":189,"sourceHtmlUrl":190},"references\u002Fdiagrams\u002Fzenuml.md",2285,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fzenuml.md",{"path":192,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":193,"sourceHtmlUrl":194},"references\u002Fmarkdown_style_guide.md",35114,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fmarkdown_style_guide.md",{"path":196,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":197,"sourceHtmlUrl":198},"references\u002Fmermaid_style_guide.md",26433,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Freferences\u002Fmermaid_style_guide.md",{"path":200,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":201,"sourceHtmlUrl":202},"templates\u002Fdecision_record.md",7169,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fdecision_record.md",{"path":204,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":205,"sourceHtmlUrl":206},"templates\u002Fhow_to_guide.md",7091,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fhow_to_guide.md",{"path":208,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":209,"sourceHtmlUrl":210},"templates\u002Fissue.md",12835,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fissue.md",{"path":212,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":213,"sourceHtmlUrl":214},"templates\u002Fkanban.md",11403,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fkanban.md",{"path":216,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":217,"sourceHtmlUrl":218},"templates\u002Fpresentation.md",8068,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fpresentation.md",{"path":220,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":221,"sourceHtmlUrl":222},"templates\u002Fproject_documentation.md",11489,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fproject_documentation.md",{"path":224,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":225,"sourceHtmlUrl":226},"templates\u002Fpull_request.md",12903,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fpull_request.md",{"path":228,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":229,"sourceHtmlUrl":230},"templates\u002Fresearch_paper.md",10157,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fresearch_paper.md",{"path":232,"resourceType":95,"resourceTypeDesc":96,"sizeBytes":233,"sourceHtmlUrl":234},"templates\u002Fstatus_report.md",7185,"https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fmarkdown-mermaid-writing\u002Ftemplates\u002Fstatus_report.md",[236,262,289,314,340,367],{"skillNo":237,"name":238,"nameZh":6,"description":239,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":240,"licenseFileUrl":6,"sourceHtmlUrl":241,"categories":242,"keywords":244,"publishedAt":55},"01M7167B28PK20HP7R7ZED2DY0","statistical-power","Sample size calculation, power analysis, and effect size conversion for scientific studies. Use BEFORE data collection (a priori) to determine required N, or after (post-hoc) to compute achieved power. Covers parametric tests (t-test, ANOVA, chi-square, proportions, correlation, regression), simulation-based power for complex\u002Fclustered\u002Fnested designs, and power curves. Use this skill when someone asks 'how many samples do I need', 'what is my power', 'what effect size can I detect', or any variant. Pairs with \u002Fexperimental-design (choose design first, then compute power) and \u002Fstatistical-analysis (analyze data after collection).","MIT","https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fstatistical-power\u002FSKILL.md",[243],{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[245,246,247,248,249,250,251,252,49,48,253,47,254,255,256,257,258,259,260,261],"power","statistical power","effect","scipy","regression","choose","design","uv","collection","calculation","ANOVA","conversion","analyze","t-test","chi-square","simulation","sample",{"skillNo":263,"name":264,"nameZh":6,"description":265,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":240,"licenseFileUrl":6,"sourceHtmlUrl":266,"categories":267,"keywords":271,"publishedAt":55},"01M71677EBCM8EPCE9BZCK8505","statistical-analysis","Guided statistical analysis with test selection and reporting. Use when you need help choosing appropriate tests for your data, assumption checking, power analysis, and APA-formatted results. Best for academic research reporting, test selection guidance. For implementing specific models programmatically use statsmodels.","https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fstatistical-analysis\u002FSKILL.md",[268],{"categoryNo":269,"categoryName":270,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000008","测试与质量",[47,272,245,273,274,275,49,276,277,278,279,280,281,282,283,284,285,286,287,288],"statistical analysis","academic research","implementing","selection","you","reporting","data","for","tests","use","with","test","research","results","statsmodels","models","help",{"skillNo":290,"name":291,"nameZh":6,"description":292,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":240,"licenseFileUrl":6,"sourceHtmlUrl":293,"categories":294,"keywords":298,"publishedAt":55},"01M71673R93XAHFH81DBNVNG7H","scientific-writing","Core skill for the deep research and writing tool. Write scientific manuscripts in full paragraphs (never bullet points). Use two-stage process with (1) section outlines with key points using research-lookup then (2) convert to flowing prose. IMRAD structure, citations (APA\u002FAMA\u002FVancouver), figures\u002Ftables, reporting guidelines (CONSORT\u002FSTROBE\u002FPRISMA), for research papers and journal submissions.","https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fscientific-writing\u002FSKILL.md",[295,296,297],{"categoryNo":24,"categoryName":25,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":30,"categoryName":31,"taxonomyType":32,"taxonomyTypeDesc":33},[38,40,299,300,301,302,303,304,305,306,48,307,308,309,310,311,312,39,277,313],"scientific writing","Citations","deep","deep research","never","papers","journal","false","api","prisma","structure","openrouter","Outlines","core skill","features",{"skillNo":315,"name":316,"nameZh":6,"description":317,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":240,"licenseFileUrl":6,"sourceHtmlUrl":318,"categories":319,"keywords":324,"publishedAt":55},"01M7166ZPKXBF4EBPHVTJPQBB1","scientific-visualization","Meta-skill for publication-ready figures. Use when creating journal submission figures requiring multi-panel layouts, significance annotations, error bars, colorblind-safe palettes, and specific journal formatting (Nature, Science, Cell). Orchestrates matplotlib\u002Fseaborn\u002Fplotly with publication styles. For quick exploration use seaborn or plotly directly.","https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fscientific-visualization\u002FSKILL.md",[320,323],{"categoryNo":321,"categoryName":322,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000013","分析与可视化",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},[52,40,325,326,327,328,329,330,331,305,49,332,333,334,335,336,337,338,279,339],"scientific visualization","error","ready","quick","exploration","meta-skill","Meta","safe","plotly","annotations","formatting","Publication","figures","panel","submission",{"skillNo":341,"name":342,"nameZh":6,"description":343,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":240,"licenseFileUrl":6,"sourceHtmlUrl":344,"categories":345,"keywords":352,"publishedAt":55},"01M7166VXJWQSSC3RQZP60WBGR","research-code","Debug, profile, review, and restructure Python research and analysis code. Use when analysis scripts crash, produce wrong results, run too slowly, or need a correctness review. Covers: reading tracebacks and diagnosing root causes, hypothesis-driven debugging, reviewing code for common statistical\u002Fnumerical errors, profiling data pipelines, improving reproducibility (seeds, environments, determinism), and structuring analysis scripts for sharing. Distinct from \u002Fexploratory-data-analysis (which understands data) and \u002Fstatistical-analysis (which chooses and runs tests) — this skill focuses on the code itself.","https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fresearch-code\u002FSKILL.md",[346,349],{"categoryNo":347,"categoryName":348,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000021","资料检索与研究",{"categoryNo":350,"categoryName":351,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000030","开发工程师",[353,354,284,355,356,357,358,252,359,49,48,47,360,361,362,363,364,365,39,366],"code","research code","which","memory","data-analysis","errors","debugging","common","review","data pipelines","run","scripts","line","write",{"skillNo":368,"name":369,"nameZh":6,"description":370,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":240,"licenseFileUrl":6,"sourceHtmlUrl":371,"categories":372,"keywords":381,"publishedAt":55},"01M716618J5EDTN4RW41JZ4W4Z","hypothesis-generation","Structured hypothesis formulation from observations. Use when you have experimental observations or data and need to formulate testable hypotheses with predictions, propose mechanisms, and design experiments to test them. Follows scientific method framework. For open-ended ideation use scientific-brainstorming; for automated LLM-driven hypothesis testing on datasets use hypogenic.","https:\u002F\u002Fgithub.com\u002Ffadrienne\u002FMyGitHub\u002Fblob\u002Fmain\u002Fscientific-agent-skills\u002Fskills\u002Fhypothesis-generation\u002FSKILL.md",[373,374,377,378],{"categoryNo":269,"categoryName":270,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":375,"categoryName":376,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000015","视觉设计",{"categoryNo":27,"categoryName":28,"taxonomyType":21,"taxonomyTypeDesc":22},{"categoryNo":379,"categoryName":380,"taxonomyType":32,"taxonomyTypeDesc":33},"01JBSEEDCAT000000000000032","设计师",[382,383,384,385,386,251,306,49,387,276,48,307,310,40,388,39,313,366,389,278],"hypothesis generation","generation","hypothesis","testing","open","predictions","hypothesis formulation","edit"]