create-trigger

Automates Harness trigger and MCP deployment for CI workflows.

80|16|Updated Mar 11, 2026
One-click install
npx skills add https://github.com/harness/harness-skills --skill create-trigger
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: create-trigger
Source: https://github.com/harness/harness-skills/tree/main/skills/create-trigger
Command: npx skills add https://github.com/harness/harness-skills --skill create-trigger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates Harness trigger configuration and MCP deployments to streamline CI workflow setup and reduce manual errors when wiring pipelines to events.

Core Features & Use Cases

  • Trigger YAML Generation: Generate Harness trigger YAML templates from user intent and target pipelines.
  • MCP Creation: Create triggers via MCP using the harness_create tool.
  • Webhook Registration Verification: Verify webhook registrations with Git providers to ensure triggers fire correctly.

Quick Start

Create a webhook trigger for a GitHub repository to run the ci_pipeline on PullRequest events.

Frequently Asked Questions about create-trigger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate Harness trigger creation for CI pipelines?

Automate Harness trigger creation by generating YAML templates and deploying them via MCP to wire pipelines to webhook, scheduled, and artifact events. This reduces manual configuration errors and streamlines CI workflow setup across projects.

How do I generate a webhook trigger YAML for a Harness pipeline?

Generate a webhook trigger YAML by defining your target pipeline and event intent, such as a GitHub PullRequest. The system creates a Harness trigger YAML template that you can apply to automate pipeline executions based on Git provider events.

Can I verify webhook registrations with Git providers when creating Harness triggers?

Yes, webhook registration verification with Git providers is supported to ensure triggers fire correctly. This validates that your Harness trigger configuration is properly wired to your repository events before pipeline execution relies on it.

Does MCP integration support creating scheduled and artifact triggers across projects?

Yes, MCP integration uses the harness_create tool to support scheduled, artifact, and webhook triggers across projects. This allows you to automate pipeline executions and respond to events using a streamlined deployment process.

What is the best way to configure Harness triggers without manual errors?

The best way to configure Harness triggers without manual errors is automating the setup through MCP creation and YAML template generation. This approach standardizes trigger configuration for webhook, scheduled, and artifact events across your CI workflows.

When should I not use automated YAML generation for Harness triggers?

Avoid automated YAML generation for Harness triggers when you require highly custom event payloads or conditional logic beyond standard webhook, scheduled, and artifact trigger configurations supported by the MCP integration.