Name: create-service
Rating: 72.8 (1 reviews)
Author: harness

create-service

Generate Harness Service YAML for deployable workloads and create via MCP. Supports Kubernetes, Helm, ECS, Serverless, SSH, and WinRm deployment types with artifact sources from Docker Hub, ECR, GCR, ACR, Nexus, and S3. Use when asked to create a service, define a Kubernetes service, set up a Helm chart deployment, configure an ECS service, or define what gets deployed. Trigger phrases: create service, service definition, Kubernetes service, Helm service, ECS service, deployment service, artifact source.

Quality

89%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

78%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 concrete YAML and MCP guidance, but it is somewhat monolithic: bulk reference material is inlined rather than split into bundle files, and one validation step sits outside the numbered workflow. Tightening redundancy and extracting reference files would improve it.

Suggestions

Move the per-deployment-type YAML examples and the Artifact Source Types catalog into reference files under references/ (e.g., deployment-types.md, artifact-sources.md), keeping only the generic structure and detection rules inline in SKILL.md.

Promote connector-existence verification from 'Performance Notes' into an explicit numbered workflow step before 'Create via MCP' (e.g., step 4.5: verify connectorRefs via harness_list).

Remove or consolidate the generic 'Service Structure' Kubernetes example to eliminate overlap with the dedicated 'Kubernetes Service' section.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean reference YAML that assumes Claude's competence, but the generic 'Service Structure' example substantially duplicates the per-type Kubernetes section and could be trimmed.	4 / 5
Actionability	Provides copy-paste-ready YAML for each deployment type, concrete MCP tool calls with exact parameters (harness_create, resource_type 'service'), and specific file-pattern detection rules plus error-code troubleshooting.	5 / 5
Workflow Clarity	A clear five-step numbered sequence exists with a 'Confirm with user' checkpoint and a troubleshooting feedback loop, but connector-existence pre-validation is buried in 'Performance Notes' rather than integrated as an explicit workflow step.	4 / 5
Progressive Disclosure	The file is well-sectioned with clear headers, but no bundle files exist and all reference material (artifact-source catalog, per-type YAML) is inlined in SKILL.md with no one-level-deep references to split content.	3 / 5
	Total	16 / 20 Passed

Description

100%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 exemplary: it states concrete capabilities, enumerates supported deployment types and artifact sources, and provides explicit 'Use when' guidance with natural trigger phrases in third-person voice. No improvements needed.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions ('Generate Harness Service YAML', 'create via MCP') and comprehensively enumerates deployment types (Kubernetes, Helm, ECS, Serverless, SSH, WinRm) and artifact sources (Docker Hub, ECR, GCR, ACR, Nexus, S3).	5 / 5
Completeness	Explicitly answers both what ('Generate Harness Service YAML for deployable workloads and create via MCP') and when ('Use when asked to create a service...') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Provides comprehensive natural trigger phrases ('create service', 'service definition', 'Kubernetes service', 'Helm service', 'ECS service') including synonyms users would actually say, plus artifact-source keywords.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear Harness-specific niche with distinct triggers tied to platform deployment types and artifact registries, minimizing overlap with generic skills.	5 / 5
	Total	20 / 20 Passed

Validation

100%

Warnings & errors only

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
Path: plugins/claude/skills/create-service/SKILL.md
Commit: 23e9b8b

Reviewed: 11 days ago

Table of Contents

Discovery Implementation Validation

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.