Skip to content
TrustedSkillsbeta
Back to all skills

Assume Cloudformation Role

Checked
daisuke897·vlatest·cloud

This skill allows you to automatically assume a CloudFormation role for your Lambda function, simplifying permissions management and enhancing security.

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 daisuke897/dotfiles --skill assume-cloudformation-role -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

daisuke897

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 daisuke897/dotfiles at f94f9c79fb.

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

Scanned
1 file, 76 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

This skill allows an AI agent to assume a CloudFormation role. This enables the agent to interact with and manage AWS resources defined in CloudFormation templates, granting temporary permissions for specific tasks. It facilitates automated infrastructure provisioning and management within your AWS environment.

When to use it

  • Automating deployments: Use this when you need to deploy or update CloudFormation stacks as part of a larger automation workflow.
  • Resource cleanup: Employ the skill to automatically delete unused resources defined in a CloudFormation template after testing or experimentation.
  • Infrastructure provisioning: Leverage the agent to create new infrastructure based on pre-defined CloudFormation templates, streamlining setup processes.
  • Security audits: Use it to review and validate configurations within your CloudFormation stacks for compliance purposes.

Key capabilities

  • Assumes a specified IAM role.
  • Interacts with AWS resources through CloudFormation.
  • Supports automated infrastructure management tasks.

Example prompts

  • "Assume the CloudFormation role 'DeploymentAdmin' and update stack 'MyWebApp'."
  • "Using the CloudFormation role, delete all stacks in region us-east-1 that have 'test' in their name."
  • "Can you assume the CloudFormation role named 'InfrastructureProvisioner'?"

Tips & gotchas

  • Ensure the AI agent has appropriate permissions to assume the specified IAM role.
  • Be mindful of the potential impact when modifying or deleting resources via CloudFormation; always test changes in a non-production environment first.