add-trigger

Create or update Sim webhook triggers with standardized registry wiring.

Updated Apr 16, 2026
One-click install
npx skills add https://github.com/tunacosgun/sim --skill add-trigger-tunacosgun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: add-trigger
Source: https://github.com/tunacosgun/sim/tree/main/.agents/skills/add-trigger
Command: npx skills add https://github.com/tunacosgun/sim --skill add-trigger-tunacosgun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Webhook management for Sim integrations is error-prone and time-consuming. This Skill automates creating and updating triggers using the generic trigger builder, aligning outputs, registration, and wiring to blocks.

Core Features & Use Cases

  • Scaffold and register triggers for new services using the standard builder
  • Generate or update provider handlers, outputs, and registry wiring
  • Integrate with apps/sim/triggers and block configuration to ensure consistent behavior

Quick Start

Provide the service name and let the builder scaffold and register the triggers.

Frequently Asked Questions about add-trigger

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

FAQPage Schema
How do I create webhook triggers for a Sim integration service?

To create Sim webhook triggers, you provide the service name to the builder, which scaffolds the trigger and registers it in the apps/sim/triggers directory. This ensures consistent outputs and provider handlers without manual configuration.

What is the best way to update webhook triggers without breaking block wiring?

Updating webhook triggers safely requires using the generic trigger builder to align provider handlers, outputs, and registry wiring. This standardized approach prevents block wiring mismatches and eliminates guessing payloads during integration updates.

How does the generic trigger builder standardize webhook integration?

The generic trigger builder standardizes webhook integration by automatically generating provider handlers, defining consistent outputs, and wiring the trigger registry. This removes error-prone manual configuration when adding webhook support to an integration.

Can I add webhook support to an existing integration without manual payload configuration?

Yes, you can add webhook support without manual payload configuration by applying the builder to the trigger registry. It generates standardized wiring and provider handlers across apps/sim/triggers, ensuring consistent behavior with no guessing of payloads.

Do I need to manually configure the trigger registry when scaffolding new services?

No, manual trigger registry configuration is unnecessary when scaffolding new services. The builder automates registration and block wiring, applying standardized outputs and provider handlers to ensure consistent webhook behavior across the integration.