CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pipeline

Generate Harness v0 Pipeline YAML for CI/CD workflows and create them via MCP. Supports CI stages (build, test, Docker push), CD stages (Kubernetes, Helm, ECS, serverless), approval gates, parallel execution, matrix strategies, and failure rollback. Use when asked to create a pipeline, build pipeline, deployment pipeline, CI/CD workflow, or set up Harness pipelines. Do NOT use for v1 simplified pipelines (use create-pipeline-v1). Trigger phrases: create pipeline, build pipeline, deployment pipeline, CI/CD, Harness pipeline, Kubernetes deploy pipeline.

75

Quality

94%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

88%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A strong, highly actionable skill body with executable YAML, a well-sequenced validated workflow, and good reference structure. The only notable gaps are minor conciseness redundancy between Instructions and Troubleshooting, and an unreferenced schema bundle file.

Suggestions

Link to references/v0-pipeline-schema.md from the body (e.g., in the Pipeline Structure section) so the existing bundle file is discoverable rather than orphaned.

Consolidate the validation rules duplicated between the Instructions step 4 and the Troubleshooting section — reference one from the other instead of repeating the regex and failureStrategies rules verbatim.

Trim or fold the Performance Notes section, which largely restates rules already stated in Instructions (e.g., 'check native-steps.md before using Run', 'verify project exists').

DimensionReasoningScore

Conciseness

Mostly lean and efficient — it provides executable YAML templates and rules without explaining CI/CD, Docker, or Kubernetes basics — but the Troubleshooting and Performance Notes sections restate validation rules already given in Instructions, a minor redundancy that could be trimmed.

4 / 5

Actionability

Fully executable: concrete YAML blocks for every stage/step type, specific native step names (BuildAndPushDockerRegistry, K8sRollingDeploy, HarnessApproval), and explicit MCP tool calls with parameters, plus copy-paste-ready complete CI and CD examples covering the common cases.

5 / 5

Workflow Clarity

A clear 5-step numbered workflow (Analyze → Clarify → Select steps → Generate → Create) with explicit validation checkpoints (verify project exists, validate connectors, failureStrategies requirement, identifier/name regexes) and a Troubleshooting section providing error-message-to-fix feedback loops for the create operation.

5 / 5

Progressive Disclosure

SKILL.md acts as an overview with clearly signaled one-level-deep references to real files (codebase-analysis.md, native-steps.md), keeping the 300+ step catalog out of the body — but references/v0-pipeline-schema.md exists as a bundle file that is never referenced from the body, a minor organization gap.

4 / 5

Total

18

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: concrete capabilities, comprehensive natural trigger phrases, explicit what-and-when guidance, and a clear disambiguation boundary against the v1 variant. No meaningful weaknesses.

DimensionReasoningScore

Specificity

Lists multiple concrete actions ('Generate Harness v0 Pipeline YAML', 'create them via MCP') plus an enumerated capability set (CI/CD stages, approval gates, parallel execution, matrix strategies, failure rollback) — comprehensive coverage of what the skill does.

5 / 5

Completeness

Clearly answers 'what' (generate YAML, create via MCP, supported stage types) and 'when' (explicit 'Use when asked to create a pipeline, build pipeline...' clause) with concrete trigger phrases.

5 / 5

Trigger Term Quality

An explicit 'Trigger phrases:' clause covers natural terms users would say ('create pipeline', 'build pipeline', 'deployment pipeline', 'CI/CD', 'Harness pipeline', 'Kubernetes deploy pipeline') including synonyms.

5 / 5

Distinctiveness Conflict Risk

A clear Harness v0 niche with an explicit negative boundary ('Do NOT use for v1 simplified pipelines (use create-pipeline-v1)') keeps conflict risk minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

skill_md_line_count

SKILL.md is long (601 lines); consider splitting into references/ and linking

Warning

Total

15

/

16

Passed

Repository
harness/harness-ai
Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.