AWS & Kubernetes Environment Setup for Judge

Configure AWS_PROFILE and kubectl context for Judge platform tasks.

1|Updated Oct 20, 2025
One-click install
npx skills add https://github.com/colek42/claude-plugins --skill aws-kubernetes-environment-setup-for-judge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: AWS & Kubernetes Environment Setup for Judge
Source: https://github.com/colek42/claude-plugins/tree/main/nk-aws-kubernetes/skills/aws-judge-setup
Command: npx skills add https://github.com/colek42/claude-plugins --skill aws-kubernetes-environment-setup-for-judge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures your AWS and Kubernetes environment is correctly configured for Judge platform tasks, eliminating manual setup errors and saving time spent debugging context issues. It automates the critical steps to get you working efficiently.

Core Features & Use Cases

  • Automated Context Configuration: Automatically sets the correct AWS_PROFILE and kubectl context for the Judge platform.
  • Command Prefixing: Intelligently prefixes AWS CLI and Terraform commands with the required AWS_PROFILE=conda-demo.
  • Verification & Warnings: Verifies your current AWS profile and kubectl context, warning you if they are incorrect and suggesting the necessary setup command.
  • Use Case: A developer starts a new day working on the Judge platform. This skill ensures their terminal environment is instantly configured with the correct AWS account and Kubernetes cluster, allowing them to run terraform plan or kubectl get pods without any manual context switching or configuration errors.

Quick Start

IMPORTANT: Always run this before starting Claude Code for Judge platform work:

export AWS_PROFILE=conda-demo && kubectl config use-context arn:aws:eks:us-east-1:831646886084:cluster/demo-judge

Verify your setup:

echo $AWS_PROFILE kubectl config current-context

Frequently Asked Questions about AWS & Kubernetes Environment Setup for Judge

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I set up AWS and Kubernetes context for Judge platform work?

AWS and Kubernetes context setup for Judge involves exporting AWS_PROFILE=conda-demo and configuring kubectl to use the demo-judge cluster context. Run: export AWS_PROFILE=conda-demo && kubectl config use-context arn:aws:eks:us-east-1:831646886084:cluster/demo-judge before starting Judge platform tasks.

Why should I verify my AWS profile and kubectl context before running Judge commands?

Verifying AWS profile and kubectl context prevents commands from executing against the wrong AWS account or Kubernetes cluster. Incorrect context can cause Terraform and kubectl commands to fail or modify unintended resources, so verification catches misconfigurations early.

Can I run Terraform and AWS CLI commands without manually setting AWS_PROFILE each time?

Yes. Setting AWS_PROFILE=conda-demo in your environment persists the correct AWS account context across all subsequent Terraform and AWS CLI commands in that session, eliminating repeated manual profile specification.

What happens if my kubectl context points to the wrong cluster when running Judge tasks?

kubectl commands execute against the wrong Kubernetes cluster, potentially querying or modifying resources outside the Judge demo-judge environment. The Skill verifies and warns you if context is incorrect, suggesting the correct setup command to realign.

Do I need to reconfigure my environment every time I start a new terminal session for Judge work?

Yes. Environment variables and kubectl context configuration are session-specific. Run the setup command at the start of each new terminal session to ensure AWS_PROFILE and kubectl context remain correctly configured for Judge platform tasks.