Markdown Mermaid Writing

K-DenseCommunityCreated by Clayton Young / Superior Byte Works, LLC (@borealBytes)Distributed by K-Dense

Skill
Tool integration
Documents and content
Apache-2.0
Low risk

From the author

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.

— the description by Clayton Young / Superior Byte Works, LLC (@borealBytes)

AutoGineer summary

Written by AutoGineer from the skill’s own files, not by the author

This skill provides a structured approach to creating technical and scientific documentation using Markdown and Mermaid. It emphasizes the use of text-based diagrams for structural clarity, ensuring that workflows, architectures, and data models remain editable, version-controlled, and accessible. The skill includes templates for various document types and comprehensive guides for 23 different Mermaid diagram types, ensuring consistent formatting and adherence to accessibility standards.

What it does

Writes scientific Markdown reports, READMEs, and research documentation.
Creates structural Mermaid diagrams for workflows, timelines, schemas, and architectures.
Provides templates for common technical documents like ADRs, pull requests, and status reports.
Offers style guides for consistent Markdown formatting and Mermaid diagram design.
Includes accessibility guidance for diagrams using titles and descriptions.
Supports version-aware rendering checks for Mermaid diagrams.

When to use it

When you need to document complex workflows, system architectures, or data relationships.
When you want to maintain diagrams as editable text within a Git repository.
When creating technical reports that require a consistent, professional house style.
When you need to ensure your diagrams are accessible and renderable across different platforms.

Advantages

Diagrams are stored as plain text, making them easily diffable and version-controlled.
Reduces token usage compared to long-form text descriptions of relationships.
Promotes a consistent documentation style across projects.
Supports accessibility through standardized metadata.
Facilitates easy updates to diagrams without needing specialized image editing software.

Usage examples

“Create a Mermaid flowchart for a data processing pipeline.”: Generates a Markdown-formatted document containing a Mermaid flowchart block that maps the data pipeline steps, following the established style guide.
“Draft an Architecture Decision Record (ADR) for a new database choice.”: Produces a structured Markdown document using the ADR template, including placeholders for context, decision, and consequences.
“How do I create a sequence diagram for an API interaction?”: Provides the specific Mermaid sequence diagram syntax, a copy-paste template, and tips on how to style it according to the project's guidelines.
“Check if my Mermaid diagram is accessible.”: Reviews the diagram code for required accessibility metadata (accTitle/accDescr) and suggests improvements based on the Mermaid style guide.

Install

Download the skill as a ZIP:
https://autogineer.com/agent-skills/k-dense-ai/markdown-mermaid-writing/download

Unzip it into the cross-client skills folder of your project:

mkdir -p .agents/skills && unzip markdown-mermaid-writing.zip -d .agents/skills

Documentation by Clayton Young / Superior Byte Works, LLC (@borealBytes)

Markdown and Mermaid Writing

Overview

This skill provides an optional house style for Markdown documentation with Mermaid structural diagrams. Follow the requested output format, existing repository conventions, and journal requirements first. This skill does not replace scientific analysis or plotting.

A relationship expressed as Mermaid inside a .md file is editable text that diffs cleanly in git. A compatible host renders it without a separate user build step. It renders where the host has Mermaid support; plain Markdown viewers may show only code, and platforms/extensions ship different Mermaid versions. It uses a compact source representation, though token use depends on the diagram. Exporting SVG/PNG requires a renderer; retain the diagram source alongside exported figures.

"The more you get your reports and files in .md in just regular text, which mermaid is as well as being a simple 'script language'. This just helps with any downstream rendering and especially AI generated images (using mermaid instead of just long form text to describe relationships < tokens). Additionally mermaid can render along with markdown for easy use almost anywhere by humans or AI."
— Clayton Young (@borealBytes), K-Dense Discord, 2026-02-19

When to Use This Skill

Use this skill when:

