create-template

Create and register Harness template YAML via MCP operations.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill create-template-harness
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-template
Source: https://github.com/harness/harness-skills/tree/main/skills/create-template
Command: npx skills add https://github.com/harness/harness-skills --skill create-template-harness

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates the creation and registration of Harness template YAML via MCP, reducing manual steps when building reusable pipeline components.

Core Features & Use Cases

  • Template types: Step, Stage, Pipeline, StepGroup
  • MCP integration: harness_create, harness_list, harness_update
  • Versioning and runtime inputs: supports versionLabel and <+input> placeholders for runtime configuration

Quick Start

Create a new template named My Template of type Step and publish it to MCP.

Frequently Asked Questions about create-template

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

FAQPage Schema
How do I create a Harness template YAML using MCP?

You can create a Harness template YAML using MCP by utilizing the harness_create operation to define and register Step, Stage, Pipeline, or StepGroup templates with versioning and runtime inputs.

What types of Harness pipeline templates can I automate with MCP?

You can automate the creation of Step, Stage, Pipeline, and StepGroup templates via MCP, embedding them into workflows with versioning and <+input> placeholders for runtime configuration.

How do I add runtime inputs to a Harness template via MCP?

You add runtime inputs to a Harness template via MCP by using <+input> placeholders within the template YAML structure, allowing for dynamic configuration when the template executes in a pipeline.

Can I update an existing Harness template YAML through MCP?

Yes, you can update an existing Harness template YAML through MCP by using the harness_update operation to modify registered components. You can also use harness_list to retrieve existing templates.

Does versioning work when creating Harness templates with MCP?

Versioning works when creating Harness templates with MCP by applying a versionLabel to the template YAML, ensuring reusable pipeline components are properly tracked and managed across workflows.

Why use MCP to manage Harness template YAML instead of manual steps?

Using MCP to manage Harness template YAML reduces manual steps when building reusable pipeline components, automating the registration process and ensuring standard operations for creating, listing, and updating templates.