Install
$ agentstack add skill-asolfre-plantuml-rendering-skill-plantuml-rendering-skill ✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
About
Workflow
Use this flow to keep runs predictable and easy to debug.
1. Prepare the input
- The renderer expects a
.pumlfile on disk with@startumland@endumldelimiters. - If the user provides inline PlantUML text (pasted in chat, in a code block, etc.), save it to a
.pumlfile first. Pick a descriptive name based on the content — for example, if it describes authentication flow, save asauth-flow.puml. Place it in the same directory as related project files, or in the project root if there is no obvious location. - Java must be available on the system. If
javais not found, report that clearly and stop.
2. Render the diagram
The render script is bundled with this skill. Resolve its path relative to where this SKILL.md lives — the script is at scripts/render_diagram.sh inside this skill's directory.
/scripts/render_diagram.sh
The script handles path resolution internally, so the .puml file path can be absolute or relative to the current working directory.
Exit codes the script may return: | Code | Meaning | |------|---------| | 0 | Success — PNG created | | 1 | No input file argument provided | | 2 | Java not installed or not in PATH | | 3 | PlantUML JAR missing from skill bundle | | 4 | PlantUML execution error | | 5 | Input file not found on disk | | 6 | PlantUML exited OK but no PNG was generated (likely syntax issues in the source) |
3. Verify the output
After the script runs, confirm the PNG file exists next to the input .puml file. The output path follows PlantUML's convention:
docs/architecture.puml → docs/architecture.png
If the script reports exit code 6 (no PNG generated despite no PlantUML error), the source file likely has syntax problems. Check the PlantUML output for warnings like "no image in ...".
4. Handle multiple diagrams
If the user has several .puml files to render, call the script once per file. There is no batch mode — each invocation renders one diagram.
5. Fallback behavior
If local rendering fails for any reason (invalid syntax, environment issue, or user preference), provide this online fallback:
https://www.plantuml.com/plantuml/uml/
Tell the user to paste the PlantUML source there to validate syntax or generate an image quickly. If the failure appears environment-related (exit codes 2, 3, or 5), also report the likely cause so the user can fix their setup.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: asolfre
- Source: asolfre/plantuml-rendering-skill
- License: MIT
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet — be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.