Deployment Patterns
Rolling, blue-green, and canary strategies plus CI/CD pipelines, health checks, and production readiness checklists.
- What
- Rolling, blue-green, and canary strategies plus CI/CD pipelines, health checks, and production readiness checklists.
- Cost
- Free
- Needs
- the Muse app (mobile or web). Pure guidance skill, nothing to install. A web app you deploy (or plan to).
- Level
- Beginner — the Muse app (mobile or web).
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor: production deployment workflows and CI/CD best practices for web applications. Walks through the three core rollout strategies with their trade-offs: rolling deployments (zero downtime, but two versions coexist so changes must stay backward compatible), blue-green (instant rollback by switching traffic, at the cost of double infrastructure during cutover), and canary releases, plus the supporting machinery that makes them safe: health checks and readiness probes, environment-specific configuration, Docker containerization, and a production readiness checklist to run before every release. Written to be used at two moments: when setting up a pipeline from scratch, and as a pre-release sanity check when the stakes are high. By @affaan-m, listed here with credit to its creator. From the affaan-m/ECC repository (MIT). Honest caveats: strategy guidance, not a turnkey pipeline; you still adapt it to your platform (Kubernetes, VPS, PaaS) and your team's tolerance for risk. Skill Harbor never reviews the code, review it yourself before use.
Version:
Quick answer
Deployment Patterns is a free Muse skill for production deployment workflows and CI/CD best practices for web applications. It walks through three core rollout strategies with trade-offs: rolling deployments with zero downtime but two versions coexisting, blue-green with instant rollback by switching traffic at double infrastructure cost during cutover, and canary releases, plus health checks and production readiness checklists.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit 4eb71d9Pinned version: install the code at commit 4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. Use "Deployment Patterns" with your Muse. Prerequisites: the Muse app (mobile or web). Pure guidance skill, nothing to install. A web app you deploy (or plan to). 1. Open the skill: https://raw.githubusercontent.com/affaan-m/ECC/4eb71d92a39cab44ad40ac9d8a6a5ccb4029d6c2/skills/deployment-patterns/SKILL.md and copy the full SKILL.md text. 2. Paste it into a chat with Muse and add: "Help me choose a deployment strategy for [my app]: [stack, hosting, traffic level, tolerance for downtime]." 3. Ask Muse to compare rolling vs blue-green vs canary for your case, then draft the pipeline steps, health checks, and the pre-release readiness checklist. Tip: decide the rollback story before the rollout story. If you cannot describe how you revert in under a minute, the strategy is not finished. Safety: a skill is plain-text instructions; it runs nothing by itself. Review any pipeline config before applying it, never paste secrets into a chat, and review anything Muse proposes before it acts.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- 4eb71d9 · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 21, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : No commands, network calls, packages, file writes or API keys detected.
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.