Writing a requested Markdown report, README, methods overview, or research note
Diagramming a workflow, data pipeline, schema, state machine, or conceptual relationship
Maintaining editable Mermaid sources and their rendered SVG/PNG exports

Use scientific plotting tools directly for measured data, uncertainty, statistical graphics, exact geometry, or publication figures that Mermaid cannot faithfully represent. Mermaid is not a required precursor to a quantitative chart or an existing SVG/code-native asset.

🎨 The Source Format Philosophy

Why text-based diagrams win

What matters	Mermaid in Markdown	Python / AI Image
Git diff readable	✅ text source	Plotting code/SVG can also be text
Editable source	✅	Plotting scripts and vector sources are editable
Compact relationship notation	Often	Depends on representation
Native preview	Host/version dependent	Viewer/format dependent
Parseable by AI without vision	✅	❌
Works in destination	Check Mermaid support and version	Check image format support
Accessible (screen readers)	Check SVG metadata and text alternative	Provide alt text/data table
Convertible to image later	✅ anytime	— already image

The three-phase workflow

flowchart LR
    accTitle: Three-Phase Documentation Workflow
    accDescr: Markdown holds the structural diagram source. Quantitative charts come from data and plotting code; optional illustrations require a separate factual review.

    p1["📄 Phase 1<br/>Mermaid in Markdown<br/>(structural source)"]
    p2["🐍 Phase 2<br/>Python Generated<br/>(optional — data charts)"]
    p3["🎨 Phase 3<br/>AI Generated Visuals<br/>(optional — polish)"]
    out["📊 Final Deliverable"]

    p1 --> out
    data["Data and plotting code"] --> p2
    p1 -.->|"when needed"| p3
    p2 --> out
    p3 --> out

    classDef required fill:#dbeafe,stroke:#2563eb,stroke-width:2px,color:#1e3a5f
    classDef optional fill:#fef9c3,stroke:#ca8a04,stroke-width:2px,color:#713f12
    classDef output fill:#dcfce7,stroke:#16a34a,stroke-width:2px,color:#14532d

    class p1 required
    class p2,p3 optional
    class out output

Retain Mermaid for structural diagrams and data/code for quantitative charts. An AI illustration is not a quantitative conversion; verify every label and relationship against its sources.

What Mermaid can express

This skill includes 23 diagram-type guides plus a composition guide. Mermaid supports additional types; these references are a curated subset, not an exhaustive version catalogue:

Use case	Diagram type	File
Experimental workflow / decision logic	Flowchart	`references/diagrams/flowchart.md`
Service interactions / API calls / messaging	Sequence	`references/diagrams/sequence.md`
Data model / schema	ER diagram	`references/diagrams/er.md`
State machine / lifecycle	State	`references/diagrams/state.md`
Project timeline / roadmap	Gantt	`references/diagrams/gantt.md`
Proportions / composition	Pie	`references/diagrams/pie.md`
System architecture (zoom levels)	C4	`references/diagrams/c4.md`
Concept hierarchy / brainstorm	Mindmap	`references/diagrams/mindmap.md`
Chronological events / history	Timeline	`references/diagrams/timeline.md`
Class hierarchy / type relationships	Class	`references/diagrams/class.md`
User journey / satisfaction map	User Journey	`references/diagrams/user_journey.md`
Two-axis comparison / prioritization	Quadrant	`references/diagrams/quadrant.md`
Requirements traceability	Requirement	`references/diagrams/requirement.md`
Flow magnitude / resource distribution	Sankey	`references/diagrams/sankey.md`
Numeric trends / bar + line charts	XY Chart	`references/diagrams/xy_chart.md`
Component layout / spatial arrangement	Block	`references/diagrams/block.md`
Work item status / task columns	Kanban	`references/diagrams/kanban.md`
Cloud infrastructure / service topology	Architecture	`references/diagrams/architecture.md`
Multi-dimensional comparison / skills radar	Radar	`references/diagrams/radar.md`
Hierarchical proportions / budget	Treemap	`references/diagrams/treemap.md`
Binary protocol / data format	Packet	`references/diagrams/packet.md`
Git branching / merge strategy	Git Graph	`references/diagrams/git_graph.md`
Code-style sequence (programming syntax)	ZenUML	`references/diagrams/zenuml.md`
Multi-diagram composition patterns	Complex Examples	`references/diagrams/complex_examples.md`

