create-pipeline-v1

Generate Harness v1 Pipeline YAML with flat structure and expressions.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Generates Harness v1 simplified Pipeline YAML configurations to streamline pipeline creation and ensure consistency with the v1 syntax.

Core Features & Use Cases

  • Generate v1 YAML pipelines with a flat structure and ${{ }} expressions for parameterization.
  • Optionally push the created pipeline to Harness via MCP in a single step.
  • Use for rapid bootstrap of CI/CD workflows and for educational or internal testing.

Quick Start

Create a v1 CI pipeline skeleton for a Node.js project.

Frequently Asked Questions about create-pipeline-v1

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

FAQPage Schema
How do I generate a Harness v1 pipeline YAML configuration?

Generate Harness v1 pipeline YAML by using a flat structure with the pipeline root, `${{ }}` expressions for parameterization, and script fields for run steps to ensure syntax consistency.

What is the correct YAML structure for a Harness v1 CI/CD pipeline?

A Harness v1 CI/CD pipeline uses a flat structure under the pipeline root, applies `${{ }}` expressions for variables, and defines script fields for execution steps.

Can I push a newly created v1 pipeline directly to Harness?

Yes, you can push the created v1 pipeline YAML directly to Harness via MCP in a single step after generation, streamlining the pipeline creation process.

Does this pipeline generation approach work for bootstrapping CI/CD workflows?

Yes, this approach is specifically suited for rapid bootstrap of CI/CD workflows and works well for educational or internal testing scenarios using simplified v1 YAML.

What distinguishes Harness v1 simplified YAML from other pipeline configurations?

Harness v1 simplified YAML enforces a flat structure, uses `${{ }}` expression syntax for parameterization, and conforms to the v1 spec by applying script fields for run steps.

When should I not use the flat structure for v1 pipeline creation?

Avoid using the flat v1 pipeline structure if your CI/CD workflow does not conform to the v1 spec or requires nested configurations beyond script fields and `${{ }}` expressions.