CtrlK
BlogDocsLog inGet started
Tessl Logo

create-infrastructure

Generate Harness Infrastructure Definition YAML for deployment targets and create via MCP. Use when user says "create infrastructure", "infrastructure definition", "k8s cluster config", "deployment target", or wants to configure where workloads run.

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

76%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 highly actionable with executable templates and a clear step sequence, and is well-structured. The main weakness is workflow clarity: creating infrastructure via MCP is a resource-mutating operation whose prerequisite verification is advisory rather than an explicit validate-then-proceed checkpoint.

Suggestions

Promote the prerequisite check into an explicit validation step in the numbered Instructions (e.g., step 2 'Verify connector and environment exist; if missing, create them first') so the create step is gated on a concrete checkpoint.

Add a feedback loop in Troubleshooting for the create call (e.g., on CONNECTOR_NOT_FOUND/ENVIRONMENT_NOT_FOUND, create the missing resource then re-run harness_create) rather than only listing error causes.

De-duplicate the releaseName and connector/environment guidance so each note appears once in its most relevant section.

DimensionReasoningScore

Conciseness

Lean YAML templates with minimal prose and no concept over-explanation, but the `<+INFRA_KEY_SHORT_ID>` releaseName guidance and connector/environment prerequisite are each stated more than once.

4 / 5

Actionability

Provides copy-paste-ready executable YAML templates for each infrastructure type plus a concrete MCP call with named parameters and real worked examples covering the common cases.

5 / 5

Workflow Clarity

A clear 4-step sequence exists, but the verification ('Verify the referenced connector and environment exist before creating') is advisory prose rather than an explicit validation checkpoint with a feedback loop for an operation that creates resources.

3 / 5

Progressive Disclosure

Well-organized single-file structure with clear sections and one level of content; the eight inline templates are the core payload and reasonably belong inline, though the bulk could be split into reference files.

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 clearly states what the skill does and when to use it with concrete, natural trigger phrases in a third-person voice. Trigger coverage is good but could add a few more synonyms for the supported infrastructure types.

DimensionReasoningScore

Specificity

Names the domain plus two concrete actions ('Generate Harness Infrastructure Definition YAML' and 'create via MCP'), covering the core task with minor gaps in coverage rather than only minimal actions.

4 / 5

Completeness

Explicitly states both what it does ('Generate Harness Infrastructure Definition YAML... and create via MCP') and when to use it via a clear 'Use when...' clause with concrete trigger phrases.

5 / 5

Trigger Term Quality

Includes several natural quoted phrases users would say ('create infrastructure', 'infrastructure definition', 'k8s cluster config', 'deployment target') plus a synonym, but omits a few common variations like GKE/ECS/AKS.

4 / 5

Distinctiveness Conflict Risk

Targets a narrow Harness-specific niche ('Infrastructure Definition') with distinct trigger phrases and Harness MCP context, minimizing overlap with unrelated skills.

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.