CtrlK
BlogDocsLog inGet started
Tessl Logo

create-template

Generate Harness v0 Template YAML for reusable pipeline components (Step, Stage, Pipeline, StepGroup) and create them via MCP. Use when asked to create a template, build a step template, stage template, pipeline template, or reusable step. Do NOT use for checking template usage or references (use template-usage instead). Trigger phrases: create template, step template, stage template, pipeline template, reusable step, template YAML.

68

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

65%

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

The content is highly actionable with executable YAML and concrete MCP calls, and it is reasonably concise. Workflow sequencing and validation feedback loops are present but only implicit against the documented error cases, and progressive disclosure would benefit from splitting the extensive template examples into referenced bundle files.

Suggestions

Add an explicit validate-fix-retry loop after creation: on DUPLICATE_IDENTIFIER or INVALID_VERSION, update with a new unique versionLabel and re-run harness_create/harness_update before proceeding.

Move the four full template YAML examples into a references/ file (e.g. references/templates.md) and keep only the generic structure plus one worked example inline, so SKILL.md stays a lean overview with one-level-deep navigation.

Tighten the 'Template Types' bullet list and the generic 'Template Structure' skeleton since their content is already demonstrated by the typed examples below.

DimensionReasoningScore

Conciseness

The body is largely efficient and example-driven, but four near-complete template YAML blocks plus a generic 'Template Structure' skeleton restate overlapping scaffolding, and the 'Template Types' list repeats what the intro already conveyed — it could be tightened without losing clarity.

2 / 3

Actionability

It provides complete, copy-paste-ready YAML for every template type and concrete MCP tool invocations (harness_create, harness_update, harness_list) with named parameters and placeholder values, matching the fully-executable anchor.

3 / 3

Workflow Clarity

The numbered Instructions list gives a clear sequence and includes a 'Verify creation using harness_list' checkpoint, but creation/update are batch-style mutations with only an implicit verify step and no validate-fix-retry loop for the documented DUPLICATE_IDENTIFIER/INVALID_VERSION errors, capping it at 2.

2 / 3

Progressive Disclosure

The body is well-organized into clearly headed sections, but everything is inlined into SKILL.md with no bundle references (references/, scripts/, assets/ are absent); for a skill of this depth, the four full template examples and troubleshooting reference could be split out for clearer one-level-deep navigation.

2 / 3

Total

9

/

12

Passed

Description

100%

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

The description is specific, action-oriented, and clearly separates its scope from the sibling template-usage skill via an explicit exclusion clause. It covers both what the skill does and when to use it with concrete trigger phrases.

DimensionReasoningScore

Specificity

Multiple concrete actions are listed — 'Generate Harness v0 Template YAML for reusable pipeline components (Step, Stage, Pipeline, StepGroup) and create them via MCP' — matching the rubric's top anchor for naming several specific concrete actions.

3 / 3

Completeness

It states both what it does (generate template YAML and create via MCP) and when to use it with an explicit 'Use when asked to create a template...' clause plus a 'Do NOT use for...' exclusion, satisfying both the 'what' and 'when' anchors.

3 / 3

Trigger Term Quality

Explicit 'Trigger phrases' list natural terms a user would say ('create template, step template, stage template, pipeline template, reusable step, template YAML'), giving good coverage of common phrasings.

3 / 3

Distinctiveness Conflict Risk

A clear niche (Harness template creation) with distinct triggers and an explicit disambiguation ('Do NOT use for checking template usage or references (use template-usage instead)') makes it unlikely to trigger the wrong skill.

3 / 3

Total

12

/

12

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.