Skylv Mermaid Diagram

Generates Mermaid diagrams from descriptions. Creates flowcharts, sequence diagrams, and architecture diagrams. Triggers: mermaid diagram, architecture diagr...

Security Scan

The skill is an instruction-only Mermaid diagram generator whose requirements and instructions align with its stated purpose and do not request extra privileges or credentials.

Purpose & Capability

Name/description (generate Mermaid diagrams) match the content of SKILL.md, which provides templates and tips for flowcharts, sequence diagrams, and architecture diagrams. No unrelated capabilities or resources are requested.

Instruction Scope

SKILL.md contains only diagram templates, usage hints, and triggers. It does not instruct the agent to read local files, access environment variables, call external endpoints, or transmit data outside the expected task.

Install Mechanism

No install spec and no code files are present (instruction-only). Nothing is downloaded or written to disk by the skill itself.

Credentials

The skill requests no environment variables, credentials, or config paths — appropriate for a text-based diagram generator.

Persistence & Privilege

always is false and the skill does not request persistent system presence or modify system/other-skill settings. Autonomous invocation is allowed by default but is normal for skills and not combined with other risky factors here.

Assessment

This skill is low-risk and coherent: it produces Mermaid syntax (text) for diagrams but does not render images itself. If you plan to share sensitive architecture details, avoid pasting secrets or private credentials into prompts because the skill will include whatever you provide in generated diagram text. No special credentials or installs are required. If you need auto-rendering or exporting to specific services, look for a skill that explicitly integrates with that service and requests only the minimal credentials required.

Mermaid Diagram Generator

Overview

Generates Mermaid diagrams for documentation.

When to Use

• User asks to "draw a diagram" or "create architecture diagram"

Flowchart Template

graph TD A[Start] --> B{Decision} B -->|Yes| C[Action 1] B -->|No| D[Action 2] C --> E[End] D --> E

Sequence Diagram Template

sequenceDiagram Client->>API: POST /orders API->>DB: INSERT order DB-->>API: order_id API-->>Client: Confirmation

Architecture Diagram Template

graph TB subgraph Frontend A[React App] end subgraph Backend B[API Gateway] C[Auth Service] end A --> B B --> C

Tips

• Use LR (left-right) or TD (top-down)
• Use subgraphs to group components
• Add notes for complex decisions