agentsclimarketplace

Miro diagram generator

Skill MarieLynneBlock/arcanum-artifex/workflows/4plus1-diagrams/skills/miro-diagram-generator

Prompts, skills, and agents that survive contact with real workflows. No vendor loyalty. Occasionally heretical. 🧙🏻‍♀️

Install
npx -y skills add MarieLynneBlock/arcanum-artifex --skill miro-diagram-generator

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

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 2 stars2 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.

What its author says it does

Copied from the file, not written here

Generate Miro board prompts for architecture diagrams. Use this skill to produce per-view Miro prompts from canonical 4+1 diagram sources, with RISEN structure, strict scope boundaries, and track-specific validation.

SKILL.md

2.5 KB, as published. Nobody here has run it

Miro Diagram Generator

Generates Miro prompt artefacts for architecture views.

This skill is output-track specific:

  • consumes canonical architecture view content
  • produces Miro prompts only
  • does not own 4+1 method logic

Inputs required

For each view, provide:

  • view name (logical, process, development, physical, scenarios)
  • audience (dev-only, cross-functional, executive)
  • exact component list
  • exact relationship list
  • canonical source path (.mmd or .puml)

Workflow

Step 1 — Load template

Use templates/miro-prompt-template.md as the base.

Step 2 — Fill RISEN sections

The prompt must include:

  • Role
  • Input
  • Steps
  • Expectation
  • Narrowing

Step 3 — Enforce deterministic specificity

All prompts must include:

  • explicit frame title
  • explicit counts of shapes and arrows
  • explicit labels for all entities and connectors
  • explicit arrow semantics (solid/dashed/dotted)
  • explicit exclusions in Narrowing
  • for BPMN/swimlane process views, explicit shared semantic mapping: user task = primary, service task/start event = success, gateway = warning, end event = error, lane = neutral

Step 4 — Validate against canonical source

Check that names and relationships in the prompt match the canonical source exactly.

Step 5 — Write per-view output

Output files:

diagrams/miro/
  <view>-miro-prompt.md

Optional aggregate output:

diagrams/miro/full-board-prompt.md

Use templates/full-board-prompt-template.md when the user wants one aggregate board prompt that orchestrates all per-view Miro prompts.

Output contract

Each output must be:

  • valid markdown
  • one view per file
  • scoped to the target view only
  • free of cross-view leakage

Validation checklist

  • naming pattern: <view>-miro-prompt.md
  • template sections present (Role, Input, Steps, Expectation, Narrowing)
  • all component names match canonical source
  • all relationship labels match canonical source
  • no unlabeled arrows in instructions
  • no unsupported decorative elements
  • BPMN/swimlane process prompts include the shared semantic mapping above

References

  • templates/miro-prompt-template.md
  • templates/full-board-prompt-template.md
  • examples/synth-claim/miro-prompts/

Keep looking

Skills are one crate of 328,083. 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.