create-service

Generate Harness Service YAML for deployment types and artifact sources.

1|Updated Apr 16, 2026

Search Tags:#deployment automation #service creation #Harness #infrastructure management #YAML generation

Ready to run

npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill create-service-thisrohangupta

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: create-service
Source: https://github.com/thisrohangupta/cursor-harness-plugin/tree/main/skills/create-service
Command: npx skills add https://github.com/thisrohangupta/cursor-harness-plugin --skill create-service-thisrohangupta

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires harness-mcp-v2, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the creation of Harness Services, simplifying the process of defining and deploying services and infrastructure configurations. It supports multiple deployment types and artifact sources.

Core Features & Use Cases

Service Definition Generation: Automatically generate Harness Service YAML based on detected deployment type and artifact source.
Deployment Types: Supports Kubernetes, Helm, ECS, Serverless, SSH, and WinRm.
Artifact Sources: Utilizes various artifact sources including Docker Hub, ECR, GCR, ACR, Nexus, and S3.
Use Case: Ideal for users needing to create new Kubernetes services, define Helm charts, set up ECS services, or manage other types of deployment services quickly and efficiently.

Quick Start

Use the create-service skill to generate a service definition for a new Kubernetes service in your Harness project.

Frequently Asked Questions about create-service

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

FAQPage Schema

How do I generate a Harness Service YAML for Kubernetes deployments?▼

You can generate a Harness Service YAML for Kubernetes deployments by using an automation Skill that detects your deployment type and artifact source to automatically output the required configuration. This simplifies defining and deploying services.

What deployment types are supported when creating a Harness Service?▼

Creating a Harness Service supports Kubernetes, Helm, ECS, Serverless, SSH, and WinRm deployment types. The generation process automatically adapts the YAML output to match the specific deployment infrastructure you select.

Can I use Docker Hub and ECR as artifact sources for Harness Service creation?▼

Yes, you can use Docker Hub and ECR as artifact sources, along with GCR, ACR, Nexus, and S3. The service definition generation process incorporates these artifact sources directly into your Harness infrastructure configuration.

Do I need a Harness MCP v2 server to automate service creation?▼

Yes, you need the Harness MCP v2 server to automate service creation. This dependency is required for the Skill to interface with your Harness project and generate the service definition YAML successfully.

How do I automate the creation of ECS services and infrastructure configurations?▼

You can automate the creation of ECS services and infrastructure configurations by using the create-service automation process. It detects your ECS deployment type and generates the corresponding Harness Service YAML automatically.

What is the best way to define a new Helm chart service in Harness?▼

The best way to define a new Helm chart service in Harness is through deployment automation that generates the service YAML. This approach quickly establishes your infrastructure configuration by detecting the Helm deployment type.