Watadot Aws Lambda

Serverless compute orchestration by Watadot Studio. Manage functions, triggers, and cloud rendering.

Security Scan

The skill is internally consistent: it provides AWS Lambda CLI instructions and only requires the aws CLI (and whatever AWS credentials the environment already provides) to operate — nothing unrelated is requested.

Purpose & Capability

Name/description match the content: SKILL.md contains AWS CLI commands for listing, invoking, updating, and configuring Lambda functions and sensible best-practice notes. The required binary (aws) is appropriate for the stated purpose.

Instruction Scope

Instructions are narrowly scoped to Lambda management (list, invoke, update code/config, concurrency). They do not reference unrelated files, external endpoints, or unexpected environment variables.

Install Mechanism

No install spec and no code files — instruction-only skill. This minimizes disk-write/remote-code risk.

Credentials

The skill declares no env vars but requires the aws CLI; the CLI will use standard AWS credentials (environment variables, ~/.aws/credentials, or instance/profile role). This is expected but important: the skill will act with whatever AWS credentials are available, so ensure least-privilege credentials and correct target account/region.

Persistence & Privilege

always is false and the skill has no install step that modifies other skills or global configs. Normal autonomous invocation is allowed (platform default) and is not, by itself, a red flag here.

Assessment

This skill is a set of AWS CLI recipes for managing Lambda and is coherent with its description. Before using it: (1) confirm your aws CLI is configured to the intended AWS account and region (and, if applicable, the intended profile); (2) give the agent only IAM credentials with least privilege — avoid using root or overly broad keys; (3) be cautious when running update-function-code or update-function-configuration commands (they change live functions); (4) if you do not want the agent to run cloud-modifying commands autonomously, avoid enabling autonomous invocation or run in a restricted environment. Because the skill is instruction-only, it does not add code to disk, but any aws commands it issues will execute with whatever credentials are present, so verify permissions and targets first.

AWS Lambda Skills

Architectural patterns for serverless execution and orchestration.

🚀 Core Commands

Function Lifecycle

# List all functions with runtime and memory info
aws lambda list-functions --query "Functions[].{Name:FunctionName,Runtime:Runtime,Memory:MemorySize}" --output table

# Invoke a function synchronously with payload
aws lambda invoke --function-name <name> --payload '{"key": "value"}' --cli-binary-format raw-in-base64-out response.json

Deployment & Configuration

# Update function code via ZIP
aws lambda update-function-code --function-name <name> --zip-file fileb://function.zip

# Update environment variables
aws lambda update-function-configuration --function-name <name> --environment "Variables={KEY=VALUE,ENV=PROD}"

Performance & Scaling

# Check concurrency limits and usage
aws lambda get-account-settings --query "AccountLimit"

# Put provisioned concurrency (warm start optimization)
aws lambda put-provisioned-concurrency-config --function-name <name> --qualifier <alias> --provisioned-concurrent-executions 5

🧠 Best Practices

1. Layer Management: Offload heavy dependencies (like FFmpeg or Chromium) into Lambda Layers to keep deployment packages small.
2. Timeout Strategy: Set aggressive timeouts to prevent runaway costs from stuck executions.
3. IAM Execution Role: Ensure the role has exactly the permissions needed for S3/DynamoDB access—no more.
4. Monitoring: Use CloudWatch Insights to trace latencies and cold starts.