Agent skill

Add Trigger

by simstudioai in simstudioai/sim

Create webhook or polling triggers for a Sim integration. An agent skill from simstudioai/sim.

Apache-2.0Auto-check passedBackend & APIs

Install Add Trigger

skills CLI
$ npx skills add simstudioai/sim --skill add-trigger -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install simstudioai/sim add-trigger --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/simstudioai/sim.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/add-trigger .claude/skills/add-trigger && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
add-trigger
GitHub stars
30k
Token cost
~5.6k tokens
SKILL.md length
1,285 words
Files
2
Skills in repo
40
Repo updated
First seen
Licence
Apache-2.0

At a glance

Create webhook or polling triggers for a Sim integration. An agent skill from simstudioai/sim.

  • Works in 3 steps: Create utils.ts → Create Trigger Files → Register and Wire
  • A Sim integration
  • SKILL.md covers Your Task, Hard Rule: No Guessed Webhook…, Directory Structure and Step 1: Create utils.ts, plus 9 more sections
  • Calls bun

What it does

Add Trigger is an agent skill from simstudioai/sim. Create webhook or polling triggers for a Sim integration

Its SKILL.md is about 5.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).

It sits in Backend & APIs, covering Webhooks. The repository describes itself as: Sim is the collaborative workspace to build, deploy, and monitor AI agents and workflows. Used by 100,000+ builders. The licence is Apache-2.0.

When your agent uses it

  • A Sim integration
  • Tasks that involve Webhooks

Example prompts

  • “/add-trigger”

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Create utils.ts
  2. Create Trigger Files
  3. Register and Wire

What it can do on your machine

Read from SKILL.md and the folder at commit 546d4e7. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • bun

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Add Trigger loads about 5.6k tokens when it runs. Until then it costs about 17 tokens; SKILL.md has 1,285 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~17
When it runs · the whole SKILL.md, loaded when a task matches
~5.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from simstudioai/sim at commit 546d4e7, republished under its Apache-2.0 licence (© simstudioai). 1,285 words, ~5,553 tokens.

Download SKILL.mdSave it as .claude/skills/add-trigger/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
add-trigger
description
Create webhook or polling triggers for a Sim integration
argument-hint
<service-name>

Add Trigger

You are an expert at creating webhook and polling triggers for Sim. You understand the trigger system, the generic buildTriggerSubBlocks helper, polling infrastructure, and how triggers connect to blocks.

Your Task

  1. Research what webhook events the service supports — if the service lacks reliable webhooks, use polling
  2. Create the trigger files using the generic builder (webhook) or manual config (polling)
  3. Create a provider handler (webhook) or polling handler (polling)
  4. Register triggers and connect them to the block

Hard Rule: No Guessed Webhook Payload Schemas

If the service docs do not clearly show the webhook payload JSON for an event, you MUST tell the user instead of guessing trigger outputs or formatInput mappings.

  • Do NOT invent payload field names
  • Do NOT guess nested event object paths
  • Do NOT infer output fields from the UI or marketing docs
  • Do NOT write formatInput against unverified webhook bodies

If the payload shape is unknown, do one of these instead:

  1. Ask the user for sample webhook payloads
  2. Ask the user for a test webhook source so you can inspect a real event
  3. Implement only the event registration/setup portions whose payloads are documented
  4. Leave the trigger unimplemented and explicitly say which payload fields are unknown

Directory Structure

apps/sim/triggers/{service}/
├── index.ts              # Barrel exports
├── utils.ts              # Service-specific helpers (options, instructions, extra fields, outputs)
├── {event_a}.ts          # Primary trigger (includes dropdown)
├── {event_b}.ts          # Secondary trigger (no dropdown)
└── webhook.ts            # Generic webhook trigger (optional, for "all events")

apps/sim/lib/webhooks/
├── provider-subscription-utils.ts  # Shared subscription helpers (getProviderConfig, getNotificationUrl)
├── providers/
│   ├── {service}.ts       # Provider handler (auth, formatInput, matchEvent, subscriptions)
│   ├── types.ts           # WebhookProviderHandler interface
│   ├── utils.ts           # Shared helpers (createHmacVerifier, verifyTokenAuth, skipByEventTypes)
│   └── registry.ts        # Handler map + default handler

Step 1: Create utils.ts

