[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6FHFYCGFKYKFV94HAZKMMW9":3,"skill-same:01M6FHFYCGFKYKFV94HAZKMMW9":243},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":33,"publishedAt":55,"linkOnly":56,"markdownContent":57,"markdownBody":58,"frontMatter":59,"refName":70,"commitSha":71,"skillDirectory":72,"forksCount":73,"repositoryHtmlUrl":74,"repositoryHomepageUrl":6,"ownerHtmlUrl":75,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":76,"install":77,"resources":90},"01M6FHFYCGFKYKFV94HAZKMMW9","markdown-mermaid-writing",null,"Writes scientific Markdown documentation and Mermaid diagrams for workflows, relationships, timelines, and schemas. Provides syntax references, document templates, accessibility guidance, and version-aware rendering checks. Use when a user requests Markdown, Mermaid, or a text-based structural diagram; quantitative scientific figures require suitable plotting tools.","boisenoise\u002Fskills-collections","boisenoise","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F193180?v=4","01M6CDBDQK6BDN55ZMA6B6PKBM","01M6CDBDVSJ3JPTBYN26FZ7TZK",12,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002FSKILL.md",[17,22,25,28],{"categoryNo":18,"categoryName":19,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000002","文档处理","SCENARIO","使用场景",{"categoryNo":23,"categoryName":24,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000018","写作与文案",{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},"01JBSEEDCAT000000000000023","Skill与智能体开发",{"categoryNo":29,"categoryName":30,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000036","内容创作者","PROFESSION","适用职业",[34,35,36,37,38,39,40,41,42,43,44,45,46,47,48,49,50,51,52,53,54],"writing","mermaid","markdown mermaid writing","markdown","when","structural","project","local","community","references","diagrams","text","access","Bash","team","credentials","browser","diagram","documentation","workflows","cli","2026-11-10 10:12:30",false,"---\nname: markdown-mermaid-writing\ndescription: Writes scientific Markdown documentation and Mermaid diagrams for workflows, relationships, timelines, and schemas. Provides syntax references, document templates, accessibility guidance, and version-aware rendering checks. Use when a user requests Markdown, Mermaid, or a text-based structural diagram; quantitative scientific figures require suitable plotting tools.\nallowed-tools: Read Write Edit Bash\nlicense: Apache-2.0\ncompatibility: Markdown authoring needs no runtime. Local rendering targets Mermaid and Mermaid CLI 12.0.0, Node.js 22.13+ and a supported Chromium browser. Package or CDN installation needs network access; no credentials required.\nmetadata:\n  version: \"1.3\"\n  last-reviewed: \"2026-10-01\"\n  mermaid-tested: \"12.0.0\"\n  mermaid-cli-tested: \"12.0.0\"\n  skill-author: Clayton Young \u002F Superior Byte Works, LLC (@borealBytes)\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); K-Dense Team (K-Dense Inc.; Integration target and community feedback)\n---\n\n# Markdown and Mermaid Writing\n\n## Overview\n\nThis skill provides an optional house style for **Markdown documentation with Mermaid\nstructural diagrams**. Follow the requested output format, existing repository conventions,\nand journal requirements first. This skill does not replace scientific analysis or plotting.\n\nA relationship expressed as Mermaid inside a `.md` file is editable text that diffs\ncleanly in git. A compatible host renders it without a separate user build step.\nIt renders where the host has Mermaid support; plain Markdown viewers may show only code,\nand platforms\u002Fextensions ship different Mermaid versions. It uses\na compact source representation, though token use depends on the diagram. Exporting\nSVG\u002FPNG requires a renderer; retain the diagram source alongside exported figures.\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- Writing a requested Markdown report, README, methods overview, or research note\n- Diagramming a workflow, data pipeline, schema, state machine, or conceptual relationship\n- Maintaining editable Mermaid sources and their rendered SVG\u002FPNG exports\n\nUse scientific plotting tools directly for measured data, uncertainty, statistical graphics,\nexact geometry, or publication figures that Mermaid cannot faithfully represent. Mermaid\nis not a required precursor to a quantitative chart or an existing SVG\u002Fcode-native asset.\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 | ✅ text source | Plotting code\u002FSVG can also be text |\n| Editable source | ✅ | Plotting scripts and vector sources are editable |\n| Compact relationship notation | Often | Depends on representation |\n| Native preview | Host\u002Fversion dependent | Viewer\u002Fformat dependent |\n| Parseable by AI without vision | ✅ | ❌ |\n| Works in destination | Check Mermaid support and version | Check image format support |\n| Accessible (screen readers) | Check SVG metadata and text alternative | Provide alt text\u002Fdata table |\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: Markdown holds the structural diagram source. Quantitative charts come from data and plotting code; optional illustrations require a separate factual review.\n\n    p1[\"? Phase 1\u003Cbr\u002F>Mermaid in Markdown\u003Cbr\u002F>(structural source)\"]\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    data[\"Data and plotting code\"] --> 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\nRetain Mermaid for structural diagrams and data\u002Fcode for quantitative charts. An AI illustration\nis not a quantitative conversion; verify every label and relationship against its sources.\n\n### What Mermaid can express\n\nThis skill includes 23 diagram-type guides plus a composition guide. Mermaid supports\nadditional types; these references are a curated subset, not an exhaustive version catalogue:\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\nFor this Markdown workflow, read `references\u002Fmarkdown_style_guide.md`. Treat emoji,\nheading counts, and horizontal rules as house style rather than Markdown syntax requirements.\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- **Support factual claims** — use verified sources and the requested citation format\n- **Bold sparingly** — max 2-3 bold terms per paragraph, never full sentences\n- **Optional horizontal rules** after `\u003C\u002Fdetails>` when they improve separation\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\nAdd accessibility metadata for types that emit it in the chosen renderer:\n\n```\naccTitle: Short Name 3-8 Words\naccDescr: One or two sentences explaining what this diagram shows.\n```\n\n- Prefer host themes; `%%{init}` directives are deprecated in favor of YAML configuration\n- Prefer reusable `classDef` where supported; style syntax is diagram-specific\n- **One emoji per node max** — at the start of the label\n- Use descriptive IDs with the type's syntax: `snake_case` works for flowcharts; ER\u002Fclass\u002Fstate conventions differ\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\nRender in the **actual destination** before delivery. Check its Mermaid version and\nplugin requirements before choosing newer diagram types; [GitHub documents an `info`\ndiagram for this check](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fget-started\u002Fwriting-on-github\u002Fworking-with-advanced-formatting\u002Fcreating-diagrams).\nA successful latest-version local preview does not establish GitHub or another host\nwill render it. Where Mermaid is unsupported, supply a rendered SVG\u002FPNG with a text\ndescription alongside the retained `.md` source.\n\n### Step 5: Retain source and verification\n\nKeep the `.md` source, rendered deliverable, and tested renderer version together.\nFollow the project's version-control workflow; this skill does not itself authorize a commit or publication.\nFor CLI export, embedding, and the tested accessibility matrix, read\n[Current rendering and validation](references\u002Fcurrent-rendering.md).\n\n---\n\n## ⚠️ Common pitfalls\n\n### Radar chart syntax (`radar-beta`)\n\n**WRONG (shown as text so it does not break the document renderer):**\n```text\nradar\ntitle Example\nx-axis [\"A\", \"B\", \"C\"]\n\"Series\" : [1, 2, 3]\n```\n\n**CORRECT:**\n```mermaid\nradar-beta\naccTitle: Example Radar Scores\naccDescr: Illustrative values of one, two, and three on a shared zero-to-three scale.\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- Mermaid 12.0.0 radar emits `accTitle`\u002F`accDescr`; check older hosts and retain a visible description\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 on a stated, common score scale. See the data table for exact values._\n\n```text\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\nFor a manuscript that uses Mermaid structural figures, this skill handles diagram syntax.\nFollow the manuscript's required figure formats and scientific visualization conventions.\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 plotting or schematic tools where appropriate to the scientific content\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 a document using this skill, check:\n\n- [ ] Does the document use a template? If so, did I start from the right one?\n- [ ] Is each diagram in an appropriate format, with working accessibility metadata or a text alternative?\n- [ ] Is configuration supported by the destination and tested in light\u002Fdark themes?\n- [ ] Do citations support external claims, and are synthetic values labeled?\n- [ ] One H1, emoji on H2 only?\n- [ ] Does the final Markdown\u002FHTML structure render correctly?\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` | see file | Headings, formatting, citations, tables, Mermaid integration, templates, quality checklist |\n| Mermaid Style Guide | `references\u002Fmermaid_style_guide.md` | see file | Accessibility, emoji set, color classes, theme neutrality, type selection, complexity tiers |\n| Current Rendering | `references\u002Fcurrent-rendering.md` | see file | Mermaid 12 changes, CLI export, browser APIs, tested accessibility matrix, scientific checks |\n\n### Diagram guides (23 types plus composition)\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 synthetic quality-control report with explicitly invented data, an auditable count table, a structural flowchart, a bar chart, and a chronology. It makes no experimental or software API claims.\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 provides an optional house style for **Markdown documentation with Mermaid\nstructural diagrams**. Follow the requested output format, existing repository conventions,\nand journal requirements first. This skill does not replace scientific analysis or plotting.\n\nA relationship expressed as Mermaid inside a `.md` file is editable text that diffs\ncleanly in git. A compatible host renders it without a separate user build step.\nIt renders where the host has Mermaid support; plain Markdown viewers may show only code,\nand platforms\u002Fextensions ship different Mermaid versions. It uses\na compact source representation, though token use depends on the diagram. Exporting\nSVG\u002FPNG requires a renderer; retain the diagram source alongside exported figures.\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- Writing a requested Markdown report, README, methods overview, or research note\n- Diagramming a workflow, data pipeline, schema, state machine, or conceptual relationship\n- Maintaining editable Mermaid sources and their rendered SVG\u002FPNG exports\n\nUse scientific plotting tools directly for measured data, uncertainty, statistical graphics,\nexact geometry, or publication figures that Mermaid cannot faithfully represent. Mermaid\nis not a required precursor to a quantitative chart or an existing SVG\u002Fcode-native asset.\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 | ✅ text source | Plotting code\u002FSVG can also be text |\n| Editable source | ✅ | Plotting scripts and vector sources are editable |\n| Compact relationship notation | Often | Depends on representation |\n| Native preview | Host\u002Fversion dependent | Viewer\u002Fformat dependent |\n| Parseable by AI without vision | ✅ | ❌ |\n| Works in destination | Check Mermaid support and version | Check image format support |\n| Accessible (screen readers) | Check SVG metadata and text alternative | Provide alt text\u002Fdata table |\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: Markdown holds the structural diagram source. Quantitative charts come from data and plotting code; optional illustrations require a separate factual review.\n\n    p1[\"? Phase 1\u003Cbr\u002F>Mermaid in Markdown\u003Cbr\u002F>(structural source)\"]\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    data[\"Data and plotting code\"] --> 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\nRetain Mermaid for structural diagrams and data\u002Fcode for quantitative charts. An AI illustration\nis not a quantitative conversion; verify every label and relationship against its sources.\n\n### What Mermaid can express\n\nThis skill includes 23 diagram-type guides plus a composition guide. Mermaid supports\nadditional types; these references are a curated subset, not an exhaustive version catalogue:\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\nFor this Markdown workflow, read `references\u002Fmarkdown_style_guide.md`. Treat emoji,\nheading counts, and horizontal rules as house style rather than Markdown syntax requirements.\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- **Support factual claims** — use verified sources and the requested citation format\n- **Bold sparingly** — max 2-3 bold terms per paragraph, never full sentences\n- **Optional horizontal rules** after `\u003C\u002Fdetails>` when they improve separation\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\nAdd accessibility metadata for types that emit it in the chosen renderer:\n\n```\naccTitle: Short Name 3-8 Words\naccDescr: One or two sentences explaining what this diagram shows.\n```\n\n- Prefer host themes; `%%{init}` directives are deprecated in favor of YAML configuration\n- Prefer reusable `classDef` where supported; style syntax is diagram-specific\n- **One emoji per node max** — at the start of the label\n- Use descriptive IDs with the type's syntax: `snake_case` works for flowcharts; ER\u002Fclass\u002Fstate conventions differ\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\nRender in the **actual destination** before delivery. Check its Mermaid version and\nplugin requirements before choosing newer diagram types; [GitHub documents an `info`\ndiagram for this check](https:\u002F\u002Fdocs.github.com\u002Fen\u002Fget-started\u002Fwriting-on-github\u002Fworking-with-advanced-formatting\u002Fcreating-diagrams).\nA successful latest-version local preview does not establish GitHub or another host\nwill render it. Where Mermaid is unsupported, supply a rendered SVG\u002FPNG with a text\ndescription alongside the retained `.md` source.\n\n### Step 5: Retain source and verification\n\nKeep the `.md` source, rendered deliverable, and tested renderer version together.\nFollow the project's version-control workflow; this skill does not itself authorize a commit or publication.\nFor CLI export, embedding, and the tested accessibility matrix, read\n[Current rendering and validation](references\u002Fcurrent-rendering.md).\n\n---\n\n## ⚠️ Common pitfalls\n\n### Radar chart syntax (`radar-beta`)\n\n**WRONG (shown as text so it does not break the document renderer):**\n```text\nradar\ntitle Example\nx-axis [\"A\", \"B\", \"C\"]\n\"Series\" : [1, 2, 3]\n```\n\n**CORRECT:**\n```mermaid\nradar-beta\naccTitle: Example Radar Scores\naccDescr: Illustrative values of one, two, and three on a shared zero-to-three scale.\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- Mermaid 12.0.0 radar emits `accTitle`\u002F`accDescr`; check older hosts and retain a visible description\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 on a stated, common score scale. See the data table for exact values._\n\n```text\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\nFor a manuscript that uses Mermaid structural figures, this skill handles diagram syntax.\nFollow the manuscript's required figure formats and scientific visualization conventions.\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 plotting or schematic tools where appropriate to the scientific content\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 a document using this skill, check:\n\n- [ ] Does the document use a template? If so, did I start from the right one?\n- [ ] Is each diagram in an appropriate format, with working accessibility metadata or a text alternative?\n- [ ] Is configuration supported by the destination and tested in light\u002Fdark themes?\n- [ ] Do citations support external claims, and are synthetic values labeled?\n- [ ] One H1, emoji on H2 only?\n- [ ] Does the final Markdown\u002FHTML structure render correctly?\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` | see file | Headings, formatting, citations, tables, Mermaid integration, templates, quality checklist |\n| Mermaid Style Guide | `references\u002Fmermaid_style_guide.md` | see file | Accessibility, emoji set, color classes, theme neutrality, type selection, complexity tiers |\n| Current Rendering | `references\u002Fcurrent-rendering.md` | see file | Mermaid 12 changes, CLI export, browser APIs, tested accessibility matrix, scientific checks |\n\n### Diagram guides (23 types plus composition)\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 synthetic quality-control report with explicitly invented data, an auditable count table, a structural flowchart, a bar chart, and a chronology. It makes no experimental or software API claims.\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":14,"metadata":60,"description":7,"allowed-tools":68,"compatibility":69},{"version":61,"skill-author":62,"skill-source":63,"last-reviewed":64,"skill-version":65,"mermaid-tested":66,"mermaid-cli-tested":66,"skill-contributors":67},"1.3","Clayton Young \u002F Superior Byte Works, LLC (@borealBytes)","https:\u002F\u002Fgithub.com\u002FSuperiorByteWorks-LLC\u002Fagent-project","2026-10-01","1.0.0","12.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","Markdown authoring needs no runtime. Local rendering targets Mermaid and Mermaid CLI 12.0.0, Node.js 22.13+ and a supported Chromium browser. Package or CDN installation needs network access; no credentials required.","main","7bf2279c8a65758319526a721d5c4b75683aec9c","skills\u002Fkdense-markdown-mermaid-writing",3,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections","https:\u002F\u002Fgithub.com\u002Fboisenoise","2026-11-13 14:20:47",{"source":8,"skillName":5,"commands":78,"prompt":88,"zipAvailable":89},[79,82,85],{"tool":80,"command":81},"npx","npx skills add boisenoise\u002Fskills-collections --skill markdown-mermaid-writing",{"tool":83,"command":84},"bunx","bunx skills add boisenoise\u002Fskills-collections --skill markdown-mermaid-writing",{"tool":86,"command":87},"pnpm","pnpm dlx skills add boisenoise\u002Fskills-collections --skill markdown-mermaid-writing","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002FSKILL.md",true,[91,97,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,235,239],{"path":92,"resourceType":93,"resourceTypeDesc":94,"sizeBytes":95,"sourceHtmlUrl":96},"assets\u002Fexamples\u002Fexample-research-report.md","ASSET","资产文件",3509,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Fassets\u002Fexamples\u002Fexample-research-report.md",{"path":98,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":101,"sourceHtmlUrl":102},"references\u002Fcurrent-rendering.md","REFERENCE","参考文档",7744,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fcurrent-rendering.md",{"path":104,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":105,"sourceHtmlUrl":106},"references\u002Fdiagrams\u002Farchitecture.md",5092,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Farchitecture.md",{"path":108,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":109,"sourceHtmlUrl":110},"references\u002Fdiagrams\u002Fblock.md",5138,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fblock.md",{"path":112,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":113,"sourceHtmlUrl":114},"references\u002Fdiagrams\u002Fc4.md",6815,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fc4.md",{"path":116,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":117,"sourceHtmlUrl":118},"references\u002Fdiagrams\u002Fclass.md",8840,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fclass.md",{"path":120,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":121,"sourceHtmlUrl":122},"references\u002Fdiagrams\u002Fcomplex_examples.md",17248,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fcomplex_examples.md",{"path":124,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":125,"sourceHtmlUrl":126},"references\u002Fdiagrams\u002Fer.md",8237,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fer.md",{"path":128,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":129,"sourceHtmlUrl":130},"references\u002Fdiagrams\u002Fflowchart.md",7203,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fflowchart.md",{"path":132,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":133,"sourceHtmlUrl":134},"references\u002Fdiagrams\u002Fgantt.md",6101,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fgantt.md",{"path":136,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":137,"sourceHtmlUrl":138},"references\u002Fdiagrams\u002Fgit_graph.md",2294,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fgit_graph.md",{"path":140,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":141,"sourceHtmlUrl":142},"references\u002Fdiagrams\u002Fkanban.md",4047,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fkanban.md",{"path":144,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":145,"sourceHtmlUrl":146},"references\u002Fdiagrams\u002Fmindmap.md",2516,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fmindmap.md",{"path":148,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":149,"sourceHtmlUrl":150},"references\u002Fdiagrams\u002Fpacket.md",2485,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fpacket.md",{"path":152,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":153,"sourceHtmlUrl":154},"references\u002Fdiagrams\u002Fpie.md",1961,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fpie.md",{"path":156,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":157,"sourceHtmlUrl":158},"references\u002Fdiagrams\u002Fquadrant.md",2702,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fquadrant.md",{"path":160,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":161,"sourceHtmlUrl":162},"references\u002Fdiagrams\u002Fradar.md",2851,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fradar.md",{"path":164,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":165,"sourceHtmlUrl":166},"references\u002Fdiagrams\u002Frequirement.md",3121,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Frequirement.md",{"path":168,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":169,"sourceHtmlUrl":170},"references\u002Fdiagrams\u002Fsankey.md",2691,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fsankey.md",{"path":172,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":173,"sourceHtmlUrl":174},"references\u002Fdiagrams\u002Fsequence.md",6052,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fsequence.md",{"path":176,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":177,"sourceHtmlUrl":178},"references\u002Fdiagrams\u002Fstate.md",5822,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fstate.md",{"path":180,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":181,"sourceHtmlUrl":182},"references\u002Fdiagrams\u002Ftimeline.md",4583,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Ftimeline.md",{"path":184,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":185,"sourceHtmlUrl":186},"references\u002Fdiagrams\u002Ftreemap.md",2652,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Ftreemap.md",{"path":188,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":189,"sourceHtmlUrl":190},"references\u002Fdiagrams\u002Fuser_journey.md",5302,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fuser_journey.md",{"path":192,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":193,"sourceHtmlUrl":194},"references\u002Fdiagrams\u002Fxy_chart.md",2655,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fxy_chart.md",{"path":196,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":197,"sourceHtmlUrl":198},"references\u002Fdiagrams\u002Fzenuml.md",2568,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fdiagrams\u002Fzenuml.md",{"path":200,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":201,"sourceHtmlUrl":202},"references\u002Fmarkdown_style_guide.md",33195,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fmarkdown_style_guide.md",{"path":204,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":205,"sourceHtmlUrl":206},"references\u002Fmermaid_style_guide.md",27258,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Freferences\u002Fmermaid_style_guide.md",{"path":208,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":209,"sourceHtmlUrl":210},"templates\u002Fdecision_record.md",7323,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fdecision_record.md",{"path":212,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":213,"sourceHtmlUrl":214},"templates\u002Fhow_to_guide.md",7295,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fhow_to_guide.md",{"path":216,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":217,"sourceHtmlUrl":218},"templates\u002Fissue.md",11915,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fissue.md",{"path":220,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":221,"sourceHtmlUrl":222},"templates\u002Fkanban.md",10826,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fkanban.md",{"path":224,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":225,"sourceHtmlUrl":226},"templates\u002Fpresentation.md",8303,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fpresentation.md",{"path":228,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":229,"sourceHtmlUrl":230},"templates\u002Fproject_documentation.md",11795,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fproject_documentation.md",{"path":232,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":233,"sourceHtmlUrl":234},"templates\u002Fpull_request.md",12131,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fpull_request.md",{"path":236,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":237,"sourceHtmlUrl":238},"templates\u002Fresearch_paper.md",10361,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fresearch_paper.md",{"path":240,"resourceType":99,"resourceTypeDesc":100,"sizeBytes":241,"sourceHtmlUrl":242},"templates\u002Fstatus_report.md",7336,"https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fkdense-markdown-mermaid-writing\u002Ftemplates\u002Fstatus_report.md",[244,270,291,315,334,357],{"skillNo":245,"name":246,"nameZh":6,"description":247,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":248,"sourceHtmlUrl":249,"categories":250,"keywords":251,"publishedAt":55},"01M6WNH92BHVFXHGPDZCPJ0AG0","web-access","Use Treg for public web or platform data only when existing search, browser and connected tools cannot cover the task, with explicit cost and data boundaries.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-web-access\u002FSKILL.md",[],[252,46,253,254,255,50,256,257,258,259,260,261,262,263,264,265,266,267,268,38,269],"web","web access","official","development","search","data","Tools","read","fetch","only","youtube","free tools","platform","critical","free","cover","normal","2026",{"skillNo":271,"name":272,"nameZh":6,"description":273,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":274,"sourceHtmlUrl":275,"categories":276,"keywords":278,"publishedAt":55},"01M6WNF9XAYAB2CZDDJBAKNM93","treg","Use the Treg CLI or MCP catalog to discover, price and call authorized external tools with team-scoped credentials and a user-approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-treg\u002FSKILL.md",[277],{"categoryNo":26,"categoryName":27,"taxonomyType":20,"taxonomyTypeDesc":21},[272,279,54,280,254,255,281,258,282,49,48,283,284,285,286,265,287,288,289,290,269],"MCP","github","license","Budget","catalog","use","call","discover","external tools","with","scoped","blob",{"skillNo":292,"name":293,"nameZh":6,"description":294,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":295,"sourceHtmlUrl":296,"categories":297,"keywords":301,"publishedAt":55},"01M6WN93MEAZ4E41DYAHJRPHQT","recruit","Turn a job description into an evidence-linked candidate shortlist through Treg, with job-related ranking and optional authorized business contact enrichment.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-recruit\u002FSKILL.md",[298],{"categoryNo":299,"categoryName":300,"taxonomyType":31,"taxonomyTypeDesc":32},"01JBSEEDCAT000000000000038","人力资源",[293,280,254,281,302,303,304,305,306,307,265,308,309,310,288,311,312,313,314,290,272,269],"https","email","enrichment","business","evidence","phone","ranking","post","job description","for","person","candidate","reason",{"skillNo":316,"name":317,"nameZh":6,"description":318,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":319,"sourceHtmlUrl":320,"categories":321,"keywords":322,"publishedAt":55},"01M6WN8R5RXSMHM9B4D9FAFX42","rea-growth","Analyze a company’s public growth and content through Treg, distinguish observations from hypotheses, and produce an evidence-linked playbook within an approved budget.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-rea-growth\u002FSKILL.md",[],[323,324,325,280,254,281,326,327,302,328,282,329,330,331,306,265,332,333,290,272,269],"growth","rea","rea growth","produce","content","playbook","marketing","analyze","public","observations","company",{"skillNo":335,"name":336,"nameZh":6,"description":337,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":338,"sourceHtmlUrl":339,"categories":340,"keywords":341,"publishedAt":55},"01M6WN2EVE3RQRGWAKBT4S7YT2","make-ugc","Create original AI UGC-style product videos through Treg: research hooks, approve a licensed presenter and voice, generate clips, add captions and report costs.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-make-ugc\u002FSKILL.md",[],[342,343,280,344,254,345,281,346,347,348,349,350,265,351,352,353,354,355,356,290],"make","make ugc","research","create","Video","Captions","ads","short","hooks","head","style","niche","trending","talking-head","approve",{"skillNo":358,"name":359,"nameZh":6,"description":360,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":6,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":361,"sourceHtmlUrl":362,"categories":363,"keywords":364,"publishedAt":55},"01M6WN10ARAA63Y8K1YNGXJ2RM","lead-signals","Find and qualify public buying signals through Treg, rank fitting business accounts and optionally enrich authorized business contact information.","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fboisenoise\u002Fskills-collections\u002Fblob\u002Fmain\u002Fskills\u002Fantigravity-lead-signals\u002FSKILL.md",[],[365,366,367,280,254,281,368,369,305,370,371,265,372,373,374,375,376,377,378,290],"signals","lead","lead signals","how","find","ready","as","how to","qualify","people","information","enrich","changes","funding"]