agentsclimarketplace
Sign in

Plantuml sequence diagram

Skill brunojaime/plantuml-diagram-toolkit/skills/plantuml-sequence-diagram

Generate and refine UML sequence diagrams in PlantUML from use cases, API flows, webhooks, queues, retries, callbacks, or architecture notes. Use when the user asks for secuencia, flujo temporal, order of calls, request/response, asynchronous events, alternatives, loops, errors, timeouts, or participant lifelines. Do not show deployment containment, static component topology, class structure, or database entity relationships.From its SKILL.md

Install
npx -y skills add brunojaime/plantuml-diagram-toolkit --skill plantuml-sequence-diagram

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.9 KB, 316 tokens by cl100k_base, as published. Nobody here has run it

PlantUML Sequence Diagram

Model who communicates, in what order, with which message, and under which conditions.

Workflow

  1. Define the scenario start, success outcome, and relevant failure boundary.
  2. Select participants by runtime role, not every internal class.
  3. Order messages from top to bottom and name messages by intent.
  4. Use solid arrows for calls/messages and dashed arrows for returns.
  5. Use alt, opt, loop, par, and break only when supported.
  6. Distinguish synchronous calls, asynchronous events, callbacks, retries, and timeouts.
  7. Apply conventions.md. Apply LANG-001 and LANG-002 to every user-visible label and response field.
  8. Render and inspect chronology and activation readability.
  9. Return one @startuml ... @enduml block plus assumptions.

Hard rules

  • A sequence arrow represents a message, not a component dependency or provided/required interface.
  • Generate all user-visible content in Spanish. Preserve official products, protocols, event names, and exact API/code identifiers.
  • Do not show nodes, regions, containers, class members, or DER cardinalities.
  • Do not invent retries, timeouts, response payloads, or error paths.
  • Keep one primary scenario per diagram; use a separate diagram for unrelated workflows.
  • Use unique aliases and no remote includes.

When user feedback is reusable, update references/conventions.md.

What ships with it: 3 files

1.6 KB alongside SKILL.md

agents/

references/

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.