cloud-design-patterns SKILL.md skillA
cloud-design-patterns from bg-szy/top-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add bg-szy/top-skills/cloud-design-patterns@v2.0Pins v2.0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- bg-szy/top-skills
- Path
skills/agent-skills/cloud-design-patterns/SKILL.md- Versions recorded
- 5
- Latest version
- v2.0, committed Nov 11, 2026
- First version recorded
- Jul 12, 2026
- Size
- 7,353 bytes
- Repository stars
- 6
- License
- a license file GitHub does not identify
Choose and compare cloud design patterns for distributed systems. Use when reviewing architecture, selecting workload patterns, or mapping reliability, performance, messaging, security, and migration concerns to concrete design options.
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
# Cloud Design Patterns Architects design workloads by integrating platform services, functionality, and code to meet both functional and nonfunctional requirements. To design effective workloads, you must understand these requirements and select topologies and methodologies that address the challenges of your workload's constraints. Cloud design patterns provide solutions to many common challenges. System design heavily relies on established design patterns. You can design infrastructure, code, and distributed systems by using a combination of these patterns. These patterns are crucial for building reliable, highly secure, cost-optimized, operationally efficient, and high-performing applications in the cloud. The following cloud design patterns are technology-agnostic, which makes them suitable for any distributed system. You can apply these patterns across Azure, other cloud platforms, on-premises setups, and hybrid environments. ## How Cloud Design Patterns Enhance the Design Process Cloud workloads are vulnerable to the fallacies of distributed computing, which are common but incorrect assumptions about how distributed systems operate. Examples of these fallacies include: …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_3d7cfps42icdyg2v/b1f1437ad3f9c9b41c14bb6a9ee39c7a4175bb5b13b50ab7e17a989c8a448648.json
Then /plugin install cloud-design-patterns@markdownregistry-3d7cfps42icdyg2v in Claude Code. It installs v2.0, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add bg-szy/top-skills/cloud-design-patterns@sha256:b1f1437ad3f9c9b4The line at the top of this page pins the label v2.0, 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.
[](https://markdownregistry.com/a/art_3d7cfps42icdyg2v)
1 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in bg-szy/top-skills/cloud-design-patterns 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 cloud-design-patterns from somewhere else? Ask it: where did my cloud-design-patterns 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 5 versions of this file, between Jul 12, 2026 and Nov 11, 2026, about one every 31 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| v2.0 latest | 2026-11-11 | b533f7f | 7,353 B | A | view · diff |
| v2.0 | 2026-08-25 | b67c05b | 6,818 B | A | view · diff |
| v2.0 | 2026-08-15 | 7b5e773 | 6,818 B | A | view · diff |
| v2.0 | 2026-07-30 | 5be6365 | 6,818 B | A | view · diff |
| v1.3 | 2026-07-12 | 94eb15d | 7,114 B | A | view |
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.
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.
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.
Installed this file, say at .claude/skills/cloud-design-patterns/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (7353 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
bg-szy/top-skills · 6 stars · license a license file GitHub does not identify · pushed 2026-11-15 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_3d7cfps42icdyg2v GET https://markdownregistry.com/api/v1/resolve?ref=bg-szy/top-skills/cloud-design-patterns GET https://markdownregistry.com/api/v1/blob/b1f1437ad3f9c9b41c14bb6a9ee39c7a4175bb5b13b50ab7e17a989c8a448648
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 bg-szy/top-skills
Every file in bg-szy/top-skills