Agent skill

Create Pipeline V1

by harness in harness/harness-skills

Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps.

Apache-2.0Auto-check passedDevOps & Cloud

Install Create Pipeline V1

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

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

GitHub CLI
$ gh skill install harness/harness-skills create-pipeline-v1 --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-pipeline-v1 .claude/skills/create-pipeline-v1 && 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-pipeline-v1
GitHub stars
115
Token cost
~3.1k tokens
SKILL.md length
687 words
Files
3 (incl. references)
Skills in repo
24
Repo updated
First seen
Licence
Apache-2.0

At a glance

Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps.

  • Works in 6 steps: Confirm v1 format - User must… → Clarify requirements - Pipeline type… → Consult the spec reference - Use… → …
  • Asked for a v1 pipeline
  • SKILL.md covers Instructions, v1 Key Differences from v0, Pipeline Structure and Stages, plus 11 more sections
  • Calls docker; reaches acme.com

What it does

Create Pipeline V1 is an agent skill from harness/harness-skills. Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps. Supports CI stages (run, run-test, background), CD stages (service/environment with action steps for K8s, Helm, ECS), approval (stage-level and inline), parallel execution, matrix/for/while strategies, caching, volumes, and templates. Use when asked for a v1 pipeline, simplified pipeline, new pipeline format, or when user specifically requests v1 syntax. Do NOT use for…

Its SKILL.md is about 3.1k tokens, which your agent loads only when the skill is triggered. The skill folder holds 3 other files, including reference files (for example `references/native-actions.md` and `references/v1-spec-schema.md`). Compatibility notes: Requires Harness MCP v2 server (harness-mcp-v2)

It sits in DevOps & Cloud, covering Container orchestration and Caching. It works with Kubernetes and Docker. 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

  • Asked for a v1 pipeline
  • Simplified pipeline
  • New pipeline format
  • User specifically requests v1 syntax

Example prompts

  • “/create-pipeline-v1”

Requirements

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

Workflow steps

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

  1. Confirm v1 format - User must specifically want v1 syntax. Default to v0 (/create-pipeline) if unclear.
  2. Clarify requirements - Pipeline type (CI, CD, or both), language/framework, deployment target
  3. Consult the spec reference - Use references/v1-spec-schema.md for the complete v1 schema, step types, action catalog, and examples
  4. Select native actions - Always prefer native action and template steps over run: steps. Consult references/native-actions.md for the full…
  5. Generate v1 YAML using flat structure, ${{ }} expressions, script field for run steps, and action/template steps for deployments
  6. Optionally create via MCP using harness_create with resource_type pipeline

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

    Shell commands in SKILL.md call:

    • docker

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

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • acme.com

    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 Pipeline V1 loads about 3.1k tokens when it runs, and up to ~10k if it reads all its reference files. Until then it costs about 172 tokens; SKILL.md has 687 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~172
When it runs · the whole SKILL.md, loaded when a task matches
~3.1k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~10k

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). 687 words, ~3,097 tokens.

Download SKILL.mdSave it as .claude/skills/create-pipeline-v1/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.
name
create-pipeline-v1
description
Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps. Supports CI stages (run, run-test, background), CD stages (service/environment with action steps for K8s, Helm, ECS), approval (stage-level and inline), parallel execution, matrix/for/while strategies, caching, volumes, and templates. Use when asked for a v1 pipeline, simplified pipeline, new pipeline format, or when user specifically requests v1 syntax. Do NOT use for v0/standard pipelines (use create-pipeline). Trigger phrases: v1 pipeline, simplified pipeline, new pipeline format, create v1, modern pipeline syntax.
compatibility
Requires Harness MCP v2 server (harness-mcp-v2)
metadata.author
Harness
metadata.version
3.1.0
metadata.mcp-server
harness-mcp-v2
license
Apache-2.0

Create Pipeline v1

Generate Harness v1 simplified Pipeline YAML and optionally push to Harness via MCP.

