How do I install the Assume Cloudformation Role skill?

Run npx skillmds@latest add daisuke897/assume-cloudformation-role in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Assume Cloudformation Role safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Assume Cloudformation Role?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Assume Cloudformation Role free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Assume Cloudformation Role?

daisuke897 (@daisuke897) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Assume Cloudformation Role by daisuke897

Name: Assume Cloudformation Role
Author: daisuke897

Assume Cloudformation Role

Assume AWS IAM role for CloudFormation operations and set temporary credentials as environment variables. Use when working with CloudFormation stacks or when authentication setup is needed before AWS CloudFormation operations.

daisuke897 59a3c0c 2.6 KB Updated Sep 17, 2026

File contents

Assume CloudFormation Write Role

A skill to obtain the necessary credentials for AWS CloudFormation stack operations (create, delete, update) and set them as environment variables.

Purpose

Before CloudFormation operations, assume the specified role to obtain temporary credentials and set them as environment variables that can be used by AWS CLI.

Input Parameters

profile: AWS CLI profile name (default: <profile-name>)
role_arn: IAM role ARN to assume (default: arn:aws:iam::<AWS_ACCOUNT_ID>:role/<RoleName>)
role_session_name: Session name (default: cfn-write)

Execution Steps

Use AWS STS to assume the role and obtain credentials
Save credentials to a temporary file
Parse credentials using jq and set as environment variables
Clean up the temporary file

Command Example

# Assume role and obtain credentials
aws sts assume-role \
  --role-arn arn:aws:iam::<AWS_ACCOUNT_ID>:role/<RoleName> \
  --role-session-name cfn-write \
  --profile <profile-name> \
  > /tmp/creds.json

# Set environment variables
export AWS_ACCESS_KEY_ID=$(jq -r '.Credentials.AccessKeyId' /tmp/creds.json)
export AWS_SECRET_ACCESS_KEY=$(jq -r '.Credentials.SecretAccessKey' /tmp/creds.json)
export AWS_SESSION_TOKEN=$(jq -r '.Credentials.SessionToken' /tmp/creds.json)

# Remove temporary file
rm /tmp/creds.json

Output

Environment variables are set, making CloudFormation operations available via AWS CLI:

AWS_ACCESS_KEY_ID
AWS_SECRET_ACCESS_KEY
AWS_SESSION_TOKEN

Usage Examples

After executing this skill, the following CloudFormation commands become available:

# Create stack
aws cloudformation create-stack --stack-name my-stack --template-body file://template.yaml

# Update stack
aws cloudformation update-stack --stack-name my-stack --template-body file://template.yaml

# Delete stack
aws cloudformation delete-stack --stack-name my-stack

Prerequisites

AWS CLI installed
jq command installed
Specified profile configured in ~/.aws/credentials or ~/.aws/config
Source profile has sts:AssumeRole permission for the specified role

Notes

Credentials are temporary and typically expire after 1 hour
If credentials expire, re-execute this skill
For security purposes, temporary files are always deleted after processing

---name: assume-cloudformation-roledescription: Assume AWS IAM role for CloudFormation operations and set temporary credentials as environment variables. Use when working with CloudFormation stacks or when authentication setup is needed before AWS CloudFormation operations.---# Assume CloudFormation Write RoleA skill to obtain the necessary credentials for AWS CloudFormation stack operations (create, delete, update) and set them as environment variables.## PurposeBefore CloudFormation operations, assume the specified role to obtain temporary credentials and set them as environment variables that can be used by AWS CLI.## Input Parameters- `profile`: AWS CLI profile name (default: `<profile-name>`)- `role_arn`: IAM role ARN to assume (default: `arn:aws:iam::<AWS_ACCOUNT_ID>:role/<RoleName>`)- `role_session_name`: Session name (default: `cfn-write`)## Execution Steps1. Use AWS STS to assume the role and obtain credentials2. Save credentials to a temporary file3. Parse credentials using jq and set as environment variables4. Clean up the temporary file## Command Example```bash# Assume role and obtain credentialsaws sts assume-role \ --role-arn arn:aws:iam::<AWS_ACCOUNT_ID>:role/<RoleName> \ --role-session-name cfn-write \ --profile <profile-name> \ > /tmp/creds.json# Set environment variablesexport AWS_ACCESS_KEY_ID=$(jq -r '.Credentials.AccessKeyId' /tmp/creds.json)export AWS_SECRET_ACCESS_KEY=$(jq -r '.Credentials.SecretAccessKey' /tmp/creds.json)export AWS_SESSION_TOKEN=$(jq -r '.Credentials.SessionToken' /tmp/creds.json)# Remove temporary filerm /tmp/creds.json```## OutputEnvironment variables are set, making CloudFormation operations available via AWS CLI:- `AWS_ACCESS_KEY_ID`- `AWS_SECRET_ACCESS_KEY`- `AWS_SESSION_TOKEN`## Usage ExamplesAfter executing this skill, the following CloudFormation commands become available:```bash# Create stackaws cloudformation create-stack --stack-name my-stack --template-body file://template.yaml# Update stackaws cloudformation update-stack --stack-name my-stack --template-body file://template.yaml# Delete stackaws cloudformation delete-stack --stack-name my-stack```## Prerequisites- AWS CLI installed- jq command installed- Specified profile configured in `~/.aws/credentials` or `~/.aws/config`- Source profile has `sts:AssumeRole` permission for the specified role## Notes- Credentials are temporary and typically expire after 1 hour- If credentials expire, re-execute this skill- For security purposes, temporary files are always deleted after processing

Frequently asked questions