domains / families / devops / hf-cloud-aws-context-discovery

hf-cloud-aws-context-discovery

combined

Discover the user's local AWS context (active profile, region, account ID, caller identity) at the start of any AWS task. Use this skill before any other AWS work — deploying to SageMaker, creating resources, calling AWS APIs, or anything that touches an AWS account. Use it especially when the user has not specified a region or profile explicitly, when they say things like "use my AWS account", "deploy to AWS", "use my profile", or when about to make any AWS CLI or SDK call. Never guess the region or account ID — always use this skill to read it from the local configuration first. Discover the effective local AWS profile, region, account, and caller identity before any AWS task without exposing credentials.

When to use

• Establish the effective AWS profile, region, account, and caller before AWS work.
• Diagnose expired SSO sessions, missing profiles, or configuration overrides.
• Provide verified context to later SageMaker planning and deployment skills.

When not to use

• Discovery may reveal account IDs, role ARNs, or profile names; report only what the task needs and never expose secrets or session tokens.
• STS identity checks require network access and valid credentials.
• A valid identity does not imply permission to change resources.

Skill page

Conflict

The huggingface/skills copy is the upstream source, but the sickn33/agentic-awesome-skills copy is not a faithful reproduction. It adds a security layer (never open or print credentials, SSO token caches, or secret env vars; use masked CLI metadata commands like aws configure list-profiles and aws configure get region) and a Limitations section that the upstream copy lacks. The upstream copy, by contrast, explicitly permits reading ~/.aws/config and ~/.aws/credentials as plain INI files and relies on AWS_PROFILE/AWS_REGION/AWS_DEFAULT_REGION env vars for region resolution, which the mirror copy omits. Crowning the upstream copy would hide the mirror's credential-safety constraints, and crowning the mirror would hide the upstream's env-var resolution steps and raw-config reading guidance. The copies overlap heavily on the core discovery flow (profile, region, sts get-caller-identity, SSO ARN detection, reporting format) but each has material steps the other lacks, so combine is correct.