stack-diagram SKILL.md skillA

This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.

stack-diagram from orbyn-dev/orbyn-fullstack-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add orbyn-dev/orbyn-fullstack-skills/stack-diagram@git:20261116.5ae588a

Pins git:20261116.5ae588a in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
orbyn-dev/orbyn-fullstack-skills
Path
skills/stack-diagram/SKILL.md
Versions recorded
4
Latest version
git:20261116.5ae588a, committed Nov 16, 2026
First version recorded
Nov 2, 2026
Size
6,089 bytes
Repository stars
4
License
MIT

Turn a described stack into an architecture diagram as self-contained HTML, PNG or TSX, with grouped nodes and three edge kinds. Use architect for system design and state or lifecycle diagrams, technical-illustration for model-driven figures and motion, product-illustration for faux product UI.

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Stack diagram

Use this when someone describes a stack, a service topology or an infrastructure layout and wants a picture of how the parts connect. The result is an engineering-style drawing: icons on tiles, labelled group boxes, orthogonal arrows.

One built HTML file is the source of truth. PNG and TSX derive from it. Keep job files in a git-ignored working folder, for example `output/<job>/`.

This draws what exists and how it connects. A diagram of how one thing changes over time, with states, transitions and guards, is a statechart: use [architect](../architect/references/statecharts.md), which checks it against the real behaviour. A deployment shown here and a lifecycle shown there are often both useful. A diagram inside a film is redrawn in film code under the [code-only rule](../technical-illustration/references/code-only.md), using only logos the user supplied.

## Method

### 1. Settle the content

From the user's list, decide:

- **Nodes.** One per technology: a name and a short lowercase role such as `http server`.
- **Groups.** Draw a box around things that share a runtime, vendor or repository. Nest one level at most. Write labels in the brand's own casing.
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_h2eekktfqydvr7m3/1066178b7c1655c620dc5da6ef709ca239fb2795afd97f9ec94bfc8045122c63.json

Then /plugin install stack-diagram@markdownregistry-h2eekktfqydvr7m3 in Claude Code. It installs git:20261116.5ae588a, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add orbyn-dev/orbyn-fullstack-skills/stack-diagram@sha256:1066178b7c1655c6

The line at the top of this page pins the label git:20261116.5ae588a, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_h2eekktfqydvr7m3.svg)](https://markdownregistry.com/a/art_h2eekktfqydvr7m3)

1 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in orbyn-dev/orbyn-fullstack-skills/stack-diagram since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of stack-diagram from somewhere else? Ask it: where did my stack-diagram come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 4 versions of this file, between Nov 2, 2026 and Nov 16, 2026, about one every 5 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261116.5ae588a latest2026-11-16 5ae588a 6,089 BA view · diff
git:20261112.ccb817f2026-11-12 ccb817f 5,969 BA view · diff
git:20261106.90cf3742026-11-06 90cf374 6,963 BA view · diff
git:20261102.4d850f32026-11-02 4d850f3 6,667 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (6089 bytes)
  • pass: No zero-width or bidi control characters
  • pass: No instruction hidden inside an HTML comment
  • pass: No link to an exfiltration or paste host
  • pass: No credential-shaped string
  • pass: No instruction to send local credentials anywhere
  • pass: No text hidden with inline styles
  • pass: No prompt-injection phrasing
  • pass: No curl or wget piped into a shell
  • pass: No recursive delete of root, home or parent
  • pass: No instruction to read or print local credentials
  • pass: No base64 blob over 200 characters
  • pass: No link to a raw IP address
  • pass: No script tag

Source

GitHub

orbyn-dev/orbyn-fullstack-skills · 4 stars · license MIT · pushed 2026-11-16 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_h2eekktfqydvr7m3
GET https://markdownregistry.com/api/v1/resolve?ref=orbyn-dev/orbyn-fullstack-skills/stack-diagram
GET https://markdownregistry.com/api/v1/blob/1066178b7c1655c620dc5da6ef709ca239fb2795afd97f9ec94bfc8045122c63

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from orbyn-dev/orbyn-fullstack-skills

AGENTS.md AGENTS.md file
orbyn-dev/orbyn-fullstack-skills · AGENTS.md
git:20261109.2a02a02 · audit A · 4 stars
CLAUDE.md CLAUDE.md file
orbyn-dev/orbyn-fullstack-skills · CLAUDE.md
git:20261102.49be3ba · audit A · 4 stars
architect SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/architect/SKILL.md · Design data shapes, interfaces, ownership, statecharts and module boundaries for substantive features or refactors; use…
git:20261116.8c76756 · audit A · 4 stars
arena SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/arena/SKILL.md · Build and compare competing design or implementation sketches when a consequential choice cannot be resolved cheaply…
git:20261102.41fe595 · audit A · 4 stars
automate-me SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/automate-me/SKILL.md · Capture a working preference the user explicitly asks to keep in a reusable local skill, using the current conversation…
git:20261101.8be107b · audit A · 4 stars
figure-it-out SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/figure-it-out/SKILL.md · Execute an authorized large migration or cross-cutting change through to its measurable end state, tracking every unit…
git:20261102.41fe595 · audit A · 4 stars
how SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/how/SKILL.md · Trace source behavior, data flow and dependency impact across code, build and runtime boundaries; reproduce and reduce…
git:20261108.c9fb634 · audit A · 4 stars
interrogate SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/interrogate/SKILL.md · Challenge a specified design, patch or claim for concrete correctness, ownership and evidence gaps. Use for adversarial…
git:20261108.ead3465 · audit A · 4 stars
language-best-practices SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/language-best-practices/SKILL.md · Implement or review TypeScript, JavaScript, Python, Go, Rust, Java, Kotlin, C#, Swift, C, C++, SQL or shell code using…
git:20261101.8be107b · audit A · 4 stars
motion-match SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/motion-match/SKILL.md · Copy, clone or match how something moves: measure timing and easing, write a spec, build, film ours the same way and…
git:20261112.ccb817f · audit A · 4 stars
orbyn-affectui SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/orbyn-affectui/SKILL.md · Build agent UI in React from affectUI's free one-file components: tool-call cards, a decision inbox, a thinking loader…
git:20261111.8bded09 · audit A · 4 stars
orbyn-ai-application SKILL.md skill
orbyn-dev/orbyn-fullstack-skills · skills/orbyn-ai-application/SKILL.md · Design, implement or evaluate model-powered application behavior: grounded answers, retrieval, structured generation…
git:20261101.8be107b · audit A · 4 stars

Every file in orbyn-dev/orbyn-fullstack-skills

Other files named stack-diagram

stack-diagram SKILL.md skill
kinqsradio/orbyn-fullstack-skills · skills/stack-diagram/SKILL.md · Turn a described stack into an architecture diagram as self-contained HTML, PNG or TSX, with grouped nodes and three…
git:20261116.5ae588a · audit A · 4 stars

Browse by kind, by grade A, or by owner.