💡 Pick the right type, not the easy one. Don't default to flowcharts for everything. A timeline beats a flowchart for chronological events. A sequence beats a flowchart for service interactions. Scan the table and match.

🔧 Core workflow

Step 1: Identify the document type

Check if a template exists before writing from scratch:

Document type	Template
Pull request record	`templates/pull_request.md`
Issue / bug / feature request	`templates/issue.md`
Sprint / project board	`templates/kanban.md`
Architecture decision (ADR)	`templates/decision_record.md`
Presentation / briefing	`templates/presentation.md`
Research paper / analysis	`templates/research_paper.md`
Project documentation	`templates/project_documentation.md`
How-to / tutorial	`templates/how_to_guide.md`
Status report	`templates/status_report.md`

Step 2: Read the style guide

For this Markdown workflow, read references/markdown_style_guide.md. Treat emoji, heading counts, and horizontal rules as house style rather than Markdown syntax requirements.

Key rules to internalize:

One H1 per document — the title. Never more.
Emoji on H2 headings only — one emoji per H2, none in H3/H4
Support factual claims — use verified sources and the requested citation format
Bold sparingly — max 2-3 bold terms per paragraph, never full sentences
Optional horizontal rules after </details> when they improve separation
Tables over prose for comparisons, configurations, structured data
Diagrams over walls of text — if it describes flow, structure, or relationships, add Mermaid

Step 3: Pick the diagram type and read its guide

Before creating any Mermaid diagram: read references/mermaid_style_guide.md.

Then open the specific type file (e.g., references/diagrams/flowchart.md) for the exemplar, tips, and copy-paste template.

Add accessibility metadata for types that emit it in the chosen renderer:

accTitle: Short Name 3-8 Words
accDescr: One or two sentences explaining what this diagram shows.

Prefer host themes; %%{init} directives are deprecated in favor of YAML configuration
Prefer reusable classDef where supported; style syntax is diagram-specific
One emoji per node max — at the start of the label
Use descriptive IDs with the type's syntax: snake_case works for flowcharts; ER/class/state conventions differ

Step 4: Write the document

Start from the template. Apply the markdown style guide. Place diagrams inline with related text — not in a separate "Figures" section.

Render in the actual destination before delivery. Check its Mermaid version and plugin requirements before choosing newer diagram types; GitHub documents an info diagram for this check. A successful latest-version local preview does not establish GitHub or another host will render it. Where Mermaid is unsupported, supply a rendered SVG/PNG with a text description alongside the retained .md source.

Step 5: Retain source and verification

Keep the .md source, rendered deliverable, and tested renderer version together. Follow the project's version-control workflow; this skill does not itself authorize a commit or publication. For CLI export, embedding, and the tested accessibility matrix, read Current rendering and validation.

⚠️ Common pitfalls

Radar chart syntax (`radar-beta`)

WRONG (shown as text so it does not break the document renderer):

radar
title Example
x-axis ["A", "B", "C"]
"Series" : [1, 2, 3]

CORRECT:

radar-beta
accTitle: Example Radar Scores
accDescr: Illustrative values of one, two, and three on a shared zero-to-three scale.
title Example
axis a["A"], b["B"], c["C"]
curve series["Series"]{1, 2, 3}
max 3

