Watadot Aws Lambda
PassAudited by ClawScan on May 10, 2026.
Overview
This instruction-only skill matches its AWS Lambda management purpose, but its example commands can change cloud functions and costs using your configured AWS credentials.
Before using this skill, make sure your AWS CLI is pointed at the intended account, region, and least-privilege profile. Review and approve any commands that update function code, environment variables, or provisioned concurrency, especially for production Lambdas.
Findings (2)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
If run against the wrong function, account, or alias, these commands could change production behavior or increase AWS costs.
These are AWS CLI operations that can modify deployed Lambda code, environment variables, and concurrency settings. They are aligned with the skill's Lambda management purpose, but users should review before execution because they affect cloud resources.
aws lambda update-function-code --function-name <name> --zip-file fileb://function.zip
aws lambda update-function-configuration --function-name <name> --environment "Variables={KEY=VALUE,ENV=PROD}"
aws lambda put-provisioned-concurrency-config --function-name <name> --qualifier <alias> --provisioned-concurrent-executions 5Use an explicit AWS profile/account and require user confirmation before running update or concurrency-changing commands.
The agent may act with the permissions of the currently configured AWS credentials.
The skill relies on the AWS CLI, which uses the user's configured AWS identity and permissions. This is expected for AWS Lambda management, but the artifact does not specify a profile, account boundary, or least-privilege policy.
requires: anyBins: [aws] ... aws lambda list-functions
Use a least-privilege AWS role or dedicated profile for this skill, and verify the target account and region before running commands.