Alpha: This skill is currently in internal testing only.

Instructions

  1. Confirm v1 format - User must specifically want v1 syntax. Default to v0 (/create-pipeline) if unclear.
  2. Clarify requirements - Pipeline type (CI, CD, or both), language/framework, deployment target
  3. Consult the spec reference - Use references/v1-spec-schema.md for the complete v1 schema, step types, action catalog, and examples
  4. Select native actions - Always prefer native action and template steps over run: steps. Consult references/native-actions.md for the full mapping. Key rules:
    • Docker build/push → use template: uses: buildAndPushToDocker / buildAndPushToECR / buildAndPushToGAR (never run: docker build && docker push)
    • K8s deploy → use action: uses: kubernetes-rolling-deploy or template: uses: k8sRollingDeployStep (never run: kubectl apply)
    • Helm deploy → use action: uses: helm-deploy or template: uses: helmDeployBasicStep (never run: helm upgrade --install)
    • ECS deploy → use template: uses: ecsBluegreenDeployStep (never run: aws ecs update-service)
    • Terraform → use template: uses: terraformStep (never run: terraform apply)
    • Security scanning → use native STO templates (gitleaksStep, banditStep, sbomOrchestrationStep)
    • Uploads → use template: uses: uploadArtifactsToS3 / uploadArtifactsToGCS (never run: aws s3 cp)
    • Approvals → use approval: uses: harness or approval: uses: jira (never polling scripts)
    • Ticketing → use action: uses: jira-create / snow-create (never run: curl)
    • HTTP requests → use action: uses: http or template: uses: httpStep (never run: curl)
    • Use run: steps only for custom build/test/lint commands with no native equivalent
  5. Generate v1 YAML using flat structure, ${{ }} expressions, script field for run steps, and action/template steps for deployments
  6. Optionally create via MCP using harness_create with resource_type pipeline

v1 Key Differences from v0

v0 Syntaxv1 Syntax
<+variable> expressions${{ variable }} expressions
type: CI / type: Deployment stage typesFlat stages -- no type field
command: field in Run stepsscript: field in run: steps
Native steps (K8sRollingDeploy, HelmDeploy)Action steps (action: uses: kubernetes-rolling-deploy)
failureStrategies:on-failure:
HarnessApproval step typeapproval: uses: harness (stage-level or inline)
Deep nesting (spec: execution: steps:)Flat structure (steps:)
strategy: matrix: under stage specstrategy: matrix: directly on stage or step

Pipeline Structure

yaml
pipeline:
  name: My Pipeline
  repo:                          # optional: repository config
    connector: account.github
    name: myorg/my-repo
  clone:                         # optional: clone config
    depth: 1
  on:                            # optional: event triggers
  - push:
      branches: [main]
  env:                           # optional: global env vars
    NODE_ENV: production
  inputs:                        # optional: pipeline inputs
    branch:
      type: string
      default: main
  stages:
  - name: build
    steps:
    - run:
        script: go build

No version:, kind:, or spec: wrapper -- pipeline: is the root key.

Stages

Stages have no type field. Their purpose is determined by their keys.

CI Stage
yaml
- name: build
  runtime: cloud
  platform:
    os: linux
    arch: arm
  cache:
    path: node_modules
    key: npm.${{ branch }}
  steps:
  - run:
      script: npm ci
Deployment Stage
yaml
- name: deploy
  service: my-service
  environment: staging
  steps:
  - action:
      uses: kubernetes-rolling-deploy
      with:
        dry-run: false
Approval (stage-level)
yaml
- approval:
    uses: harness
    with:
      timeout: 30m
      message: "Approve deployment?"
      groups: [admins, ops]
      min-approvers: 1

Step Types

Run Step

Uses script: field (not command: or run:).

yaml
# long syntax
- run:
    script: npm test

# short syntax
- run: npm test

# with container
- run:
    container: node:18
    script: npm test