Use radar-beta not radar (the bare keyword doesn't exist)
Use axis to define dimensions, not x-axis
Use curve to define data series, not quoted labels with colon
Mermaid 12.0.0 radar emits accTitle/accDescr; check older hosts and retain a visible description

XY Chart vs Radar confusion

Diagram	Keyword	Axis syntax	Data syntax
XY Chart (bars/lines)	`xychart-beta`	`x-axis ["Label1", "Label2"]`	`bar [10, 20]` or `line [10, 20]`
Radar (spider/web)	`radar-beta`	`axis id["Label"]`	`curve id["Label"]{10, 20}`

Forgetting `accTitle`/`accDescr` on supported types

Only some diagram types support accTitle/accDescr. For those that don't, always place a descriptive italic paragraph directly above the code block:

Radar chart comparing three methods on a stated, common score scale. See the data table for exact values.

radar-beta
...

🔗 Integration with other skills

With `scientific-schematics`

scientific-schematics generates AI-powered publication-quality images (PNG). Use the Mermaid diagram as the brief for the schematic:

Workflow:
1. Create the concept as Mermaid in .md (this skill — Phase 1)
2. Describe the same concept to scientific-schematics for a polished PNG (Phase 3)
3. Commit both — the .md as source, the PNG as a supplementary figure

With `scientific-writing`

For a manuscript that uses Mermaid structural figures, this skill handles diagram syntax. Follow the manuscript's required figure formats and scientific visualization conventions.

Workflow:
1. Use scientific-writing to draft the manuscript
2. For every figure that shows a workflow, architecture, or relationship:
   - Replace placeholder with a Mermaid diagram following this skill's guide
3. Use plotting or schematic tools where appropriate to the scientific content

With `literature-review`

Literature review produces summaries with lots of relationship data. Use this skill to:

Create concept maps (Mindmap) of the literature landscape
Show publication timelines (Timeline or Gantt)
Compare methodologies (Quadrant or Radar)
Diagram data flows described in papers (Sequence or Flowchart)

With any skill that produces output documents

Before finalizing a document using this skill, check:

[ ] Does the document use a template? If so, did I start from the right one?
[ ] Is each diagram in an appropriate format, with working accessibility metadata or a text alternative?
[ ] Is configuration supported by the destination and tested in light/dark themes?
[ ] Do citations support external claims, and are synthetic values labeled?
[ ] One H1, emoji on H2 only?
[ ] Does the final Markdown/HTML structure render correctly?

📚 Reference index

Style guides

Guide	Path	Lines	What it covers
Markdown Style Guide	`references/markdown_style_guide.md`	see file	Headings, formatting, citations, tables, Mermaid integration, templates, quality checklist
Mermaid Style Guide	`references/mermaid_style_guide.md`	see file	Accessibility, emoji set, color classes, theme neutrality, type selection, complexity tiers
Current Rendering	`references/current-rendering.md`	see file	Mermaid 12 changes, CLI export, browser APIs, tested accessibility matrix, scientific checks

Diagram guides (23 types plus composition)

Each file contains: production-quality exemplar, tips specific to that type, and a copy-paste template.

references/diagrams/ — 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

Document templates (9 types)

templates/ — decision_record, how_to_guide, issue, kanban, presentation, project_documentation, pull_request, research_paper, status_report

Examples

assets/examples/example-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.

📝 Attribution

All style guides, diagram type guides, and document templates in this skill are ported from the SuperiorByteWorks-LLC/agent-project repository under the Apache-2.0 License.

Source: https://github.com/SuperiorByteWorks-LLC/agent-project
Author: Clayton Young / Superior Byte Works, LLC (@borealBytes)
License: Apache-2.0

This 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.

[^1]: GitHub Blog. (2022). "Include diagrams in your Markdown files with Mermaid." https://github.blog/2022-02-14-include-diagrams-markdown-files-mermaid/

[^2]: Mermaid. "Mermaid Diagramming and Charting Tool." https://mermaid.js.org/

Files

ATTRIBUTION.mdAdded by AutoGineer1.1 KiB
LICENSEAdded by AutoGineer10.0 KiB
SKILL.md16.3 KiB
assets/examples/example-research-report.md3.4 KiB
references/current-rendering.md7.6 KiB
references/diagrams/architecture.md5.0 KiB
references/diagrams/block.md5.0 KiB
references/diagrams/c4.md6.7 KiB
references/diagrams/class.md8.6 KiB
references/diagrams/complex_examples.md16.8 KiB
references/diagrams/er.md8.0 KiB
references/diagrams/flowchart.md7.0 KiB
references/diagrams/gantt.md6.0 KiB
references/diagrams/git_graph.md2.2 KiB
references/diagrams/kanban.md4.0 KiB
references/diagrams/mindmap.md2.5 KiB
references/diagrams/packet.md2.4 KiB
references/diagrams/pie.md1.9 KiB
references/diagrams/quadrant.md2.6 KiB
references/diagrams/radar.md2.8 KiB
references/diagrams/requirement.md3.0 KiB
references/diagrams/sankey.md2.6 KiB
references/diagrams/sequence.md5.9 KiB
references/diagrams/state.md5.7 KiB
references/diagrams/timeline.md4.5 KiB
references/diagrams/treemap.md2.6 KiB
references/diagrams/user_journey.md5.2 KiB
references/diagrams/xy_chart.md2.6 KiB
references/diagrams/zenuml.md2.5 KiB
references/markdown_style_guide.md32.4 KiB
references/mermaid_style_guide.md26.6 KiB
templates/decision_record.md7.2 KiB
templates/how_to_guide.md7.1 KiB
templates/issue.md11.6 KiB
templates/kanban.md10.6 KiB
templates/presentation.md8.1 KiB
templates/project_documentation.md11.5 KiB
templates/pull_request.md11.8 KiB
templates/research_paper.md10.1 KiB
templates/status_report.md7.2 KiB

LICENSE

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

1. Definitions.

"License" shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document.

"Licensor" shall mean the copyright owner or entity authorized by the copyright owner that is granting the License.

"Legal Entity" shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, "control" means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity.

"You" (or "Your") shall mean an individual or Legal Entity exercising permissions granted by this License.

"Source" form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files.

"Object" form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types.

"Work" shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below).