This file contains all service-specific helpers used by triggers.

typescript
import type { SubBlockConfig } from '@/blocks/types'
import type { TriggerOutput } from '@/triggers/types'

export const {service}TriggerOptions = [
  { label: 'Event A', id: '{service}_event_a' },
  { label: 'Event B', id: '{service}_event_b' },
]

export function {service}SetupInstructions(eventType: string): string {
  const instructions = [
    'Copy the <strong>Webhook URL</strong> above',
    'Go to <strong>{Service} Settings > Webhooks</strong>',
    `Select the <strong>${eventType}</strong> event type`,
    'Paste the webhook URL and save',
    'Click "Save" above to activate your trigger',
  ]
  return instructions
    .map((instruction, index) =>
      `<div class="mb-3"><strong>${index + 1}.</strong> ${instruction}</div>`
    )
    .join('')
}

export function build{Service}ExtraFields(triggerId: string): SubBlockConfig[] {
  return [
    {
      id: 'projectId',
      title: 'Project ID (Optional)',
      type: 'short-input',
      placeholder: 'Leave empty for all projects',
      mode: 'trigger',
      condition: { field: 'selectedTriggerId', value: triggerId },
    },
  ]
}

export function build{Service}Outputs(): Record<string, TriggerOutput> {
  return {
    eventType: { type: 'string', description: 'The type of event' },
    resourceId: { type: 'string', description: 'ID of the affected resource' },
    resource: {
      id: { type: 'string', description: 'Resource ID' },
      name: { type: 'string', description: 'Resource name' },
    },
  }
}

Step 2: Create Trigger Files

Primary trigger — MUST include includeDropdown: true:

typescript
import { {Service}Icon } from '@/components/icons'
import { buildTriggerSubBlocks } from '@/triggers'
import { build{Service}ExtraFields, build{Service}Outputs, {service}SetupInstructions, {service}TriggerOptions } from '@/triggers/{service}/utils'
import type { TriggerConfig } from '@/triggers/types'

export const {service}EventATrigger: TriggerConfig = {
  id: '{service}_event_a',
  name: '{Service} Event A',
  provider: '{service}',
  description: 'Trigger workflow when Event A occurs',
  version: '1.0.0',
  icon: {Service}Icon,
  subBlocks: buildTriggerSubBlocks({
    triggerId: '{service}_event_a',
    triggerOptions: {service}TriggerOptions,
    includeDropdown: true,
    setupInstructions: {service}SetupInstructions('Event A'),
    extraFields: build{Service}ExtraFields('{service}_event_a'),
  }),
  outputs: build{Service}Outputs(),
  webhook: { method: 'POST', headers: { 'Content-Type': 'application/json' } },
}

