Name: create-trigger
Rating: 65.60000000000001 (1 reviews)
Author: harness

create-trigger

Generate Harness Trigger YAML for automated pipeline execution and create via MCP. Use when user says "create trigger", "webhook trigger", "cron trigger", "scheduled build", "artifact trigger", or wants pipelines to run automatically.

Quality

77%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./plugins/claude/skills/create-trigger/SKILL.md

Quality

Content

64%

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 excellent YAML templates covering all major trigger types and concrete MCP tool usage. Its main weaknesses are the monolithic structure (all templates inline rather than referenced) and the lack of explicit validation/feedback loops in the workflow steps. Minor verbosity in the examples and performance notes sections could be trimmed.

Suggestions

Integrate a validation feedback loop into the workflow: after step 4 (create via MCP), add an explicit step to verify with harness_get and a retry path if the trigger config is incorrect.

Extract detailed YAML templates for each trigger type (GitLab, Artifact, etc.) into separate reference files, keeping only the most common template (e.g., GitHub webhook) inline in SKILL.md.

Remove the 'Examples' section — it merely restates trigger type mappings already obvious from the templates above it.

Dimension	Reasoning	Score
Conciseness	The skill is mostly efficient with good YAML templates, but includes some unnecessary sections like 'Examples' (which just restates what the triggers do) and 'Performance Notes' that are somewhat obvious. The troubleshooting section adds value but could be tighter.	2 / 3
Actionability	Provides fully formed, copy-paste-ready YAML templates for each trigger type, concrete MCP tool calls with parameters, specific event types, operator lists, and payload condition keys. Very executable guidance throughout.	3 / 3
Workflow Clarity	The 5-step instruction sequence is clear, and verification is mentioned (step 5: verify webhook registration). However, there's no explicit feedback loop for error recovery — if the trigger creation fails or webhook isn't registered, there's no validate-fix-retry cycle. The troubleshooting section partially compensates but isn't integrated into the workflow.	2 / 3
Progressive Disclosure	The content is well-organized with clear section headers, but it's a long monolithic file (~150+ lines of YAML templates) with no references to external files. The artifact source types, event types, and detailed templates for each provider could be split into separate reference files for better navigation.	2 / 3
	Total	9 / 12 Passed

Description

89%

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 with excellent trigger term coverage and a clear 'Use when' clause that makes it easy for Claude to select appropriately. The main weakness is that the 'what' portion could be more specific about the concrete actions performed (e.g., configuring webhook URLs, cron expressions, artifact conditions). Overall, it follows best practices and would perform well in a multi-skill selection scenario.

Suggestions

Expand the capability description to list more specific actions, e.g., 'configure webhook endpoints, define cron schedules, set artifact conditions' to improve specificity.

Dimension	Reasoning	Score
Specificity	The description names the domain (Harness Trigger YAML) and mentions two actions (generate YAML, create via MCP), but doesn't list specific concrete capabilities like configuring webhook endpoints, setting cron schedules, defining artifact conditions, etc.	2 / 3
Completeness	Clearly answers both 'what' (generate Harness Trigger YAML for automated pipeline execution and create via MCP) and 'when' (explicit 'Use when' clause with multiple trigger phrases and a conceptual trigger).	3 / 3
Trigger Term Quality	Excellent coverage of natural trigger terms: 'create trigger', 'webhook trigger', 'cron trigger', 'scheduled build', 'artifact trigger', and the conceptual phrase 'pipelines to run automatically' covers how users would naturally describe this need.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — the combination of 'Harness', 'Trigger YAML', 'MCP', and specific trigger types like 'webhook trigger', 'cron trigger', and 'artifact trigger' creates a clear niche that is unlikely to conflict with other skills.	3 / 3
	Total	11 / 12 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 — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: harness/harness-ai
Commit: fc23d5d

Reviewed: 17 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.