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.

72

Quality

88%

Does it follow best practices?

Impact

No eval scenarios have been run

SecuritybySnyk

Passed

No known issues

SKILL.md
Quality
Evals
Security

Quality

Content

77%

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

This is a solid, actionable skill with complete YAML examples for all four Harness template types and clear MCP tool usage. The workflow is well-sequenced with a verification step. The main weakness is that the content is somewhat long for a single SKILL.md—the four full template examples plus troubleshooting could be split into supporting files for better progressive disclosure.

Suggestions

Move the detailed template type examples (Step, Stage, Pipeline, StepGroup YAML blocks) into a separate TEMPLATES_REFERENCE.md file and reference it from the main skill

Remove the 'Examples' section at the bottom as it merely restates what the template YAML blocks already demonstrate, adding no new information

DimensionReasoningScore

Conciseness

The content is mostly efficient with good YAML examples, but it's quite long with some redundancy (e.g., the 'Examples' section just restates what the templates above already demonstrate, and 'Performance Notes' contains obvious advice like 'mark configurable fields with <+input>' which is already covered). The four full template examples are borderline—useful as reference but could be trimmed.

2 / 3

Actionability

Provides complete, copy-paste ready YAML for all four template types, concrete MCP tool calls with specific parameters, and clear examples of runtime inputs and template referencing. Every section gives specific, executable guidance.

3 / 3

Workflow Clarity

The Instructions section provides a clear 5-step sequence including determination, generation, creation via MCP, and verification via harness_list. The troubleshooting section provides error recovery guidance for common failures like DUPLICATE_IDENTIFIER.

3 / 3

Progressive Disclosure

The content is well-organized with clear section headers, but it's a monolithic file with ~180 lines of inline YAML examples that could benefit from being split into separate reference files. No bundle files are provided, and no external references are used despite the content length warranting it.

2 / 3

Total

10

/

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.

This is a strong skill description that excels across all dimensions. It provides specific capabilities, comprehensive trigger terms, explicit 'Use when' and 'Do NOT use' guidance, and clear boundaries against related skills. The inclusion of both positive triggers and negative boundaries (template-usage) is particularly effective for disambiguation.

DimensionReasoningScore

Specificity

Lists multiple specific concrete actions: 'Generate Harness v0 Template YAML', 'reusable pipeline components (Step, Stage, Pipeline, StepGroup)', and 'create them via MCP'. The component types are explicitly enumerated.

3 / 3

Completeness

Clearly answers both 'what' (generate Harness v0 Template YAML for reusable pipeline components and create via MCP) and 'when' (explicit 'Use when...' clause with trigger phrases). Also includes a 'Do NOT use' boundary condition which adds clarity.

3 / 3

Trigger Term Quality

Excellent coverage of natural trigger terms users would say: 'create template', 'step template', 'stage template', 'pipeline template', 'reusable step', 'template YAML'. These are explicitly listed and match how users would naturally phrase requests.

3 / 3

Distinctiveness Conflict Risk

Highly distinctive with clear niche (Harness v0 Template YAML), explicit boundary against a related skill ('use template-usage instead' for checking references), and specific trigger phrases that minimize overlap with other skills.

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.

Validation11 / 11 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.