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

81%

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

75%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.

The body is actionable and well-structured, giving executable YAML and concrete MCP calls plus a verification step and troubleshooting map. It is slightly verbose where the generic structure example overlaps the typed examples, and lacks an explicit retry loop for creation failures.

Suggestions

Add a short fix-and-retry feedback loop after the verify step (e.g., on DUPLICATE_IDENTIFIER, bump versionLabel and re-run harness_create) to push workflow_clarity to 5.

Remove or merge the generic 'Template Structure' example into the four typed examples to reduce redundancy and tighten conciseness.

Consider extracting the four full template YAML examples into a references/ file referenced one level deep from the body to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly lean — YAML examples and brief instructional steps with no padding about what YAML or templates are; the generic 'Template Structure' example partially overlaps with the four typed examples that follow, which could be trimmed.

4 / 5

Actionability

Provides complete, copy-paste-ready YAML for each template type and concrete MCP tool calls (harness_create/harness_update/harness_list) with parameter blocks; falls short of 5 because some spec bodies use '<+input>' placeholders and 'spec: ...' ellipses.

4 / 5

Workflow Clarity

A clear 5-step sequence ending in an explicit verification checkpoint ('Verify creation using harness_list'), with a Troubleshooting section mapping error codes; not a 5 because there is no explicit fix-and-retry feedback loop for creation errors like DUPLICATE_IDENTIFIER.

4 / 5

Progressive Disclosure

Well-organized into clearly headed sections with no nested references and no bundle files present; the four full inline template examples are substantial content that could optionally live in separate reference files, keeping it just below 5.

4 / 5

Total

16

/

20

Passed

Description

87%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.

The description is strong: it states concrete capabilities, gives explicit 'Use when' triggers plus a dedicated trigger-phrase list, and draws a clear boundary against a sibling skill. Minor room for more granular action verbs and synonyms, but it cleanly answers what and when.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Generate Harness v0 Template YAML', 'create them via MCP') and enumerates the four component types (Step, Stage, Pipeline, StepGroup); falls short of 5 because the action set is essentially generate+create rather than many granular operations.

4 / 5

Completeness

Explicitly answers both what ('Generate Harness v0 Template YAML... and create them via MCP') and when ('Use when asked to create a template...') with concrete trigger phrases and a negative boundary clause.

5 / 5

Trigger Term Quality

Provides an explicit trigger-phrase list ('create template, step template, stage template, pipeline template, reusable step, template YAML') with good natural-term coverage; not a 5 because it lacks synonyms/file extensions beyond the enumerated set.

4 / 5

Distinctiveness Conflict Risk

Clear niche with explicit disambiguation ('Do NOT use for checking template usage or references (use template-usage instead)') minimizing conflict with the sibling template-usage skill.

5 / 5

Total

18

/

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.

Validation — 16 / 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.