菜单
Use AWS CLI correctly. Load this skill when doing any AWS work — querying resources, managing profiles, assuming roles, or asking the user to run AWS commands.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Load this skill when drafting or editing a Jira Change Request (CR) ticket in the CH project (Change Release) at thankyoupayroll.atlassian.net, or any change ticket whose primary reader is an executive approver rather than the implementing engineer. The skill covers audience framing, description structure, field-by-field guidance, and the CH project's known quirks (ADF formatting, character limits).
Spawn isolated agent sessions in their own git worktrees using the prism tool. Use when the user asks to spawn an agent, delegate work to another session, run something in parallel, or work on a PR or different repo.
Load this skill when the user signals that the current branch is a long-lived work-in-progress (WIP) branch where external review is deferred — phrases like "WIP", "work in progress", "long-lived branch", "feature branch", "defer review", "no reviews yet", "treat as WIP", "don't run reviews", "skip review for now", or similar. Once loaded, the worker stops kicking off `prism review` after each push and ignores the git-push reminder's review instruction until the user explicitly signals readiness.
Automates browser interactions for web testing, form filling, screenshots, and data extraction. Use when the user needs to navigate websites, interact with web pages, fill forms, take screenshots, test web applications, or extract information from web pages.
Load this skill when reading from or writing to Jira Cloud or Confluence Cloud — searching issues, fetching a specific Jira issue or Confluence page, listing or performing workflow transitions, creating/updating issues, commenting on issues, publishing or updating Confluence pages, or understanding the atlassian MCP tools.
Load this skill when drafting or reviewing acceptance criteria for an issue or ticket — before creating a work item, preparing a worker spawn prompt, or critiquing existing ACs before accepting work.
| name | aws |
| description | Use AWS CLI correctly. Load this skill when doing any AWS work — querying resources, managing profiles, assuming roles, or asking the user to run AWS commands. |
~/.aws/, ~/.config/aws/, or any AWS config/credentials file directly. Use the CLI.AWS_CONFIG_FILE env var may point to a restricted config. Respect it — don't override it or reference the default path.AWS_CONFIG_FILE, AWS_SHARED_CREDENTIALS_FILE, AWS_PROFILE, or AWS_DEFAULT_PROFILE env vars directly to work around the configured env. If a profile isn't available, ask the user.# List all configured profiles
aws configure list-profiles
# Show active config for current profile
aws configure list
# Show config for a specific profile
aws configure list --profile <name>
Pass --profile <name> on every command. Profile names match the environment or context being worked on (e.g. production, staging, dev). The same profile name exists in both the agent's restricted config and the user's full-access config — they map to different roles, but the name is the same.
aws sts get-caller-identity --profile production
aws s3 ls --profile staging
If a command fails due to missing permissions, or you need output from an environment the agent config doesn't have write access to, ask the user to run it rather than trying to work around it.
Provide a ready-to-run command wrapped in () piped to the clipboard so the user can run it and paste back the result:
(aws <command> --profile <name>) | @clipboardCmd@
Example prompt to user:
I need the output of the following command. Please run it and paste the result here:
(aws sts get-caller-identity --profile production) | @clipboardCmd@
# Verify identity
aws sts get-caller-identity --profile <name>
# List S3 buckets
aws s3 ls --profile <name>
# List EKS clusters
aws eks list-clusters --profile <name>
# Describe EC2 instances
aws ec2 describe-instances --profile <name>
# List IAM roles
aws iam list-roles --profile <name>
# Get SSM parameter
aws ssm get-parameter --name /my/param --profile <name>
Always pass --region explicitly or ensure it is set in the profile config. Do not rely on AWS_DEFAULT_REGION being set.
aws ec2 describe-instances --profile <name> --region eu-west-1