CtrlK
BlogDocsLog inGet started
Tessl Logo

create-environment

Generate Harness Environment YAML for deployment targets and create via MCP. Supports PreProduction and Production types with environment variables, manifest overrides, and multi-environment setup (dev, staging, prod). Use when asked to create an environment, set up staging, configure production, define deployment targets, or manage environment overrides. Trigger phrases: create environment, deployment environment, setup dev, setup staging, setup production, environment variables, environment overrides.

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 content is highly actionable with executable YAML and concrete MCP calls, well-organized into clear sections. Its main weakness is workflow clarity: a batch and production-affecting operation lacks explicit validation checkpoints sequenced into the workflow, capping that dimension.

Suggestions

Add an explicit validation step to the Instructions workflow (e.g. '5. Verify identifiers are unique / call harness_list before creating') with a fix-and-retry loop so batch and production-affecting creation has a real checkpoint.

Trim the 'Environment Types' section, since PreProduction/Production semantics are already covered by step 1 and the YAML comment, to remove redundancy.

Move the 'verify override paths exist' and 'distinct variable values per environment' guidance from Performance Notes into the workflow as numbered validation steps rather than advisory notes.

DimensionReasoningScore

Conciseness

Body is efficient: mostly executable YAML and terse bullets with no explanatory padding of concepts Claude knows. Minor redundancy — the 'Environment Types' section restates step 1 and the YAML comment — keeps it from a 5.

4 / 5

Actionability

Fully executable, copy-paste-ready YAML examples plus concrete MCP tool calls with exact parameters (harness_create / harness_list with resource_type, org_id, project_id, body) and a concrete troubleshooting remediation (DUPLICATE_IDENTIFIER -> use harness_update) covering the common cases.

5 / 5

Workflow Clarity

A clear 4-step sequence exists, but this is a batch (multi-environment dev/staging/prod) and production-affecting operation with no explicit validation checkpoint sequenced into the workflow (the 'verify override paths / distinct values' guidance lives in advisory notes, not the workflow), so the destructive/batch cap of 3 applies.

3 / 5

Progressive Disclosure

No bundle files exist (references/scripts/assets absent) and the body is well-organized into clearly headed sections (Instructions, Environment Structure, Multi-Environment Setup, Creating via MCP, Examples, Performance Notes, Troubleshooting); not a 5 only because some inline content is slightly beyond overview level.

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 specific, well-structured, and explicitly covers both what the skill does and when to use it, with a dedicated trigger-phrase list. Minor specificity gaps (no list/update actions) keep it just below a perfect specificity score.

DimensionReasoningScore

Specificity

Lists several concrete actions ('Generate Harness Environment YAML', 'create via MCP', 'Supports PreProduction and Production types', 'environment variables, manifest overrides', 'multi-environment setup (dev, staging, prod)') with minor coverage gaps (no mention of listing or updating environments).

4 / 5

Completeness

Explicitly answers both 'what' (generate Harness Environment YAML for deployment targets and create via MCP, supporting types/variables/overrides/multi-env) and 'when' (concrete 'Use when asked to create an environment, set up staging, configure production, define deployment targets, or manage environment overrides') with concrete trigger phrases.

5 / 5

Trigger Term Quality

Provides an explicit 'Trigger phrases' list ('create environment, deployment environment, setup dev, setup staging, setup production, environment variables, environment overrides') plus natural 'Use when...' scenarios; good coverage with a few synonyms (e.g. QA) missing, so not a 5.

4 / 5

Distinctiveness Conflict Risk

'Harness Environment YAML' is a clear niche with triggers scoped to environment creation/setup, giving minimal conflict risk with other 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.