Agent skill

Create Infrastructure

by harness in harness/harness-skills

Generate Harness Infrastructure Definition YAML for deployment targets and create via MCP.

Apache-2.0Auto-check passedDevOps & Cloud

Install Create Infrastructure

skills CLI
$ npx skills add harness/harness-skills --skill create-infrastructure -a claude-code

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

GitHub CLI
$ gh skill install harness/harness-skills create-infrastructure --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/harness/harness-skills.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/create-infrastructure .claude/skills/create-infrastructure && 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
create-infrastructure
GitHub stars
115
Token cost
~1.3k tokens
SKILL.md length
215 words
Files
1
Skills in repo
64
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate Harness Infrastructure Definition YAML for deployment targets and create via MCP.

  • Works in 4 steps: Identify infrastructure type -… → Ensure prerequisites exist - The… → Generate YAML using the templates below,… → …
  • User says create infrastructure
  • SKILL.md covers Instructions, Infrastructure Types, Creating via MCP and Examples, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Create Infrastructure is an agent skill from harness/harness-skills. Generate Harness Infrastructure Definition YAML for deployment targets and create via MCP. Use when user says "create infrastructure", "infrastructure definition", "k8s cluster config", "deployment target", or wants to configure where workloads run.

Its SKILL.md is about 1.3k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts. Compatibility notes: Requires Harness MCP v2 server (harness-mcp-v2)

It sits in DevOps & Cloud, covering Container orchestration and Deployment. It works with Model Context Protocol, Kubernetes and Google Kubernetes Engine. The repository describes itself as: A collection of structured AI agent skills that enable Claude Code, Cursor, GitHub Copilot, and other AI coding assistants to create, operate, debug, and govern Harness CI/CD… The licence is Apache-2.0.

When your agent uses it

  • User says create infrastructure
  • Infrastructure definition
  • K8s cluster config
  • Deployment target

Example prompts

  • “create infrastructure”
  • “infrastructure definition”
  • “k8s cluster config”
  • “/create-infrastructure”

Requirements

  • Compatibility (from SKILL.md): Requires Harness MCP v2 server (harness-mcp-v2)

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Identify infrastructure type - KubernetesDirect, KubernetesGcp (GKE), KubernetesAzure (AKS), ECS, or ServerlessAwsLambda
  2. Ensure prerequisites exist - The environment and cloud/cluster connector must be created first
  3. Generate YAML using the templates below, referencing the correct connector and environment
  4. Create via MCP using harness_create with resource_type infrastructure

What it can do on your machine

Read from SKILL.md and the folder at commit c25faee. 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

    No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml).

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

  • Network

    No URLs in SKILL.md.

    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.

  • Compatibility

    Requires Harness MCP v2 server (harness-mcp-v2)

    From compatibility in the SKILL.md frontmatter.

Context cost

Create Infrastructure loads about 1.3k tokens when it runs. Until then it costs about 68 tokens; SKILL.md has 215 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~68
When it runs · the whole SKILL.md, loaded when a task matches
~1.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 harness/harness-skills at commit c25faee, republished under its Apache-2.0 licence (© harness). 215 words, ~1,258 tokens.