"Derivative Works" shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof.

"Contribution" shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, "submitted" means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as "Not a Contribution."

"Contributor" shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.

2. Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.

3. Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.

4. Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that You meet the following conditions:

(a) You must give any other recipients of the Work or Derivative Works a copy of this License; and

(b) You must cause any modified files to carry prominent notices stating that You changed the files; and

(c) You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and

(d) If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License.

You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.

5. Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.

6. Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.

7. Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and assume any risks associated with Your exercise of permissions under this License.

8. Limitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages.

9. Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work.

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.

Requirements and compatibility

Works with: Claude Code, Claude apps, OpenAI Codex, GitHub Copilot, Cursor, Gemini CLI, Kiro, OpenCode, Goose, Amp, Roo Code, JetBrains Junie, Factory Droid, Devin (ex-Windsurf), Mistral Vibe, OpenHands, Letta

“Works with” means the tool reads the open Agent Skills format; a skill written for one tool may use features others lack.

Needs: Declares allowed tools, Needs Node.js

The author says: 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.

Security

What our scanner noticed· Low risk

Instructions that use the network

A static scan is not a guarantee. Skills are third-party content: review a skill before you let an agent use it.

Attribution and licence

Created by

Clayton Young / Superior Byte Works, LLC (@borealBytes)

Publisher

K-Dense (Community)

Distributed by

K-Dense

Source

K-Dense-AI/scientific-agent-skills · skills/markdown-mermaid-writing · commit a25cf9e

Licence

Apache License 2.0 (redistribution allowed)

LICENSE (written by AutoGineer)
ATTRIBUTION.md (written by AutoGineer)

Synced

2026-11-09

AutoGineer is not affiliated with or endorsed by Clayton Young / Superior Byte Works, LLC (@borealBytes) or K-Dense.

Download ZIP

The ZIP holds the skill’s files, its licence files and an ATTRIBUTION.md. Download markdown-mermaid-writing.zip