aws-judge-setup
# AWS & Kubernetes Environment Setup for Judge
What this skill does
# AWS & Kubernetes Environment Setup for Judge This skill ensures correct AWS and Kubernetes context before working on Judge platform tasks. ## When to Use Automatically activates when: - Working with Judge platform code - Running AWS CLI or Terraform commands - Executing kubectl commands - Starting work on demo-judge cluster ## Critical Setup Command **IMPORTANT: Always run this before starting Claude Code for Judge platform work:** ```bash export AWS_PROFILE=conda-demo && kubectl config use-context arn:aws:eks:us-east-1:831646886084:cluster/demo-judge ``` This ensures: - AWS CLI & Terraform use the `conda-demo` profile (demo account) - kubectl commands target the `demo-judge` EKS cluster - All agent commands will use the correct AWS account and Kubernetes context ## Command Prefixes When executing commands in Judge context: - **AWS/Terraform commands**: Always prefix with `AWS_PROFILE=conda-demo` ```bash AWS_PROFILE=conda-demo terraform plan AWS_PROFILE=conda-demo aws s3 ls ``` - **kubectl commands**: No prefix needed (context already set to demo-judge) ```bash kubectl get pods -n judge kubectl logs -n judge deployment/judge-api ``` ## Verification Before executing AWS or kubectl commands, verify: ```bash # Check AWS profile echo $AWS_PROFILE # Should output: conda-demo # Check kubectl context kubectl config current-context # Should output: arn:aws:eks:us-east-1:831646886084:cluster/demo-judge ``` ## Auto-Configuration When this skill is active, Claude will: 1. Verify AWS_PROFILE and kubectl context before AWS/kubectl commands 2. Automatically prefix AWS/Terraform commands with `AWS_PROFILE=conda-demo` 3. Warn if context appears incorrect for Judge platform work 4. Suggest re-running the setup command if needed
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.