# with shell and env
- run:
    shell: bash
    script: |
      npm ci
      npm test
    env:
      NODE_ENV: test

# with output variables
- id: build
  run:
    script: echo "TAG=v1" >> $HARNESS_OUTPUT
    output: [TAG]
Run Test Step
yaml
- run-test:
    container: maven
    script: mvn test
    report:
      type: junit
      path: target/surefire-reports/*.xml
    splitting:
      concurrency: 4
Action Step

Actions replace v0 native steps. See references/v1-spec-schema.md for the full action catalog.

yaml
# Kubernetes deploy
- action:
    uses: kubernetes-rolling-deploy
    with:
      dry-run: false

# Helm deploy
- action:
    uses: helm-deploy
    with:
      timeout: 10m

# Terraform plan
- action:
    uses: terraform-plan
    with:
      command: apply
      aws-provider: account.aws_connector

# HTTP request
- action:
    uses: http
    with:
      method: GET
      endpoint: https://acme.com
Background Step
yaml
- background:
    container: redis
- run:
    script: npm test
Template Step
yaml
- template:
    uses: account.docker@1.0.0
    with:
      push: true
      tags: latest
Approval Step (inline)
yaml
- approval:
    uses: jira
    with:
      connector: account.jira
      project: PROJ

Parallel and Group

yaml
# parallel steps
- parallel:
    steps:
    - run:
        script: npm run lint
    - run:
        script: npm test

# parallel stages
- parallel:
    stages:
    - steps:
      - run: go test
    - steps:
      - run: npm test

# step group
- group:
    steps:
    - run:
        script: go build
    - run:
        script: go test

Strategy

yaml
# matrix (stage-level)
- strategy:
    matrix:
      node: [16, 18, 20]
      os: [linux, macos]
    max-parallel: 3
  steps:
  - run:
      container: node:${{ matrix.node }}
      script: npm test

# matrix (step-level)
- strategy:
    matrix:
      go: [1.19, 1.20, 1.21]
  run:
    container: golang:${{ matrix.go }}
    script: go test

Failure Strategy

yaml
# step-level
- run:
    script: go test
  on-failure:
    errors: all
    action: ignore       # abort, ignore, retry, fail, success

# retry with attempts
- run:
    script: go test
  on-failure:
    errors: [unknown]
    action:
      retry:
        attempts: 5
        interval: 10s
        failure-action: fail

# stage-level
- steps:
  - run:
      script: go test
  on-failure:
    errors: all
    action: abort

Conditional Execution

yaml
# stage conditional
- if: ${{ branch == "main" }}
  steps:
  - run:
      script: deploy.sh

# step conditional
- if: ${{ branch == "main" }}
  run:
    script: deploy.sh

Complete CI Example

yaml
pipeline:
  repo:
    connector: account.github
    name: myorg/my-app
  clone:
    depth: 1
  on:
  - push:
      branches: [main]
  - pull_request:
      branches: [main]
  stages:
  - name: build-and-test
    runtime: cloud
    platform:
      os: linux
      arch: arm
    cache:
      path: node_modules
      key: npm.${{ branch }}
    steps:
    - run:
        script: npm ci
    - parallel:
        steps:
        - run:
            script: npm run lint
        - run-test:
            script: npm test
            report:
              type: junit
              path: junit.xml
    - action:
        uses: docker-build-push
        with:
          connector: dockerhub
          repo: myorg/my-app
          tags: [${{ pipeline.sequenceId }}, latest]

Complete CD Example

yaml
pipeline:
  inputs:
    skip_dry_run:
      type: boolean
      default: false
  stages:
  - name: deploy-staging
    service: petstore
    environment: staging
    steps:
    - action:
        uses: manifest-download
    - action:
        uses: manifest-bake
    - action:
        uses: kubernetes-rolling-deploy
        with:
          dry-run: ${{ inputs.skip_dry_run }}
  - approval:
      uses: harness
      with:
        timeout: 1d
        message: "Approve production deployment?"
        groups: [prod-approvers]
        min-approvers: 1
  - name: deploy-prod
    service: petstore
    environment: prod
    steps:
    - action:
        uses: manifest-download
    - action:
        uses: manifest-bake
    - action:
        uses: kubernetes-rolling-deploy
        with:
          dry-run: false
Show full SKILL.md (281 more words)Show less

Creating via MCP

  1. Verify the project exists — List projects with harness_list (resource_type: project, org_id) to confirm. If the project does not exist, create it first with harness_create (resource_type: project, body: { identifier, name }) or ask the user.
  2. Create the pipeline — Use harness_create with the v1 pipeline YAML serialized as a yamlPipeline string in the body. Do not pass a nested JSON pipeline object; it causes serialization errors.
Call MCP tool: harness_create
Parameters:
  resource_type: "pipeline"
  org_id: "<organization>"
  project_id: "<project>"
  body: { yamlPipeline: "<full v1 pipeline YAML string, including 'pipeline:' root key>" }

Examples

Create a v1 CI pipeline
/create-pipeline-v1
Create a v1 CI pipeline for a Node.js app with caching, parallel lint and test, and Docker push
Create a v1 deployment pipeline
/create-pipeline-v1
Create a v1 Kubernetes deployment pipeline with staging approval and production stages
Create a v1 matrix build
/create-pipeline-v1
Create a v1 pipeline that tests across Go 1.19, 1.20, and 1.21 using matrix strategy

Performance Notes

  • Always check references/native-actions.md before using a run: step. Native actions provide better error handling, rollback support, and UI integration.
  • Always consult references/v1-spec-schema.md for the complete v1 spec before generating YAML.
  • Use script: field in run steps, never command: or run: as the field name.
  • Use action: uses: or template: uses: for deployments, never v0 native step types like K8sRollingDeploy.
  • Do not mix v0 and v1 syntax. No <+...> expressions, no type: on stages, no spec: wrapper.
  • Validate all expressions use ${{ }} syntax before presenting.

Troubleshooting

Common v1 Syntax Errors
  • Using <+...> instead of ${{ ... }} expressions
  • Adding type: field on stages (v1 stages have no type)
  • Using command: or run: as the field name instead of script:
  • Wrapping pipeline in version:, kind:, spec: (v1 uses bare pipeline:)
  • Using v0 step types (K8sRollingDeploy) instead of actions (action: uses: kubernetes-rolling-deploy)
  • Using failureStrategies: instead of on-failure:
MCP Errors
  • Project not found — Verify the project exists with harness_list (resource_type: project, org_id). Create it first or confirm org_id/project_id are correct.
  • Missing required fields for pipeline: pipeline — Pass the body as { yamlPipeline: "<full v1 pipeline YAML string>" } instead of a nested JSON pipeline object.
  • DUPLICATE_IDENTIFIER — Pipeline exists; use harness_update
  • INVALID_REQUEST — Check YAML structure matches v1 schema

© 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

SKILL.md and 2 other files (references) in skills/create-pipeline-v1 of harness/harness-skills.

  • SKILL.md
  • references/native-actions.md
  • references/v1-spec-schema.md

Open the folder on GitHubat commit c25faee

Compare with similar skills

Create Pipeline V1 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 Pipeline V1 compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Create Pipeline V1 this skillharness/harness-skills115—~3.1kAutomated safety check: PassApache-2.0
LangBot Deployment Guidelangbot-app/LangBot18k—~1.2kAutomated safety check: NotesApache-2.0
Build Openshell Mxc WindowsNVIDIA/OpenShell16k—~4.9kAutomated safety check: PassApache-2.0
Devopsnicepkg/auto-company1942 repos~814Automated safety check: PassMIT
Debug Openshell ClusterNVIDIA/OpenShell16k—~19kAutomated safety check: NotesApache-2.0
Deepseek Harness Dockerrunzhliu/deepseek-harness-docker110—~2.7kAutomated safety check: NotesMIT

Similar skills

  • LangBot Deployment Guide

    langbot-app/LangBot

    Deploys and configures a LangBot instance with Docker Compose or Kubernetes, covering config.yaml, the Box sandbox runtime, the plugin runtime and the global API key.

    18k GitHub stars~1.2k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Official

    Maintain and validate OpenShell's build-only Windows MSVC lane for x64 and ARM64.

    16k GitHub stars~4.9k tokensUpdated today
    DevOps & CloudAuto-check passed
  • Devops

    nicepkg/auto-company

    Deploy to Cloudflare (Workers, R2, D1), Docker, GCP (Cloud Run, GKE), Kubernetes (kubectl, Helm).

    194 GitHub starsUsed in 2 repos~814 tokens
    DevOps & CloudAuto-check passed
  • Debug Openshell Cluster

    NVIDIA/OpenShell

    Official

    Debug why an OpenShell gateway deployment is unhealthy, unreachable, or unable to create sandboxes.

    16k GitHub stars~19k tokensUpdated today
    DevOps & CloudAuto-check: notes
  • Deepseek Harness Docker

    runzhliu/deepseek-harness-docker

    Deploy, configure, verify, upgrade, and troubleshoot DeepSeek Harness with the community Docker, Docker Compose, rootless Podman, and Helm runtime, including the built-in Chromium/noVNC browser…

    110 GitHub stars~2.7k tokensUpdated yesterday
    DevOps & CloudAuto-check: notes
  • Deep static code review of an mql provider for logic errors, nil-handling bugs, pagination truncation, caching/id collisions, and other defects that silently give users wrong data.

    412 GitHub stars~2.9k tokensUpdated today
    DevOps & CloudAuto-check passed

More from harness/harness-skills

All 24 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 3 days ago
    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 3 days ago
    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 3 days ago
    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 3 days ago
    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 3 days ago
    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 3 days ago
    Auto-check passed

Categories

Questions about Create Pipeline V1

What does Create Pipeline V1 do?

Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps. Create Pipeline V1 is an agent skill from harness/harness-skills. Generate Harness v1 simplified Pipeline YAML using the new concise syntax with flat structure, ${{ }} expressions, script field, and action steps.

When should I use Create Pipeline V1?

Create Pipeline V1 fits situations like: asked for a v1 pipeline; simplified pipeline; new pipeline format; user specifically requests v1 syntax.

How do I install Create Pipeline V1 in Claude Code?

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

How do I install Create Pipeline V1 in Codex?

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

Can I use Create Pipeline V1 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-pipeline-v1 -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-pipeline-v1, .gemini/skills/create-pipeline-v1, .github/skills/create-pipeline-v1 and .opencode/skills/create-pipeline-v1 in your project.

What does Create Pipeline V1 need to run?

Going by SKILL.md and its folder, Create Pipeline V1 needs the command-line tools its instructions call (docker). Our summary lists: Node.js; Docker. Compatibility (from SKILL.md): Requires Harness MCP v2 server (harness-mcp-v2).

Does Create Pipeline V1 access the network?

SKILL.md names 1 domain. In commands or code: acme.com; the agent is likely to contact it when it follows the instructions. This is read from the text; nothing was executed.

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

Create Pipeline V1 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 Pipeline V1 use?

About 3.1k tokens (SKILL.md is roughly 12k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 7.4k tokens, read only when the agent opens those files.

What are the alternatives to Create Pipeline V1?

Skills that share tags, products or a category with Create Pipeline V1: LangBot Deployment Guide (langbot-app/LangBot, 18k stars), Build Openshell Mxc Windows (NVIDIA/OpenShell, 16k stars), Devops (nicepkg/auto-company, 194 stars) and Debug Openshell Cluster (NVIDIA/OpenShell, 16k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Create Pipeline V1?

harness (a GitHub organization) maintains it in harness/harness-skills, which has 115 GitHub stars. The repository holds 24 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.