uml

Name: uml
Author: markdown-viewer

DevOps Community

Repo stars 2,891
Author updated Live
Author repo skills

Fluxly profile Facts only: domain, agents, trust score, runtime, permissions and network

Domain: DevOps
Compatible agents: Claude Code
Cursor
Cline
Codex
Windsurf
Gemini CLI

+20
Trust score: 88 / 100 · community maintained
Author / version / license: @markdown-viewer · no license declared
Token usage: Lean
Setup complexity: Plug-and-play
External API key: Not required
Operating systems: macOS · Linux · Windows
Runtime requirements: Node.js
Permissions: Read-only
Write / modify
Network behavior: Local-only
Install commands: 26 variants

Profile is derived at build time from SKILL.md and install vectors. Subject to drift from author intent.

Heads up: 未限定 allowed-tools，默认拥有全部工具权限。

Output preview uml.preview

---
name: uml
description: Create UML diagrams using PlantUML syntax. Best for software modeling — Class, Sequence, Activit…
category: devops
runtime: Node.js
---

# uml output preview

## PART A: Task fit
- Use case: Create UML diagrams using PlantUML syntax. Best for software modeling — Class, Sequence, Activity, State Machine, Component, Use Case, and Deployment diagrams with concise text-based notation and auto-layout..
- Inputs: target material, constraints, expected output, and acceptance criteria.
- Evidence boundary: follow “Critical Rules / UML Diagram Types / Mxgraph Stencil Icons” and do not present inference as author intent.

## PART B: Execution result
- **01** The card summarizes the use case; runtime output centers on “Create UML diagrams using PlantUML syntax. Best for software modeling — Class, Sequence, Activity, State Machine, Component, Use Case, and Deployment diagrams with concise text-based notation and auto-layout.”.
- **02** When the source has headings, the agent prioritizes “Critical Rules / UML Diagram Types / Mxgraph Stencil Icons” so the result follows the author’s structure.
- **03** Typical output includes task judgment, concrete steps, required commands or file edits, validation, and follow-up options.
- **04** Risk context follows the fingerprint: read files, write/modify files; mostly runs locally; usually needs no extra API key.

## Running Rules
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding scope.
- Return the result, validation criteria, and next iteration options.

SKILL.md SKILL.md

---
name: uml
description: Create UML diagrams using PlantUML syntax. Best for software modeling — Class, Sequence, Activit…
category: devops
source: markdown-viewer/skills
---

# uml

## When to use
- Create UML diagrams using PlantUML syntax. Best for software modeling — Class, Sequence, Activity, State Machine, Comp…
- Use it when the task has clear inputs, repeatable steps, and validation criteria.

## What to provide
- Target material, scope, expected result, and forbidden changes.
- Whether network, commands, file writes, or external services are allowed.

## Execution rules
- Organize steps around “Critical Rules / UML Diagram Types / Mxgraph Stencil Icons” and keep inference separate from source facts.
- read files, write/modify files; mostly runs locally; usually needs no extra API key.
- Validate with a small sample before expanding the task.

## Output requirements
- Return the deliverable, key evidence, validation method, and next action.
- Mark missing information as unknown; do not invent commands, platforms, or dependencies.

Evidence boundary and execution chain

The author source anchors workflow facts; repository files anchor sources and commands; Fluxly only adds fit, limitations, and quality judgment.

skill "uml" {
  input      -> user goal + target files + boundaries + acceptance criteria
  context    -> Critical Rules / UML Diagram Types / Mxgraph Stencil Icons
  rules      -> SKILL.md triggers / order / output contract
  runtime    -> Node.js | read files, write/modify files | mostly runs locally
  guardrails -> usually needs no extra API key + small-sample validation + diff/log review
  output     -> copyable result + checklist + next iteration
}

Interpretation is structured for decision-making; original keeps the upstream SKILL.md unchanged.

Decide Fit First

Core job: Create UML diagrams using PlantUML syntax. Best for software modeling — Class, Sequence, Activity, State Machine, Component, Use…
Best fit: Use it when the task has reusable inputs, steps, and validation criteria rather than a one-off answer.
Avoid forcing it: If the source lacks commands, platform support, or external-service evidence, keep those fields unknown instead of guessing.

Design Intent

Structure: The skill is organized around “Critical Rules”, “UML Diagram Types”, “Mxgraph Stencil Icons”, “Syntax”, showing how the author expects the agent to judge fit, collect context, and produce verifiable output.
Trigger evidence: Prioritize the author’s wording around when to use it, what context to collect, and what output shape to produce.
Evidence boundary: Author text states facts, repository files prove commands and paths, and Fluxly only adds fit, limits, and usage judgment.

How To Use It

Inputs: Provide target material, scope, expected result, forbidden changes, and validation method.
Invocation: Name uml directly; if the source includes slash commands, start with the command and then add task context.
Validation: Start small and check whether the result follows “Critical Rules / UML Diagram Types / Mxgraph Stencil Icons” before expanding.

