New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Hcp Create AWS

by openshift-eng in openshift-eng/ai-helpers

A skill your agent uses when you need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials, IAM roles, and VPC configuration

Apache-2.0Auto-check passedDevOps & Cloud

Install Hcp Create AWS

skills CLI
$ npx skills add openshift-eng/ai-helpers --skill hcp-create-aws -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install openshift-eng/ai-helpers hcp-create-aws --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/openshift-eng/ai-helpers.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/hcp/skills/hcp-create-aws .claude/skills/hcp-create-aws && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
hcp-create-aws
GitHub stars
120
Token cost
~4.3k tokens
SKILL.md length
724 words
Files
1
Skills in repo
118
Repo updated
First seen
Licence
Apache-2.0

At a glance

A skill your agent uses when you need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials, IAM roles, and VPC configuration

  • Works in 7 steps: Analyze Cluster Description → Apply AWS Provider Defaults → Interactive Parameter Collection → …
  • You need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials
  • SKILL.md covers When to Use This Skill, Prerequisites, AWS Provider Overview and Implementation Steps, plus 5 more sections
  • Calls aws, kubectl and jq; reaches hypershift.openshift.io and console.redhat.com

What it does

Hcp Create AWS is an agent skill from openshift-eng/ai-helpers. Use this skill when you need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials, IAM roles, and VPC configuration

Its SKILL.md is about 4.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in DevOps & Cloud. It works with Amazon Web Services. The repository describes itself as: Developer productivity tools for Claude Code & other AI assistants. The licence is Apache-2.0.

When your agent uses it

  • You need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials
  • VPC configuration

Example prompts

  • “/hcp-create-aws”

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Analyze Cluster Description
  2. Apply AWS Provider Defaults
  3. Interactive Parameter Collection
  4. Advanced Configuration (Conditional)
  5. Generate Command
  6. Pre-Flight Validation
  7. Post-Generation Instructions

What it can do on your machine

Read from SKILL.md and the folder at commit a627176. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • aws
    • kubectl
    • jq

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • hypershift.openshift.io
    • console.redhat.com
    • amd64.ocp.releases.ci.openshift.org

    Also links to:

    • docs.aws.amazon.com
    • docs.openshift.com

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Hcp Create AWS loads about 4.3k tokens when it runs. Until then it costs about 39 tokens; SKILL.md has 724 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~39
When it runs · the whole SKILL.md, loaded when a task matches
~4.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from openshift-eng/ai-helpers at commit a627176, republished under its Apache-2.0 licence (© openshift-eng). 724 words, ~4,273 tokens.