Secondary triggers — NO includeDropdown (it's already in the primary):

typescript
export const {service}EventBTrigger: TriggerConfig = {
  // Same as above but: id: '{service}_event_b', no includeDropdown
}

Step 3: Register and Wire

apps/sim/triggers/{service}/index.ts
typescript
export { {service}EventATrigger } from './event_a'
export { {service}EventBTrigger } from './event_b'
apps/sim/triggers/registry.ts
typescript
import { {service}EventATrigger, {service}EventBTrigger } from '@/triggers/{service}'

export const TRIGGER_REGISTRY: TriggerRegistry = {
  // ... existing ...
  {service}_event_a: {service}EventATrigger,
  {service}_event_b: {service}EventBTrigger,
}
Block file (apps/sim/blocks/blocks/{service}.ts)

Wire triggers into the block so the trigger UI appears and generate-docs.ts discovers them. Two changes are needed:

  1. Spread trigger subBlocks at the end of the block's subBlocks array
  2. Add triggers property after outputs with enabled: true and available: [...]
typescript
import { getTrigger } from '@/triggers'

export const {Service}Block: BlockConfig = {
  // ...
  subBlocks: [
    // Regular tool subBlocks first...
    ...getTrigger('{service}_event_a').subBlocks,
    ...getTrigger('{service}_event_b').subBlocks,
  ],
  // ... tools, inputs, outputs ...
  triggers: {
    enabled: true,
    available: ['{service}_event_a', '{service}_event_b'],
  },
}

Versioned blocks (V1 + V2): Many integrations have a hidden V1 block and a visible V2 block. Where you add the trigger wiring depends on how V2 inherits from V1:

  • V2 uses ...V1Block spread (e.g., Google Calendar): Add trigger to V1 — V2 inherits both subBlocks and triggers automatically.
  • V2 defines its own subBlocks (e.g., Google Sheets): Add trigger to V2 (the visible block). V1 is hidden and doesn't need it.
  • Single block, no V2 (e.g., Google Drive): Add trigger directly.

generate-docs.ts documents only visible blocks (category: 'tools', not hideFromToolbar, not preview), one per base type. A trigger appears only if that visible block lists it in triggers.available. Always verify by checking the output after running the script.

Provider Handler

All provider-specific webhook logic lives in a single handler file: apps/sim/lib/webhooks/providers/{service}.ts.

When to Create a Handler
BehaviorMethodExamples
HMAC signature authverifyAuth via createHmacVerifierAshby, Jira, Linear, Typeform
Custom token authverifyAuth via verifyTokenAuthGeneric, Google Forms
Event filteringmatchEventGitHub, Jira, Attio, HubSpot
Idempotency dedupextractIdempotencyIdSlack, Stripe, Linear, Jira
Custom input formattingformatInputSlack, Teams, Attio, Ashby
Auto webhook creationcreateSubscriptionAshby, Grain, Calendly, Airtable
Auto webhook deletiondeleteSubscriptionAshby, Grain, Calendly, Airtable
Challenge/verificationhandleChallengeSlack, WhatsApp, Teams
Custom success responseformatSuccessResponseSlack, Twilio Voice, Teams

If none apply, you don't need a handler. The default handler provides bearer token auth.

Example Handler
typescript
import crypto from 'crypto'
import { createLogger } from '@sim/logger'
import { safeCompare } from '@sim/security/compare'
import type { EventMatchContext, FormatInputContext, FormatInputResult, WebhookProviderHandler } from '@/lib/webhooks/providers/types'
import { createHmacVerifier } from '@/lib/webhooks/providers/utils'

const logger = createLogger('WebhookProvider:{Service}')

function validate{Service}Signature(secret: string, signature: string, body: string): boolean {
  if (!secret || !signature || !body) return false
  const computed = crypto.createHmac('sha256', secret).update(body, 'utf8').digest('hex')
  return safeCompare(computed, signature)
}

export const {service}Handler: WebhookProviderHandler = {
  verifyAuth: createHmacVerifier({
    configKey: 'webhookSecret',
    headerName: 'X-{Service}-Signature',
    validateFn: validate{Service}Signature,
    providerLabel: '{Service}',
    requireSecret: true,
  }),

  async matchEvent({ body, requestId, providerConfig }: EventMatchContext) {
    const triggerId = providerConfig.triggerId as string | undefined
    if (triggerId && triggerId !== '{service}_webhook') {
      const { is{Service}EventMatch } = await import('@/triggers/{service}/utils')
      if (!is{Service}EventMatch(triggerId, body as Record<string, unknown>)) return false
    }
    return true
  },

  async formatInput({ body }: FormatInputContext): Promise<FormatInputResult> {
    const b = body as Record<string, unknown>
    return {
      input: {
        eventType: b.type,
        resourceId: (b.data as Record<string, unknown>)?.id ?? null,
        resource: b.data,
      },
    }
  },

  extractIdempotencyId(body: unknown) {
    const obj = body as Record<string, unknown>
    return obj.id && obj.type ? `${obj.type}:${obj.id}` : null
  },
}
Register the Handler

In apps/sim/lib/webhooks/providers/registry.ts:

typescript
import { {service}Handler } from '@/lib/webhooks/providers/{service}'

const PROVIDER_HANDLERS: Record<string, WebhookProviderHandler> = {
  // ... existing (alphabetical) ...
  {service}: {service}Handler,
}

Output Alignment (Critical)

There are two sources of truth that MUST be aligned:

  1. Trigger outputs — schema defining what fields SHOULD be available (UI tag dropdown)
  2. formatInput on the handler — implementation that transforms raw payload into actual data

If they differ: the tag dropdown shows fields that don't exist, or actual data has fields users can't discover.

Rules for formatInput:

  • Return { input: { ... } } where inner keys match trigger outputs exactly
  • Return { input: ..., skip: { message: '...' } } to skip execution
  • No wrapper objects or duplication
  • Use null for missing optional data

Automatic Webhook Registration

If the service API supports programmatic webhook creation, implement createSubscription and deleteSubscription on the handler. The orchestration layer calls these automatically — no code touches route.ts, provider-subscriptions.ts, or deploy.ts.

typescript
import { getNotificationUrl, getProviderConfig } from '@/lib/webhooks/provider-subscription-utils'
import type { DeleteSubscriptionContext, SubscriptionContext, SubscriptionResult } from '@/lib/webhooks/providers/types'

export const {service}Handler: WebhookProviderHandler = {
  async createSubscription(ctx: SubscriptionContext): Promise<SubscriptionResult | undefined> {
    const config = getProviderConfig(ctx.webhook)
    const apiKey = config.apiKey as string
    if (!apiKey) throw new Error('{Service} API Key is required.')

    const res = await fetch('https://api.{service}.com/webhooks', {
      method: 'POST',
      headers: { Authorization: `Bearer ${apiKey}`, 'Content-Type': 'application/json' },
      body: JSON.stringify({ url: getNotificationUrl(ctx.webhook) }),
    })

    if (!res.ok) throw new Error(`{Service} error: ${res.status}`)
    const { id } = (await res.json()) as { id: string }
    return { providerConfigUpdates: { externalId: id } }
  },

  async deleteSubscription(ctx: DeleteSubscriptionContext): Promise<void> {
    const config = getProviderConfig(ctx.webhook)
    const { apiKey, externalId } = config as { apiKey?: string; externalId?: string }
    if (!apiKey || !externalId) return
    await fetch(`https://api.{service}.com/webhooks/${externalId}`, {
      method: 'DELETE',
      headers: { Authorization: `Bearer ${apiKey}` },
    }).catch(() => {})
  },
}

Key points:

  • Throw from createSubscription — orchestration rolls back the DB webhook
  • Never throw from deleteSubscription — log non-fatally
  • Return { providerConfigUpdates: { externalId } } — orchestration merges into providerConfig
  • Add apiKey field to build{Service}ExtraFields with password: true

Trigger Outputs Schema

Trigger outputs use the same schema as block outputs (NOT tool outputs).

Supported: type + description for leaf fields, nested objects for complex data. NOT supported: optional: true, items (those are tool-output-only features).

typescript
export function buildOutputs(): Record<string, TriggerOutput> {
  return {
    eventType: { type: 'string', description: 'Event type' },
    timestamp: { type: 'string', description: 'When it occurred' },
    payload: { type: 'json', description: 'Full event payload' },
    resource: {
      id: { type: 'string', description: 'Resource ID' },
      name: { type: 'string', description: 'Resource name' },
    },
  }
}

Polling Triggers

Use polling when the service lacks reliable webhooks (e.g., Google Sheets, Google Drive, Google Calendar, Gmail, RSS, IMAP). Polling triggers do NOT use buildTriggerSubBlocks — they define subBlocks manually.

Directory Structure
apps/sim/triggers/{service}/
├── index.ts              # Barrel export
└── poller.ts             # TriggerConfig with polling: true

apps/sim/lib/webhooks/polling/
└── {service}.ts           # PollingProviderHandler implementation
Polling Handler (apps/sim/lib/webhooks/polling/{service}.ts)
typescript
import { pollingIdempotency } from '@/lib/core/idempotency/service'
import type { PollingProviderHandler, PollWebhookContext } from '@/lib/webhooks/polling/types'
import { markWebhookFailed, markWebhookSuccess, resolveOAuthCredential, updateWebhookProviderConfig } from '@/lib/webhooks/polling/utils'
import { processPolledWebhookEvent } from '@/lib/webhooks/processor'

export const {service}PollingHandler: PollingProviderHandler = {
  provider: '{service}',
  label: '{Service}',

  async pollWebhook(ctx: PollWebhookContext): Promise<'success' | 'failure'> {
    const { webhookData, workflowData, requestId, logger } = ctx
    const webhookId = webhookData.id

    try {
      // For OAuth services:
      const accessToken = await resolveOAuthCredential(webhookData, '{service}', requestId)
      const config = webhookData.providerConfig as unknown as {Service}WebhookConfig

      // First poll: seed state, emit nothing
      if (!config.lastCheckedTimestamp) {
        await updateWebhookProviderConfig(webhookId, { lastCheckedTimestamp: new Date().toISOString() }, logger)
        await markWebhookSuccess(webhookId, logger)
        return 'success'
      }

      // Fetch changes since last poll, process with idempotency
      // ...

      await markWebhookSuccess(webhookId, logger)
      return 'success'
    } catch (error) {
      logger.error(`[${requestId}] Error processing {service} webhook ${webhookId}:`, error)
      await markWebhookFailed(webhookId, logger)
      return 'failure'
    }
  },
}

Key patterns:

  • First poll seeds state and emits nothing (avoids flooding with existing data)
  • Use pollingIdempotency.executeWithIdempotency(provider, key, callback) for dedup
  • Use processPolledWebhookEvent(webhookData, workflowData, payload, requestId) to fire the workflow
  • Use updateWebhookProviderConfig(webhookId, partialConfig, logger) for read-merge-write on state
  • Use the latest server-side timestamp from API responses (not wall clock) to avoid clock skew
Show full SKILL.md (489 more words)Show less
Trigger Config (apps/sim/triggers/{service}/poller.ts)
typescript
import { {Service}Icon } from '@/components/icons'
import type { TriggerConfig } from '@/triggers/types'

export const {service}PollingTrigger: TriggerConfig = {
  id: '{service}_poller',
  name: '{Service} Trigger',
  provider: '{service}',
  description: 'Triggers when ...',
  version: '1.0.0',
  icon: {Service}Icon,
  polling: true,               // REQUIRED — routes to polling infrastructure

  subBlocks: [
    { id: 'triggerCredentials', type: 'oauth-input', title: 'Credentials', serviceId: '{service}', canonicalParamId: 'oauthCredential', requiredScopes: [], required: true, mode: 'trigger' },
    // ... service-specific config fields (dropdowns, inputs, switches) ...
    { id: 'triggerInstructions', type: 'text', title: 'Setup Instructions', hideFromPreview: true, mode: 'trigger', defaultValue: '...' },
  ],

  outputs: {
    // Must match the payload shape from processPolledWebhookEvent
  },
}
Registration (3 places)
  1. apps/sim/triggers/constants.ts — add provider to POLLING_PROVIDERS Set
  2. apps/sim/lib/webhooks/polling/registry.ts — import handler, add to POLLING_HANDLERS
  3. apps/sim/triggers/registry.ts — import trigger config, add to TRIGGER_REGISTRY
Helm Cron Job

Add to helm/sim/values.yaml under the existing polling cron jobs:

yaml
{service}WebhookPoll:
  enabled: true
  name: {service}-webhook-poll
  schedule: "*/1 * * * *"
  path: "/api/webhooks/poll/{service}"
  concurrencyPolicy: Forbid
  successfulJobsHistoryLimit: 3
  failedJobsHistoryLimit: 1

Mirror the existing rssWebhookPoll entry, and add the matching line to docker/crontab under # Polling triggers (copy the existing rss line's format). bun run check:cron-parity fails when the two disagree.

Reference Implementations
  • Simple: apps/sim/lib/webhooks/polling/rss.ts + apps/sim/triggers/rss/poller.ts
  • Complex (OAuth, attachments): apps/sim/lib/webhooks/polling/gmail.ts + apps/sim/triggers/gmail/poller.ts
  • Cursor-based (changes API): apps/sim/lib/webhooks/polling/google-drive.ts
  • Timestamp-based: apps/sim/lib/webhooks/polling/google-calendar.ts

Option Lists: selectorKey or options, never a per-block fetcher

Trigger sub-blocks follow the same rules as block sub-blocks: see the add-block skill → Option Lists, .claude/rules/sim-integrations.md, and the add-selector skill. Trigger-specific: the shared context builder runs in trigger mode, and it aliases only the legacy credential ids credential / botCredential / customBotCredential / manualBotCredential. Any other trigger credential sub-block (such as triggerCredentials) needs canonicalParamId: 'oauthCredential', or a manifest sourceFields alias when a legacy source id must be retained.

Checklist

Webhook and polling routes are legitimate external ingress boundaries. They must not call this Sim app's own API routes to reuse provider or business logic. Extract the shared provider operation or authorized application use case and call it directly from the trigger handler and any other server adapter. HTTP is reserved for an actual cross-process/capability boundary. Tool work uses a registered InternalToolConfig.operation; a directExecution property fails bun run check:tool-request-boundary.

Trigger Definition
  • Created utils.ts with options, instructions, extra fields, and output builders
  • Primary trigger has includeDropdown: true; secondary triggers do NOT
  • All triggers use buildTriggerSubBlocks helper
  • Created index.ts barrel export
  • Trigger files never statically value-import @/blocks, directly or transitively (import type and dynamic import() are fine); bun run check:trigger-block-cycle enforces this
Registration
  • All triggers in triggers/registry.ts → TRIGGER_REGISTRY
  • Block has triggers.enabled: true and lists all trigger IDs in triggers.available
  • Block spreads all trigger subBlocks: ...getTrigger('id').subBlocks
Provider Handler (if needed)
  • Handler file at apps/sim/lib/webhooks/providers/{service}.ts
  • Registered in providers/registry.ts (alphabetical)
  • Signature validator is a private function inside the handler file
  • createHmacVerifier passes requireSecret: true when the provider always signs
  • formatInput output keys match trigger outputs exactly
  • Event matching uses dynamic await import() for trigger utils
Auto Registration (if supported)
  • createSubscription and deleteSubscription on the handler
  • NO changes to route.ts, provider-subscriptions.ts, or deploy.ts
  • API key field uses password: true
Polling Trigger (if applicable)
  • Handler implements PollingProviderHandler at lib/webhooks/polling/{service}.ts
  • Trigger config has polling: true and defines subBlocks manually (no buildTriggerSubBlocks)
  • Provider string matches across: trigger config, handler, POLLING_PROVIDERS, polling registry
  • First poll seeds state and emits nothing
  • Added provider to POLLING_PROVIDERS in triggers/constants.ts
  • Added handler to POLLING_HANDLERS in lib/webhooks/polling/registry.ts
  • Added cron job to helm/sim/values.yaml and the matching docker/crontab line; bun run check:cron-parity passes
  • Payload shape matches trigger outputs schema
Testing
  • bun run type-check passes
  • Manually verify output keys match trigger outputs keys
  • Trigger UI shows correctly in the block
  • Ran bun run scripts/generate-docs.ts and committed the refreshed pages — trigger sections render into the owning integration's docs page, and CI's bun run docs:check fails on stale pages

© simstudioai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/add-trigger of simstudioai/sim.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit 546d4e7

Compare with similar skills

Add Trigger next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Add Trigger compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Add Trigger this skillsimstudioai/sim30k—~5.6kAutomated safety check: PassApache-2.0
Novu Design Workflownovuhq/novu40k—~2.6kAutomated safety check: PassCustom licence
Golivemikehasa/golive-skill1.2k—~13kAutomated safety check: NotesMIT
Stripe Appsfossasia/eventyay1.7k1 repos~3.6kAutomated safety check: PassApache-2.0
Dingtalk Messageagentscope-ai/ReMe3.6k—~1.6kAutomated safety check: PassApache-2.0
PR Review Provideryansongda/pay5.4k—~2.4kAutomated safety check: PassMIT

Similar skills

  • Design notification workflows the Novu way — choose channels, set severity, decide when a workflow is critical, configure digests, and route based on subscriber state.

    40k GitHub stars~2.6k tokensUpdated today
    Backend & APIsAuto-check passed
  • Golive

    mikehasa/golive-skill

    Take an agent-written app from repo to live production on the user's OWN accounts, with providers they choose (hosting, database, auth, payments, email, domain/DNS).

    1.2k GitHub stars~13k tokensUpdated 3 days ago
    Backend & APIsAuto-check: notes
  • Stripe Apps

    fossasia/eventyay

    A skill your agent uses when building, modifying, or reviewing a Stripe App — or when the user describes something that implies one (e.g.

    1.7k GitHub starsUsed in 1 repo~3.6k tokens
    Backend & APIsAuto-check passed
  • Dingtalk Message

    agentscope-ai/ReMe

    钉钉消息发送技能。支持企业内部机器人(批量单聊/群聊)和 Webhook 自定义机器人两种接入方式,支持多机器人管理,支持文本、Markdown、链接、ActionCard、FeedCard等多种消息类型。

    3.6k GitHub stars~1.6k tokensUpdated yesterday
    Backend & APIsAuto-check passed
  • PR Review Provider

    yansongda/pay

    A skill your agent uses when reviewing PRs that add or modify a payment Provider in yansongda/pay - covers plugin pipeline, multi-tenant safety, signature verification, docs, and naming conventions.

    5.4k GitHub stars~2.4k tokensUpdated 9 days ago
    Backend & APIsAuto-check passed
  • Stripe Best Practices

    kanchengw/cnllm

    Guides Stripe integration decisions — API selection (Checkout Sessions vs PaymentIntents), Connect platform setup (Accounts v2, controller properties), billing/subscriptions, Treasury financial…

    175 GitHub starsUsed in 3 repos~925 tokens
    Backend & APIsAuto-check passed

More from simstudioai/sim

All 40 skills in this repo
  • Sim Helm

    simstudioai/sim

    Install, upgrade, and operate the Sim Helm chart on Kubernetes.

    30k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Add Column Type

    simstudioai/sim

    Add a new table column type to Sim — registry entry, icon, storage shape, coercion, and the behavioral hooks the grid and API read.

    30k GitHub stars~2.9k tokensUpdated today
    Auto-check passed
  • Add Enrichment

    simstudioai/sim

    Add a code-defined table enrichment (registry entry) under apps/sim/enrichments/ backed by an ordered provider cascade, ensuring every provider tool it calls has hosted-key support.

    30k GitHub stars~2.2k tokensUpdated today
    Auto-check passed
  • Add Hosted Key

    simstudioai/sim

    Add hosted API key support to a tool so Sim provides the key (metered and billed to the workspace) when a user has not brought their own.

    30k GitHub stars~3.4k tokensUpdated today
    Auto-check passed
  • Add Managed CLI

    simstudioai/sim

    Add or upgrade a curated, immutable managed CLI for Sim Function sandboxes, including client-safe catalog metadata, a pinned server-only installation recipe, checksum and executable verification…

    30k GitHub stars~2.4k tokensUpdated today
    Auto-check passed
  • Add Selector

    simstudioai/sim

    Add or update a Sim dynamic selector using the shared manifest, server attachment, and selectors.execute path.

    30k GitHub stars~1.7k tokensUpdated today
    Auto-check passed

Categories

Questions about Add Trigger

What does Add Trigger do?

Create webhook or polling triggers for a Sim integration. An agent skill from simstudioai/sim. Add Trigger is an agent skill from simstudioai/sim.

When should I use Add Trigger?

Add Trigger fits situations like: A Sim integration; tasks that involve Webhooks.

How do I install Add Trigger in Claude Code?

Run `npx skills add simstudioai/sim --skill add-trigger -a claude-code`. Or copy the skill folder (.agents/skills/add-trigger in simstudioai/sim) into .claude/skills/add-trigger in your project. Claude Code loads it when a task matches its description.

How do I install Add Trigger in Codex?

Run `npx skills add simstudioai/sim --skill add-trigger -a codex`. Or copy the skill folder (.agents/skills/add-trigger in simstudioai/sim) into .agents/skills/add-trigger in your project. Codex loads it when a task matches its description.

Can I use Add Trigger in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add simstudioai/sim --skill add-trigger -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/add-trigger, .gemini/skills/add-trigger, .github/skills/add-trigger and .opencode/skills/add-trigger in your project.

What does Add Trigger need to run?

Going by SKILL.md and its folder, Add Trigger needs the command-line tools its instructions call (bun).

Does Add Trigger access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Add Trigger safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Add Trigger use?

Add Trigger is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Add Trigger use?

About 5.6k tokens (SKILL.md is roughly 22k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Add Trigger?

Skills that share tags, products or a category with Add Trigger: Novu Design Workflow (novuhq/novu, 40k stars), Golive (mikehasa/golive-skill, 1.2k stars), Stripe Apps (fossasia/eventyay, 1.7k stars) and Dingtalk Message (agentscope-ai/ReMe, 3.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Add Trigger?

simstudioai (a GitHub organization) maintains it in simstudioai/sim, which has 29,785 GitHub stars. The repository holds 40 skills in this directory. The repository was last updated on October 7, 2026.

Source: simstudioai/sim on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.