Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →Use the correct AWS CLI profile when running AWS commands based on the target environment.
| Test case | Without → With | Effect | Δ tokens | Δ turns |
|---|---|---|---|---|
| case-02 | ✗→✓ | ▲ Improved | -40% | 0% |
| case-06 | ✗→✓ | ▲ Improved | 98% | 0% |
| case-08 | ✗→✓ | ▲ Improved | -2% | 0% |
| case-11 | ✗→✓ | ▲ Improved | -27% | 0% |
| case-12 | ✗→✓ | ▲ Improved | -13% | 0% |
When running AWS CLI commands, always pass the --profile flag based on the target environment.
Update the profile map below with your AWS profile names as configured in ~/.aws/config:
| Environment | Profile | |---|---| | Production | <your-prod-profile> | | Staging / Non-Prod | <your-nonprod-profile> |
bashaws <service> <command> --profile <profile> [options]
bash# Production aws s3 ls --profile my-prod-profile # Staging / Non-Prod aws s3 ls --profile my-nonprod-profile
--profile explicitly — never rely on the default profile.Other measured skills in the registry, with their headline benchmark lift.