CtrlK
BlogDocsLog inGet started
Tessl Logo

create-pipeline-v1

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.

72

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

78%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 highly actionable, well-structured body with executable YAML examples and properly offloaded reference material. The main weakness is redundancy: the v0-avoidance rules are restated in four places, inflating the token budget without adding information.

Suggestions

Consolidate the repeated 'never use v0 syntax' rules (currently in Instructions step 4, the v0/v1 differences table, Performance Notes, and Troubleshooting) into one canonical section and cross-reference it instead of restating.

Trim Performance Notes, which largely restates rules already in Instructions; keep only genuinely additional guidance there.

Add an explicit YAML-validation checkpoint in the generation workflow (e.g., 'validate structure against references/v1-spec-schema.md before presenting') to lift workflow_clarity from 4 to 5.

DimensionReasoningScore

Conciseness

Mostly efficient (domain-specific YAML examples, no generic concept explanations) but the same 'do not use v0 syntax' rules are repeated across Instructions step 4, the v0/v1 differences table, Performance Notes, and Troubleshooting, which could be tightened into a single canonical list.

3 / 5

Actionability

Fully executable copy-paste YAML examples cover the common cases -- CI, CD, matrix, parallel, approval, failure strategy, run/run-test/background/action/template steps -- matching the 'fully executable; specific examples cover common cases' anchor.

5 / 5

Workflow Clarity

A clear 6-step Instructions sequence plus an MCP verify-then-create flow with error recovery (harness_list project check, DUPLICATE_IDENTIFIER -> harness_update); minor validation gaps keep it just below the top anchor.

4 / 5

Progressive Disclosure

Clear overview with well-signaled one-level-deep references -- both references/v1-spec-schema.md and references/native-actions.md exist on disk and are explicitly pointed to for the full schema and action catalog, while teaching examples stay inline.

5 / 5

Total

17

/

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.

A strong, comprehensive description that explicitly covers what the skill does, when to use it, and how it differs from the v0 sibling skill. Trigger phrases are natural and well-enumerated, and third-person voice is maintained throughout.

DimensionReasoningScore

Specificity

Lists multiple concrete actions with comprehensive coverage -- CI stages (run, run-test, background), CD stages (K8s, Helm, ECS), approval, parallel, matrix/for/while, caching, volumes, templates -- matching the 'multiple specific concrete actions; comprehensive coverage' anchor.

5 / 5

Completeness

Clearly answers both 'what' (generate Harness v1 simplified Pipeline YAML with the listed features) and 'when' (explicit 'Use when...' clause with concrete trigger phrases), matching the top anchor exactly.

5 / 5

Trigger Term Quality

Explicit 'Trigger phrases: v1 pipeline, simplified pipeline, new pipeline format, create v1, modern pipeline syntax' plus 'Use when asked for a v1 pipeline...' gives comprehensive natural-term coverage with synonyms a user would actually say.

5 / 5

Distinctiveness Conflict Risk

Clear v1 niche with explicit disambiguation ('Do NOT use for v0/standard pipelines (use create-pipeline)') and distinct trigger phrases, giving minimal conflict risk.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

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.