Boundaries And Review

Dependencies: It usually needs no extra API key, so start with a small validation task.
Permissions: Declared permissions include read / write; ask the agent to state file, command, and rollback boundaries before acting.
Quality bar: A useful result names the deliverable, evidence, and next action. Generic prose means the task needs tighter context.

UML Diagram Generator

Quick Start: Choose diagram type → Write PlantUML text → Define elements and relationships → Wrap in ```plantuml fence.

⚠️ IMPORTANT: Always use ```plantuml or ```puml code fence. NEVER use ```text — it will NOT render as a diagram.

Critical Rules

Every diagram starts with @startuml and ends with @enduml
Use standard PlantUML keywords: class, interface, abstract, enum, actor, participant, component, node, database, package
Relationships use arrow syntax: -->, <|--, *--, o--, ..>, ..|>
Use skinparam for global styling and colors
Use #color on individual elements for specific colors
Notes use note left of, note right of, note over, or standalone note "text" as N

UML Diagram Types

Type	Purpose	Key Syntax	Example
Class	Class structure and relationships	`class`, `interface`, `<\|--`	class-diagram.md
Sequence	Message interactions over time	`participant`, `->`, `-->`	sequence-diagram.md
Activity	Workflow and process flow	`start`, `:action;`, `if/else`	activity-diagram.md
Swimlane Activity	Multi-role activity with swimlanes	`\|Lane\|`, `:action;`	swimlane-activity-diagram.md
State Machine	Object lifecycle states	`state`, `[*] -->`	state-machine-diagram.md
Component	System component organization	`component`, `[name]`, `interface`	component-diagram.md
Use Case	User-system interactions	`actor`, `usecase`, `(name)`	use-case-diagram.md
Deployment	Physical deployment architecture	`node`, `artifact`, `database`	deployment-diagram.md
Object	Runtime object snapshot	`object "name" as id`	object-diagram.md
Package	Module organization	`package "name"`	package-diagram.md
Communication	Object collaboration	Numbered messages with sequence syntax	communication-diagram.md
Composite Structure	Internal class structure	`component` with nested `port`	composite-structure-diagram.md
Interaction Overview	Activity + sequence combination	`group`, `ref over`	interaction-overview-diagram.md
Profile	UML extension mechanisms	`<<stereotype>>` labels	profile-diagram.md

Mxgraph Stencil Icons

draw-uml supports 9500+ mxgraph stencil icons (AWS, Azure, Cisco, Kubernetes, etc.) via the mxgraph.* syntax. Default colors are applied automatically — you do NOT need to specify fillColor or strokeColor.

Full stencil reference: See stencils/README.md.

Syntax

mxgraph.<namespace>.<icon> "Label" as <alias>
mxgraph.<namespace>.<icon> "Label" as <alias> #color
mxgraph.<namespace>.<icon> <alias>

mxgraph.<namespace>.<icon> — the stencil shape key (e.g. mxgraph.aws4.lambda, mxgraph.kubernetes.pod)
"Label" — display text (quoted if contains spaces, unquoted for single word)
as <alias> — identifier for use in relationships
#color — optional override color (e.g. #FF6600, #LightBlue)

Examples

@startuml
' Simple icon declaration
mxgraph.aws4.lambda "Lambda\nFunction" as fn
mxgraph.aws4.api_gateway "API GW" as gw
mxgraph.aws4.dynamodb "DynamoDB" as db

gw --> fn
fn --> db
@enduml

@startuml
' Kubernetes architecture with icons
mxgraph.kubernetes.ing "Ingress" as ing
mxgraph.kubernetes.svc "Service" as svc
mxgraph.kubernetes.pod "Pod" as pod
mxgraph.kubernetes.deploy "Deployment" as deploy

ing --> svc
svc --> pod
deploy --> pod
@enduml

@startuml
' Mixing standard UML with stencil icons
node "Cloud" {
  mxgraph.aws4.ec2 "EC2" as ec2
  mxgraph.aws4.rds "RDS" as rds
}
database "Legacy DB" as legacy

ec2 --> rds
rds --> legacy
@enduml

Install command

One-click installPick a runner, click Copy, paste into your terminal, press enter

npx skills add markdown-viewer/skills/uml -y

Open general install guide

View skill source

Works with

Claude Code
Cursor
Cline
Codex
Windsurf
Gemini
OpenCode
Roo Code
AAide
+Augment
GitHub Copilot
OpenClaw
KKiro
Junie
WWarp
Goose
Trae
Kilo Code
OpenHands
Amp
Zencoder
CContinue
AIAider
CodeBuddy
CodeGeeX
Replit Agent

Security audit

88 / 100

Community

未声明 license/许可。
未声明 version。
未限定 allowed-tools，默认拥有全部工具权限。

Metadata

Source: github
markdown-viewer/skills
中文

More by @markdown-viewer

A bpmn 88

Category & tags

Category DevOps