Cross-check AWS-facing code and docs against official ROSA and AWS references before changing behavior.
409 tokens
context cost
the whole folder, loaded on every use
1
files
instructions only
0
copies elsewhere
how many repositories repackaged it
103
stars on the repo
on the repository, not the skill itself
Install
one command, takes just this skill from the repository
npx skills add https://github.com/openshift/rosa --skill ROSA AWS Context
The instruction itself
3 sections, as written by the author
ROSA AWS Context
Use this skill when:
Touching pkg/aws/ or AWS-related command flows
Editing AWS setup, prerequisites, or troubleshooting docs
Changing wording around HCP, classic, STS, IAM, OIDC, VPC, subnet, quota, or region behavior
Workflow
Read AGENTS.md and guidelines/aws-guidelines.md, then use the linked external ROSA and AWS references first.
Determine whether the change is HCP-only, classic-only, or shared.
Cross-check architecture claims against the ROSA architecture docs before changing code comments, help text, or docs.
Confirm prerequisite claims against the ROSA setup docs, especially quotas, support plans, SCP constraints, and STS token version notes.
Validate AWS CLI install, profile, and config guidance against official AWS CLI documentation before editing examples.
Prefer existing AWS helper functions and client wrappers over ad-hoc SDK usage.
Do not silently bump AWS SDK or related dependency versions; if a bump is required, call it out explicitly, explain why, and validate downstream impact.
Do not hardcode credentials or add logging that exposes secret material.
If code behavior and official docs appear to disagree, surface the mismatch explicitly instead of guessing.
Verification
Re-read the exact doc section that supports the changed behavior or wording.
Check user-facing examples for current commands and options.
Run the relevant local checks from CONTRIBUTING.md and Makefile.
How to use it
Copy the folder
Take openshift/rosa aws context from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
Check the name does not clash
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.