Download SKILL.mdSave it as .claude/skills/hcp-create-aws/SKILL.md (or your agent's skills folder).
name
hcp-create-aws
description
Use this skill when you need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials, IAM roles, and VPC configuration

HyperShift AWS Provider

This skill provides implementation guidance for creating HyperShift clusters on AWS, handling AWS-specific requirements including STS credentials, IAM roles, VPC configuration, and regional best practices.

When to Use This Skill

This skill is automatically invoked by the /hcp:generate aws command to guide the AWS provider cluster creation process.

Prerequisites

  • AWS CLI configured with appropriate credentials
  • HyperShift operator installed and configured
  • STS credentials file for the target AWS account
  • IAM role with required permissions for HyperShift
  • Pull secret for accessing OpenShift images

AWS Provider Overview

AWS Provider Peculiarities
  • Requires AWS credentials (STS): Must have valid STS credentials file
  • Region selection affects availability zones: Different regions have different AZ availability
  • Instance types vary by region: Not all instance types available in all regions
  • VPC CIDR must not conflict: Must not overlap with existing infrastructure
  • IAM roles: Can be auto-created or use pre-existing roles
Common AWS Configurations

Development Environment:

  • Single replica control plane (cost-effective)
  • m5.large instances (balanced performance/cost)
  • 2 availability zones (basic redundancy)
  • Basic networking (public endpoints)

Production Environment:

  • Highly available control plane
  • m5.xlarge+ instances (better performance)
  • 3+ availability zones (high availability)
  • Custom VPC configuration
  • KMS encryption enabled

Cost-Optimized Environment:

  • Single NAT gateway
  • Smaller instance types
  • Minimal replicas
  • Spot instances (where applicable)

Implementation Steps

Step 1: Analyze Cluster Description

Parse the natural language description for AWS-specific requirements:

Environment Type Detection:

  • Development: "dev", "development", "testing", "demo", "sandbox"
  • Production: "prod", "production", "critical", "enterprise"
  • Cost-Optimized: "cheap", "cost", "minimal", "budget", "demo"

Performance Indicators:

  • High Performance: "performance", "fast", "high-compute", "intensive"
  • Standard: Default moderate configuration
  • Minimal: "small", "minimal", "basic", "simple"

Security/Compliance:

  • FIPS: "fips", "compliance", "security", "regulated"
  • Private: "private", "isolated", "secure", "internal"

Special Requirements:

  • Multi-AZ: "highly available", "ha", "multi-zone", "resilient"
  • Single-AZ: "single zone", "simple", "minimal"
Step 2: Apply AWS Provider Defaults

Required Parameters:

  • --region: AWS region (default: us-east-1)
  • --pull-secret: Path to pull secret file
  • --release-image: OpenShift release image
  • --sts-creds: REQUIRED - Path to STS credentials file
  • --role-arn: REQUIRED - ARN of the IAM role to assume
  • --base-domain: REQUIRED - Base domain for the cluster

Smart Defaults by Environment:

Development Environment:

bash
--instance-type m5.large
--node-pool-replicas 2
--control-plane-availability-policy SingleReplica
--endpoint-access Public
--root-volume-size 120
--zones auto-select 2 zones based on region

Production Environment:

bash
--instance-type m5.xlarge
--node-pool-replicas 3
--control-plane-availability-policy HighlyAvailable
--endpoint-access PublicAndPrivate
--root-volume-size 120
--auto-repair true
--zones auto-select 3+ zones based on region

Cost-Optimized Environment:

bash
--instance-type m5.large
--node-pool-replicas 2
--control-plane-availability-policy SingleReplica
--endpoint-access Public
--root-volume-size 120
--zones auto-select 2 zones (minimal redundancy)
Step 3: Interactive Parameter Collection

Required Information Collection:

  1. Cluster Name

    🔹 **Cluster Name**: What would you like to name your cluster?
   - Must be DNS-compatible (lowercase, hyphens allowed)
   - Used for AWS resource naming
   - Example: dev-cluster, prod-app, demo-env

  2. AWS Region

    🔹 **AWS Region**: Which AWS region should host your cluster?
   - Consider latency to your users
   - Verify desired instance types are available
   - [Press Enter for default: us-east-1]

   Popular regions:
   - us-east-1 (N. Virginia) - Largest service availability
   - us-west-2 (Oregon) - West coast, latest services
   - eu-west-1 (Ireland) - Europe
   - ap-southeast-1 (Singapore) - Asia Pacific

  3. STS Credentials

    🔹 **STS Credentials**: Path to your AWS STS credentials file?
   - Required for AWS authentication
   - Generate using: aws sts get-session-token
   - Example: /home/user/.aws/sts-creds.json
   - Format: {"AccessKeyId": "...", "SecretAccessKey": "...", "SessionToken": "..."}

  4. IAM Role ARN

    🔹 **IAM Role ARN**: ARN of the IAM role for HyperShift?
   - Role must have required HyperShift permissions
   - Example: arn:aws:iam::123456789012:role/hypershift-operator-role
   - See: https://hypershift.openshift.io/aws-setup/

  5. Base Domain

    🔹 **Base Domain**: What base domain should be used for cluster DNS?
   - Must be a domain you control in Route53
   - Used for cluster API and application routes
   - Example: example.com, clusters.mycompany.com

  6. Pull Secret

    🔹 **Pull Secret**: Path to your OpenShift pull secret file?
   - Required for accessing OpenShift container images
   - Download from: https://console.redhat.com/openshift/install/pull-secret
   - Example: /home/user/pull-secret.json

  7. OpenShift Version

    🔹 **OpenShift Version**: Which OpenShift version do you want to use?

   📋 **Check supported versions**: https://amd64.ocp.releases.ci.openshift.org/

   - Enter release image URL: quay.io/openshift-release-dev/ocp-release:X.Y.Z-multi
   - [Press Enter for default: quay.io/openshift-release-dev/ocp-release:4.18.0-multi]

Optional Configuration (based on description analysis):

  1. Instance Type (if performance requirements detected)

    🔹 **Instance Type**: Select instance type based on your performance needs:
   - m5.large (2 vCPU, 8GB RAM) - Development, light workloads
   - m5.xlarge (4 vCPU, 16GB RAM) - Production, balanced workloads
   - m5.2xlarge (8 vCPU, 32GB RAM) - High-performance workloads
   - c5.xlarge (4 vCPU, 8GB RAM) - Compute-optimized
   - [Press Enter for default based on environment type]

  2. Node Pool Replicas

    🔹 **Node Pool Replicas**: How many worker nodes do you need?
   - Minimum: 2 (for basic redundancy)
   - Production recommended: 3+
   - [Press Enter for default based on environment type]

  3. Availability Zones (auto-selected, but confirmed)

    🔹 **Availability Zones**: Detected region: us-east-1
   Auto-selecting zones for optimal distribution:
   - Development: us-east-1a, us-east-1b (2 zones)
   - Production: us-east-1a, us-east-1b, us-east-1c (3 zones)

   Modify zone selection? [y/N]
Show full SKILL.md (312 more words)Show less
Step 4: Advanced Configuration (Conditional)

For FIPS Compliance (if detected):

🔹 **FIPS Mode**: Enable FIPS mode for compliance?
   - Required for government/regulated workloads
   - May impact performance
   - [yes/no] [Press Enter for default: no]

For High-Performance Workloads:

🔹 **Root Volume Size**: Increase root volume size?
   - Default: 120GB
   - High-performance workloads: 200GB+
   - [Press Enter for default: 120]

For Production Environments:

🔹 **Auto-Repair**: Enable automatic node repair?
   - Automatically replaces unhealthy nodes
   - Recommended for production
   - [yes/no] [Press Enter for default: yes for production]
Step 5: Generate Command

Basic AWS Cluster Command:

bash
hypershift create cluster aws \
  --name <cluster-name> \
  --namespace <cluster-name>-ns \
  --region <region> \
  --instance-type <instance-type> \
  --pull-secret <pull-secret-path> \
  --node-pool-replicas <replica-count> \
  --zones <zone-list> \
  --control-plane-availability-policy <policy> \
  --sts-creds <sts-creds-path> \
  --role-arn <role-arn> \
  --base-domain <base-domain> \
  --release-image <release-image>

Development Configuration Example:

bash
hypershift create cluster aws \
  --name dev-cluster \
  --namespace dev-cluster-ns \
  --region us-east-1 \
  --instance-type m5.large \
  --pull-secret /path/to/pull-secret.json \
  --node-pool-replicas 2 \
  --zones us-east-1a,us-east-1b \
  --control-plane-availability-policy SingleReplica \
  --endpoint-access Public \
  --root-volume-size 120 \
  --sts-creds /path/to/sts-creds.json \
  --role-arn arn:aws:iam::123456789012:role/hypershift-role \
  --base-domain example.com \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi

Production Configuration Example:

bash
hypershift create cluster aws \
  --name production-cluster \
  --namespace production-cluster-ns \
  --region us-west-2 \
  --instance-type m5.xlarge \
  --pull-secret /path/to/pull-secret.json \
  --node-pool-replicas 3 \
  --zones us-west-2a,us-west-2b,us-west-2c \
  --control-plane-availability-policy HighlyAvailable \
  --endpoint-access PublicAndPrivate \
  --root-volume-size 120 \
  --auto-repair \
  --sts-creds /path/to/sts-creds.json \
  --role-arn arn:aws:iam::123456789012:role/hypershift-prod-role \
  --base-domain clusters.company.com \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi

FIPS-Enabled Configuration:

bash
hypershift create cluster aws \
  --name compliance-cluster \
  --namespace compliance-cluster-ns \
  --region us-gov-east-1 \
  --instance-type m5.xlarge \
  --pull-secret /path/to/pull-secret.json \
  --node-pool-replicas 3 \
  --zones us-gov-east-1a,us-gov-east-1b,us-gov-east-1c \
  --control-plane-availability-policy HighlyAvailable \
  --fips \
  --sts-creds /path/to/sts-creds.json \
  --role-arn arn:aws-us-gov:iam::123456789012:role/hypershift-fips-role \
  --base-domain secure.gov.example.com \
  --release-image quay.io/openshift-release-dev/ocp-release:4.18.0-multi
Step 6: Pre-Flight Validation

Provide validation commands:

## Pre-Flight Checks

Before creating the cluster, verify your setup:

1. **AWS Credentials:**
   aws sts get-caller-identity

2. **STS Credentials File:**
   cat /path/to/sts-creds.json | jq .

3. **IAM Role Access:**
   aws iam get-role --role-name hypershift-role

4. **Route53 Domain:**
   aws route53 list-hosted-zones --query "HostedZones[?Name=='example.com.']"

5. **Region Availability:**
   aws ec2 describe-availability-zones --region us-east-1

6. **Instance Type Availability:**
   aws ec2 describe-instance-type-offerings --location-type availability-zone --filters Name=instance-type,Values=m5.large --region us-east-1
Step 7: Post-Generation Instructions

Next Steps:

## Next Steps

1. **Verify prerequisites are met:**
   - AWS credentials configured
   - STS credentials file exists and is valid
   - IAM role has required permissions
   - Base domain exists in Route53

2. **Run the generated command:**
   Copy and paste the command above

3. **Monitor cluster creation:**
   kubectl get hostedcluster -n <cluster-namespace>
   kubectl get nodepool -n <cluster-namespace>

4. **Check AWS resources:**
   - EC2 instances in AWS console
   - Load balancers created
   - VPC and networking resources

5. **Access cluster when ready:**
   hypershift create kubeconfig --name <cluster-name> --namespace <cluster-namespace>
   export KUBECONFIG=<cluster-name>-kubeconfig
   oc get nodes

Error Handling

Invalid AWS Credentials

Scenario: AWS credentials are invalid or expired.

Action:

AWS credentials validation failed.

Please check:
1. AWS CLI configuration: aws configure list
2. STS credentials file validity
3. IAM permissions

Regenerate STS credentials:
  aws sts get-session-token --duration-seconds 3600
IAM Role Not Found

Scenario: Specified IAM role doesn't exist or can't be assumed.

Action:

IAM role "arn:aws:iam::123456789012:role/hypershift-role" not found or inaccessible.

Please verify:
1. Role exists: aws iam get-role --role-name hypershift-role
2. Role has required permissions
3. Trust relationship allows your account to assume the role

See HyperShift AWS setup guide: https://hypershift.openshift.io/aws-setup/
Region/Zone Issues

Scenario: Instance type not available in selected region/zones.

Action:

Instance type "m5.large" not available in zone "us-east-1f".

Checking alternative zones in us-east-1:
✅ us-east-1a (available)
✅ us-east-1b (available)
❌ us-east-1f (not available)

Suggested zones: us-east-1a,us-east-1b

Would you like me to update the command?
Route53 Domain Issues

Scenario: Base domain not found in Route53 or not accessible.

Action:

Base domain "example.com" not found in Route53.

Please ensure:
1. Domain exists in Route53: aws route53 list-hosted-zones
2. Account has access to the hosted zone
3. Domain spelling is correct

Alternative: Use a subdomain you control (e.g., clusters.mydomain.com)
Resource Limits

Scenario: AWS account limits would be exceeded.

Action:

AWS service limits may be exceeded:
- EC2 instances: Current: 18/20, Requested: 5 more
- Elastic IPs: Current: 4/5, Requested: 2 more

Consider:
1. Request limit increases via AWS Support
2. Choose smaller instance types
3. Reduce node count
4. Clean up unused resources

Best Practices

Cost Optimization
  1. Right-size instances: Don't over-provision for development
  2. Use Spot instances: Where appropriate for non-critical workloads
  3. Monitor resource usage: Regularly review AWS costs
  4. Clean up unused clusters: Delete development clusters when not needed
Security
  1. Least privilege IAM: Use minimal required permissions
  2. STS credentials: Use short-lived credentials when possible
  3. Private networking: Use PrivateAndPublic endpoints for production
  4. KMS encryption: Enable for sensitive workloads
High Availability
  1. Multi-AZ deployment: Use 3+ availability zones for production
  2. Instance distribution: Spread nodes across zones
  3. Auto-repair: Enable for automatic recovery
  4. Monitoring: Set up CloudWatch monitoring
Network Planning
  1. VPC design: Plan CIDR ranges carefully
  2. Subnet strategy: Use public/private subnet design
  3. Load balancer: Configure appropriate load balancer types
  4. DNS: Ensure proper Route53 configuration

Anti-Patterns to Avoid

❌ Using root AWS credentials

Never use root account credentials for HyperShift

✅ Use IAM roles and STS credentials

❌ Single availability zone for production

--zones us-east-1a  # Single point of failure

✅ Use multiple zones: --zones us-east-1a,us-east-1b,us-east-1c

❌ Over-provisioning for development

--instance-type m5.8xlarge --node-pool-replicas 10  # Expensive for dev

✅ Use appropriate sizing: --instance-type m5.large --node-pool-replicas 2

❌ Ignoring region-specific limitations

Choosing regions without checking instance type availability

✅ Verify instance types and services are available in target region

Example Workflows

Startup Development Environment
Input: "cheap AWS cluster for testing our new microservice"

Analysis:
- Environment: Development
- Cost focus: High priority
- Scale: Minimal

Generated Command:
hypershift create cluster aws \
  --name dev-microservice \
  --namespace dev-microservice-ns \
  --region us-east-1 \
  --instance-type m5.large \
  --node-pool-replicas 2 \
  --control-plane-availability-policy SingleReplica \
  --endpoint-access Public
Enterprise Production
Input: "highly available AWS production cluster for customer-facing applications"

Analysis:
- Environment: Production
- Availability: High priority
- Scale: Enterprise

Generated Command:
hypershift create cluster aws \
  --name prod-customer-apps \
  --namespace prod-customer-apps-ns \
  --region us-west-2 \
  --instance-type m5.xlarge \
  --node-pool-replicas 5 \
  --zones us-west-2a,us-west-2b,us-west-2c \
  --control-plane-availability-policy HighlyAvailable \
  --endpoint-access PublicAndPrivate \
  --auto-repair

See Also

© openshift-eng, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in plugins/hcp/skills/hcp-create-aws of openshift-eng/ai-helpers.

Open the folder on GitHubat commit a627176

Compare with similar skills

Hcp Create AWS next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Hcp Create AWS compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Hcp Create AWS this skillopenshift-eng/ai-helpers120—~4.3kAutomated safety check: PassApache-2.0
Cloud Cost Optimizationwshobson/agents40k14 repos~1.7kAutomated safety check: PassMIT
Review Docshashicorp/terraform-provider-aws11k—~1.3kAutomated safety check: PassMPL-2.0
AWS Cdk Developmentzxkane/aws-skills3672 repos~2.5kAutomated safety check: PassMIT
Senior DevOps Toolkitmaslennikov-ig/claude-code-orchestrator-kit2606 repos~1.1kAutomated safety check: NotesCustom licence
Terravision Cloud Diagramspatrickchugh/terravision1.6k—~5.6kAutomated safety check: NotesAGPL-3.0-only

Similar skills

  • Cloud Cost Optimization

    wshobson/agents

    Cuts cloud spend across AWS, Azure, GCP and OCI with cost tagging, rightsizing, commitment and spot pricing models, and architecture changes.

    40k GitHub starsUsed in 14 repos~1.7k tokens
    DevOps & CloudAuto-check passed

  • Review Docs

    hashicorp/terraform-provider-aws

    Official

    Review a Terraform AWS Provider PR's end-user documentation (website/docs//.markdown): whether docs are needed, description openings, argument/attribute style, section structure, tags wording, code…

    11k GitHub stars~1.3k tokensUpdated today
    DevOps & CloudAuto-check passed

  • AWS Cdk Development

    zxkane/aws-skills

    AWS Cloud Development Kit (CDK) expert for building cloud infrastructure with TypeScript/Python.

    367 GitHub starsUsed in 2 repos~2.5k tokens
    DevOps & CloudAuto-check passed

  • Senior DevOps Toolkit

    maslennikov-ig/claude-code-orchestrator-kit

    Comprehensive DevOps skill for CI/CD, infrastructure automation, containerization, and cloud platforms (AWS, GCP, Azure). Includes pipeline setup…

    260 GitHub starsUsed in 6 repos~1.1k tokens
    DevOps & CloudAuto-check: notes

  • Terravision Cloud Diagrams

    patrickchugh/terravision

    Draw cloud architecture diagrams for AWS, Azure or GCP with the official provider icon sets, using TerraVision.

    1.6k GitHub stars~5.6k tokensUpdated 2 days ago
    DevOps & CloudAuto-check: notes

  • Thesvg

    glincker/thesvg

    Fetch brand SVG logos and cloud architecture icons (AWS, Azure, GCP) from theSVG.

    2.8k GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed

More from openshift-eng/ai-helpers

All 118 skills in this repo

  • Investigate CI Reliability

    openshift-eng/ai-helpers

    Find and independently validate actionable reliability defects across OpenShift release jobs and presubmits, then export portable issue handoffs.

    120 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Address Review PR

    openshift-eng/ai-helpers

    Fetch and address all PR review comments — categorize by priority, make code changes, post replies, and push.

    120 GitHub stars~2.9k tokensUpdated yesterday
    Auto-check passed

  • Categorize Activity Types

    openshift-eng/ai-helpers

    Categorize Jira issues into Red Hat Sankey Activity Type categories using MCP Jira tools.

    120 GitHub stars~2.4k tokensUpdated yesterday
    Auto-check passed

  • Has Review Work

    openshift-eng/ai-helpers

    Decide whether a GitHub PR has unanswered authorized review comments or new required CI failures worth a follow-up agent.

    120 GitHub stars~1.9k tokensUpdated yesterday
    Auto-check passed

  • Must Gather Analyzer

    openshift-eng/ai-helpers

    Analyze OpenShift must-gather diagnostic data including cluster operators, pods, nodes, and network components.

    120 GitHub stars~2.3k tokensUpdated yesterday
    Auto-check passed

  • Payload Autodl JSON

    openshift-eng/ai-helpers

    Schema for the autodl JSON data file produced by payload-analysis for database ingestion — you must use this skill whenever generating the autodl JSON file

    120 GitHub stars~2.6k tokensUpdated yesterday
    Auto-check passed

Works with

Categories

Questions about Hcp Create AWS

What does Hcp Create AWS do?

A skill your agent uses when you need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials, IAM roles, and VPC configuration. Hcp Create AWS is an agent skill from openshift-eng/ai-helpers.

When should I use Hcp Create AWS?

Hcp Create AWS fits situations like: you need to deploy HyperShift clusters on AWS infrastructure with proper STS credentials; VPC configuration.

How do I install Hcp Create AWS in Claude Code?

Run `npx skills add openshift-eng/ai-helpers --skill hcp-create-aws -a claude-code`. Or copy the skill folder (plugins/hcp/skills/hcp-create-aws in openshift-eng/ai-helpers) into .claude/skills/hcp-create-aws in your project. Claude Code loads it when a task matches its description.

How do I install Hcp Create AWS in Codex?

Run `npx skills add openshift-eng/ai-helpers --skill hcp-create-aws -a codex`. Or copy the skill folder (plugins/hcp/skills/hcp-create-aws in openshift-eng/ai-helpers) into .agents/skills/hcp-create-aws in your project. Codex loads it when a task matches its description.

Can I use Hcp Create AWS in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add openshift-eng/ai-helpers --skill hcp-create-aws -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/hcp-create-aws, .gemini/skills/hcp-create-aws, .github/skills/hcp-create-aws and .opencode/skills/hcp-create-aws in your project.

What does Hcp Create AWS need to run?

Going by SKILL.md and its folder, Hcp Create AWS needs the command-line tools its instructions call (aws, kubectl and jq).

Does Hcp Create AWS access the network?

SKILL.md names 5 domains. In commands or code: hypershift.openshift.io, console.redhat.com and amd64.ocp.releases.ci.openshift.org; the agent is likely to contact these when it follows the instructions. As links in the text: docs.aws.amazon.com and docs.openshift.com. This is read from the text; nothing was executed.

Is Hcp Create AWS safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Hcp Create AWS use?

Hcp Create AWS is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Hcp Create AWS use?

About 4.3k tokens (SKILL.md is roughly 17k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Hcp Create AWS?

Skills that share tags, products or a category with Hcp Create AWS: Cloud Cost Optimization (wshobson/agents, 40k stars), Review Docs (hashicorp/terraform-provider-aws, 11k stars), AWS Cdk Development (zxkane/aws-skills, 367 stars) and Senior DevOps Toolkit (maslennikov-ig/claude-code-orchestrator-kit, 260 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Hcp Create AWS?

openshift-eng (a GitHub organization) maintains it in openshift-eng/ai-helpers, which has 120 GitHub stars. The repository holds 118 skills in this directory. The repository was last updated on October 6, 2026.

Source: openshift-eng/ai-helpers on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.