Turn complex existing or proposed behavior into checked state diagrams that show states, events, conditions, and recovery paths. The skill can compare diagrams with TLA+ specifications, validate models with TLC when available, and provide Mermaid plus a readable text view.
Explain complicated existing behavior using checked state diagrams. Use when asked for a state diagram, to diagram the previous explanation, show a bug or recovery path, compare a proposed fix or existing TLA+ spec, or derive a model from an agreed chart. Generates native Mermaid and a readable terminal fallback; optionally view and explicitly save in MEX Hub.
Run score Not tested
See how to installReview the instructions the agent will receive before you install.
Make behavior easier for a human to understand. Generate only on user intent. If a diagram would obscure the explanation, use a better explanation. A prior agent answer identifies the subject; verify it independently against current code.
mex wiki query "<subject>" --limit 5 --json before broad knowledge discovery; inspect matched terms and grounding health, then read live records. Fall back to Router-directed Markdown if unavailable. Use bounded mex timeline --query "subject" --file known/path --limit 10 --json only when history might matter. Verify historical applicability. Fresh Graph may locate evidence; call edges are not state transitions. Never refresh indexes on a read.scripts/runtime.mjs workflow entry, not the unbounded original scripts directly. Preserve existing TLA+ reference specifications and their authored configurations unchanged. Both from-spec and agreed-chart directions, settled-state rules, narrower observation points, projected overviews, independent regions, goals, proposed fixes and reference comparisons remain available.check on the artifact to record actual TLC results. For finite traces, map every numbered state/action back to the same graph and retain raw counterexamples. Goals are expected reachability witnesses, never product bugs. Use runtime summary counts, not counts inferred from the drawing. Missing mappings leave alignment unverified. Projection.json is optional: without it, or when check leaves the diagram unverified, accept and disclose that; never write your own TLC output parsers to force a projection. If TLC is unavailable (run status), still assemble the artifact with the check left unavailable and continue to step 7: the picture never depends on Java or TLC.show <artifact> <scratch-dir> once: it prints the deterministic text view and writes the artifact's own diagram.mmd and diagram.png. Deliver by client:
text block, then always open the printed diagram.png with your file-reading tool, unasked: the desktop app shows it inline. Make that read its own step: first write one short sentence such as "Here is the diagram:", then read the PNG with no other tool call before or after it, because the desktop app collapses grouped tool calls into a small thumbnail. Do not embed the image as Markdown; local image links do not render. In the terminal show also opens the image in the system viewer; tell the user, and give the path. Never present raw Mermaid as the diagram there.show produces both views. If the image is unavailable, say so and give the .mmd path. Keep domain labels readable; details belong beside the overview. Disclose every material omission. Inspect the image and numbered paths as generation QA. State diagram validity, checker outcome, implementation reproduction, and evidence freshness separately.register the validated artifact into the repository's ignored temporary preview store; this is checkout-only and nothing is shared. Keep its returned route and 24-hour expiry. Offer to open the specific diagram in Hub: for example, "Want me to open this in Hub? I can start it for you." When this repository's live Hub URL is already known, provide a clickable "View this diagram in Hub" link directly to the preview. Otherwise offer to start Hub; do not make the user run a command and find Diagrams themselves. Accepting the offer, or directly asking to open it, authorizes normal Hub startup and browser opening without another confirmation. Follow Opening the preview in Hub to preserve authentication and open the returned preview route. Generation alone does not launch Hub; never invent a localhost URL. Hub Save still requires its own exact review; commit/push remains separate. Regeneration creates a new preview and never updates old evidence baselines.No reviews yet. Tell others what you thought.
No login needed. Share how it worked for you, ask a question, or note where it did not run.
No comments yet. Be the first to write one.
Create review proposals for durable team knowledge in the project wiki, including decisions, conventions, and architecture notes. Check existing entries to find the right place for a correction or addition, and support changes to existing Specs when appropriate.
Turn a team decision, correction, or other durable project knowledge into a focused proposal for review. The skill checks existing knowledge so the contribution can extend or correct the right entry, and supports proposals for existing Specs.
Create and manage MEX Relays that preserve the context another teammate needs to continue work. Summarize progress, decisions, blockers, and next steps, or take and close a Relay. A Relay is a durable handoff record, not a message or task assignment.
Prepare and manage durable handoffs in MEX project memory. Capture progress, completed and ongoing work, blockers, decisions, and next steps so another teammate can resume. Relays preserve context; they do not send messages or assign tasks.