Skip to content
TrustedSkillsbeta
Back to all skills

Deployment Patterns

Checked
affaan-m·vlatest·devops·MIT

Helps with deployment, patterns as part of automating DevOps pipelines and CI/CD workflows workflows.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add affaan-m/ecc --skill deployment-patterns -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

affaan-m

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned affaan-m/everything-claude-code at d3b8a3e908.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d3b8a3e908
Manifest
skills/deployment-patterns/SKILL.md
Scanned
3 files, 1,214 lines
Copies in repo
3 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The deployment-patterns skill provides guidance on best practices for deploying applications in various environments, including cloud, hybrid, and on-premise setups. It covers strategies like blue-green deployments, canary releases, and infrastructure-as-code integration.

When to use it

  • When planning a migration of an application to the cloud
  • When optimizing deployment pipelines for reliability and speed
  • When preparing for high-traffic events or scaling operations

Key capabilities

  • Explains common deployment strategies (e.g., blue-green, canary)
  • Integrates with infrastructure-as-code tools like Terraform and Ansible
  • Provides guidance on rollback procedures and monitoring during deployments

Example prompts

  • "Explain how to implement a blue-green deployment for a web application."
  • "What are the best practices for using canary releases in Kubernetes?"
  • "How can I automate deployment pipelines with infrastructure-as-code tools?"

Tips & gotchas

  • Ensure your team is familiar with version control and CI/CD tools before implementing advanced patterns.
  • Some strategies may require additional resources or cloud provider-specific configurations, so review documentation carefully.