Skip to content
TrustedSkillsbeta
Back to all skills

Deploy

Checked
awslabs·vlatest·devops·Apache-2.0

Automates deployment of machine learning models to AWS infrastructure using pre-defined pipelines and configurations.

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 awslabs/agent-plugins --skill deploy -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

awslabs

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 awslabs/agent-plugins at 097fe8ad56.

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

Commit
097fe8ad56
Manifest
plugins/deploy-on-aws/skills/deploy/SKILL.md
Scanned
4 files, 504 lines
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 awslabs-deploy skill automates deployments to various environments. It handles tasks like building, testing, and releasing code changes based on provided configurations. This allows for streamlined and repeatable deployment processes, reducing manual effort and potential errors.

When to use it

  • Deploying a new version of your application to a staging environment for testing.
  • Automating the release process after successful completion of automated tests.
  • Rolling back to a previous stable version in case of deployment issues.
  • Integrating with CI/CD pipelines to trigger deployments upon code commits.

Key capabilities

  • Automated deployments
  • Environment configuration management
  • Rollback functionality
  • Integration with CI/CD pipelines

Example prompts

  • "Deploy the latest version of my application to the staging environment."
  • "Run the automated tests and deploy if successful."
  • "Initiate a rollback to the previous stable release."

Tips & gotchas

The skill requires proper configuration files defining deployment targets and procedures. Ensure these are correctly set up before attempting deployments, as incorrect configurations can lead to unexpected results.