Download SKILL.mdSave it as .claude/skills/create-infrastructure/SKILL.md (or your agent's skills folder).
name
create-infrastructure
description
Generate Harness Infrastructure Definition YAML for deployment targets and create via MCP. Use when user says "create infrastructure", "infrastructure definition", "k8s cluster config", "deployment target", or wants to configure where workloads run.
compatibility
Requires Harness MCP v2 server (harness-mcp-v2)
metadata.author
Harness
metadata.version
2.0.0
metadata.mcp-server
harness-mcp-v2
license
Apache-2.0

Create Infrastructure

Generate Harness Infrastructure Definition YAML and push via MCP.

Instructions

  1. Identify infrastructure type - KubernetesDirect, KubernetesGcp (GKE), KubernetesAzure (AKS), ECS, or ServerlessAwsLambda
  2. Ensure prerequisites exist - The environment and cloud/cluster connector must be created first
  3. Generate YAML using the templates below, referencing the correct connector and environment
  4. Create via MCP using harness_create with resource_type infrastructure

Infrastructure Types

KubernetesDirect
yaml
infrastructureDefinition:
  name: K8s Production
  identifier: k8s_prod
  orgIdentifier: default
  projectIdentifier: my_project
  environmentRef: prod
  deploymentType: Kubernetes
  type: KubernetesDirect
  spec:
    connectorRef: k8s_connector
    namespace: my-app-prod
    releaseName: release-<+INFRA_KEY_SHORT_ID>
  allowSimultaneousDeployments: false
KubernetesGcp (GKE)
yaml
infrastructureDefinition:
  name: GKE Cluster
  identifier: gke_prod
  environmentRef: prod
  deploymentType: Kubernetes
  type: KubernetesGcp
  spec:
    connectorRef: gcp_connector
    cluster: my-gke-cluster
    namespace: my-app
    releaseName: release-<+INFRA_KEY_SHORT_ID>
KubernetesAzure (AKS)
yaml
infrastructureDefinition:
  name: AKS Cluster
  identifier: aks_prod
  environmentRef: prod
  deploymentType: Kubernetes
  type: KubernetesAzure
  spec:
    connectorRef: azure_connector
    subscriptionId: <subscription_id>
    resourceGroup: my-rg
    cluster: my-aks-cluster
    namespace: my-app
    releaseName: release-<+INFRA_KEY_SHORT_ID>
ECS
yaml
infrastructureDefinition:
  name: ECS Fargate
  identifier: ecs_prod
  environmentRef: prod
  deploymentType: ECS
  type: ECS
  spec:
    connectorRef: aws_connector
    region: us-east-1
    cluster: my-ecs-cluster
ServerlessAwsLambda
yaml
infrastructureDefinition:
  name: Lambda
  identifier: lambda_prod
  environmentRef: prod
  deploymentType: ServerlessAwsLambda
  type: ServerlessAwsLambda
  spec:
    connectorRef: aws_connector
    region: us-east-1
    stage: prod
AzureWebApp
yaml
infrastructureDefinition:
  name: Azure Web App
  identifier: azure_webapp_prod
  environmentRef: prod
  deploymentType: AzureWebApp
  type: AzureWebApp
  spec:
    connectorRef: azure_connector
    subscriptionId: <subscription_id>
    resourceGroup: my-rg
Asg (Auto Scaling Group)
yaml
infrastructureDefinition:
  name: ASG Production
  identifier: asg_prod
  environmentRef: prod
  deploymentType: Asg
  type: Asg
  spec:
    connectorRef: aws_connector
    region: us-east-1
GoogleCloudFunctions
yaml
infrastructureDefinition:
  name: Cloud Functions
  identifier: gcf_prod
  environmentRef: prod
  deploymentType: GoogleCloudFunctions
  type: GoogleCloudFunctions
  spec:
    connectorRef: gcp_connector
    region: us-central1
    project: my-gcp-project
Pdc (Physical Data Center)
yaml
infrastructureDefinition:
  name: On-Prem Servers
  identifier: pdc_prod
  environmentRef: prod
  deploymentType: Ssh
  type: Pdc
  spec:
    connectorRef: pdc_connector
    hosts:
      - host1.example.com
      - host2.example.com

Creating via MCP

Call MCP tool: harness_create
Parameters:
  resource_type: "infrastructure"
  org_id: "<organization>"
  project_id: "<project>"
  body: <infrastructure YAML>

Examples

  • "Create a K8s infrastructure for prod" - KubernetesDirect with prod namespace
  • "Set up GKE infrastructure" - KubernetesGcp with GCP connector
  • "Create ECS Fargate infrastructure" - ECS type with AWS connector
  • "Create Azure Web App infrastructure" - AzureWebApp type with subscription and resource group
  • "Set up on-prem infrastructure" - Pdc type with host list for SSH deployments

Performance Notes

  • Verify the referenced connector and environment exist before creating the infrastructure definition.
  • Ensure namespace and cluster names are accurate — typos will cause deployment failures.
  • Use <+INFRA_KEY_SHORT_ID> in releaseName to guarantee uniqueness across deployments.

Troubleshooting

  • CONNECTOR_NOT_FOUND - Create the cloud/K8s connector first
  • ENVIRONMENT_NOT_FOUND - Create the environment first
  • releaseName must be unique per deployment; use <+INFRA_KEY_SHORT_ID>
  • deploymentType must match the service definition's type (e.g., Kubernetes service needs KubernetesDirect infra)
  • allowSimultaneousDeployments: false is the default; set to true only if concurrent deploys are safe

© harness, 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 skills/create-infrastructure of harness/harness-skills.

Open the folder on GitHubat commit c25faee

Compare with similar skills

Create Infrastructure 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.

Create Infrastructure compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Infrastructure this skillharness/harness-skills115—~1.3kAutomated safety check: PassApache-2.0
Google Cloud Solution Guided Gke AI Migrationgoogle/skills21k—~8.3kAutomated safety check: PassApache-2.0
KubeShark for KubernetesLukasNiessen/kubernetes-skill444—~1.2kAutomated safety check: PassMIT
Kcli Cluster Deploymentkarmab/kcli653—~1.5kAutomated safety check: PassApache-2.0
Gke Manifest Generationgoogle/skills21k—~3.1kAutomated safety check: PassApache-2.0
Gke Batch Hpcgoogle/skills21k—~1.4kAutomated safety check: PassApache-2.0

Similar skills

  • Guides the migration of existing AI workloads (Cloud Run, Gemini API, Gemini Enterprise Agent Platform) to self-hosted GKE inference using gcloud and kubectl.

    21k GitHub stars~8.3k tokensUpdated today
    DevOps & CloudAuto-check passed
  • KubeShark for Kubernetes

    LukasNiessen/kubernetes-skill

    Keeps Kubernetes manifests, Helm charts and policies grounded by diagnosing six failure modes, such as insecure defaults and API drift, and loading only matching references.

    444 GitHub stars~1.2k tokensUpdated 24 days ago
    DevOps & CloudAuto-check passed
  • Guides deployment and management of Kubernetes clusters with kcli.

    653 GitHub stars~1.5k tokensUpdated yesterday
    DevOps & CloudAuto-check passed
  • Official

    Generates and updates secure, production-ready Kubernetes YAML manifests optimized for GKE Autopilot and GKE Standard clusters.

    21k GitHub stars~3.1k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Gke Batch Hpc

    google/skills

    Official

    Runs batch and HPC workloads on GKE, utilizing job queues and parallel processing.

    21k GitHub stars~1.4k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Gke Upgrades

    google/skills

    Official

    Plans, executes, and validates Google Kubernetes Engine (GKE) cluster upgrades and maintenance operations for both Standard and Autopilot clusters.

    21k GitHub stars~5k tokensUpdated today
    DevOps & CloudAuto-check passed

More from harness/harness-skills

All 64 skills in this repo
  • Audit Report

    harness/harness-skills

    Generate audit reports and compliance trails using Harness audit trail data via MCP v2 tools.

    115 GitHub stars~1.3k tokensUpdated today
    Auto-check passed
  • Chaos Dr Test

    harness/harness-skills

    A skill your agent uses when working with Chaos Engineering steps inside a Harness pipeline.

    115 GitHub stars~2.6k tokensUpdated today
    Auto-check passed
  • Chaos Experiment

    harness/harness-skills

    A skill your agent uses when the user asks to create, edit, update, design, or configure a Harness Chaos Experiment — including faults, probes, actions, experiment YAML, fault injection, pod-delete…

    115 GitHub stars~1.6k tokensUpdated today
    Auto-check passed
  • Cleanup Feature Flags

    harness/harness-skills

    Remove a launched Harness FME feature flag from application code, keeping the treatment FME serves today, and open a pull request.

    115 GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Configure Repo Scan

    harness/harness-skills

    Configure code scanning in Harness pipelines using STO security scanners.

    115 GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Create Agent Template

    harness/harness-skills

    Generate Harness Agent Template files for AI-powered automation agents.

    115 GitHub stars~2.2k tokensUpdated today
    Auto-check passed

Categories

Questions about Create Infrastructure

What does Create Infrastructure do?

Generate Harness Infrastructure Definition YAML for deployment targets and create via MCP. Create Infrastructure is an agent skill from harness/harness-skills. Generate Harness Infrastructure Definition YAML for deployment targets and create via MCP.

When should I use Create Infrastructure?

Create Infrastructure fits situations like: user says create infrastructure; infrastructure definition; K8s cluster config; deployment target.

How do I install Create Infrastructure in Claude Code?

Run `npx skills add harness/harness-skills --skill create-infrastructure -a claude-code`. Or copy the skill folder (skills/create-infrastructure in harness/harness-skills) into .claude/skills/create-infrastructure in your project. Claude Code loads it when a task matches its description.

How do I install Create Infrastructure in Codex?

Run `npx skills add harness/harness-skills --skill create-infrastructure -a codex`. Or copy the skill folder (skills/create-infrastructure in harness/harness-skills) into .agents/skills/create-infrastructure in your project. Codex loads it when a task matches its description.

Can I use Create Infrastructure 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 harness/harness-skills --skill create-infrastructure -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/create-infrastructure, .gemini/skills/create-infrastructure, .github/skills/create-infrastructure and .opencode/skills/create-infrastructure in your project.

What does Create Infrastructure need to run?

SKILL.md names no scripts, command-line tools or credentials: Create Infrastructure is instructions for the agent only. Compatibility (from SKILL.md): Requires Harness MCP v2 server (harness-mcp-v2).

Does Create Infrastructure access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Create Infrastructure 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 Create Infrastructure use?

Create Infrastructure is published under the Apache-2.0 licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Create Infrastructure use?

About 1.3k tokens (SKILL.md is roughly 5k 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 Create Infrastructure?

Skills that share tags, products or a category with Create Infrastructure: Google Cloud Solution Guided Gke AI Migration (google/skills, 21k stars), KubeShark for Kubernetes (LukasNiessen/kubernetes-skill, 444 stars), Kcli Cluster Deployment (karmab/kcli, 653 stars) and Gke Manifest Generation (google/skills, 21k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Infrastructure?

harness (a GitHub organization) maintains it in harness/harness-skills, which has 115 GitHub stars. The repository holds 64 skills in this directory. The repository was last updated on October 6, 2026.

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