Skills DirectorySkills Directory
SkillsLearnSecurityCategoriesDocsBlogPro
Sign InSubmit Skill
Skills Directory

Security-tested agent skills for Claude, coding agents, and AI workflows.

Directory

  • Browse Skills
  • All Skills A–Z
  • Claude Skills
  • Claude Code Skills
  • Agent Skills
  • Categories
  • Authors
  • Submit a Skill

Learn

  • Learn Hub
  • Install Claude Skills
  • Write SKILL.md
  • Skills vs MCP
  • Directories Compared

Security

  • Security
  • Methodology
  • Secure Claude Skills
  • Security Badges
  • Chrome Extension
  • Skill Manager

Company

  • About
  • Community
  • Blog
  • API Docs
  • Advertise

2026 Skills Directory. All rights reserved.

ProTermsPrivacyRefunds
Back to skills

Trigger Registry

ASecurity

Create, manage, and test reactive triggers (webhook & event-based). Triggers execute skills or routines in response to external events (GitHub push, Stripe payment, Linear issue, etc.). Use when user says 'create trigger', 'list triggers', 'novo trigger', 'webhook para', 'quando acontecer', 'trigger list', 'test trigger', or any reference to reactive event triggers.

529 stars
0 votes
0 copies
0 views
Added 5/29/2026
ai-agentspythonreacttestinggitapibackend

Works with

cliapi

Security Analysis

A100/100

Scanned 5/29/2026

$npx -y skills add evolution-foundation/evo-nexus --skill trigger-registry --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Trigger Registry?

Add the live security badge to your README — it updates automatically with every re-scan.

Security grade badge for Trigger Registry
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/evolution-foundation-trigger-registry/badge)](https://www.skillsdirectory.com/skills/evolution-foundation-trigger-registry)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
Files
SKILL.md
---
name: trigger-registry
description: "Create, manage, and test reactive triggers (webhook & event-based). Triggers execute skills or routines in response to external events (GitHub push, Stripe payment, Linear issue, etc.). Use when user says 'create trigger', 'list triggers', 'novo trigger', 'webhook para', 'quando acontecer', 'trigger list', 'test trigger', or any reference to reactive event triggers."
metadata:
  author: evonexus
  version: "1.0"
---

# Trigger Registry — Reactive Event Triggers

Create and manage triggers that execute skills or routines in response to external events (webhooks, integrations).

## When to Use

- User wants to create a webhook endpoint: "cria um webhook para quando tiver push no GitHub"
- User wants to react to events: "quando alguem abrir issue no Linear, notifica no Discord"
- User wants to list/manage triggers: "lista os triggers", "desativa o trigger de deploy"
- User wants to test a trigger: "testa o trigger #3"

## API Reference

The dashboard backend exposes these endpoints:

| Method | Endpoint | Action |
|--------|----------|--------|
| GET | `/api/triggers` | List triggers (query: `?type=webhook\|event&source=github\|stripe\|...&enabled=true\|false`) |
| POST | `/api/triggers` | Create a new trigger |
| GET | `/api/triggers/<id>` | Get trigger details + last 20 executions |
| PUT | `/api/triggers/<id>` | Update trigger |
| DELETE | `/api/triggers/<id>` | Delete trigger + executions |
| POST | `/api/triggers/<id>/test` | Test trigger (simulate execution) |
| POST | `/api/triggers/<id>/regenerate-secret` | Regenerate webhook secret |
| GET | `/api/triggers/<id>/executions` | List executions with pagination |
| POST | `/api/triggers/webhook/<id>` | **Webhook receiver** (public, HMAC-validated) |

## Trigger Types

| Type | Description |
|------|-------------|
| `webhook` | Receives HTTP POST from external services (GitHub, Stripe, etc.) |
| `event` | Reacts to integration events (configured in YAML or UI) |

## Sources & Event Examples

| Source | Signature Header | Example Events |
|--------|-----------------|----------------|
| `github` | `X-Hub-Signature-256` | push, pull_request, issues, release |
| `stripe` | `Stripe-Signature` | charge.succeeded, customer.subscription.created, invoice.paid |
| `linear` | `X-Linear-Signature` | Issue (create/update), Comment |
| `telegram` | Token-based | message, callback_query |
| `discord` | Ed25519 | message_create |
| `custom` | `X-Webhook-Signature` | Any — user-defined |

## Action Types

| Type | Payload | When to Use |
|------|---------|-------------|
| `skill` | Skill name (e.g. `discord-send-message Deploy detectado`) | Running a Claude skill |
| `prompt` | Free-form prompt text | Running a raw Claude prompt |
| `script` | Script path relative to `ADWs/routines/` | Running an existing routine script |

## Agents

| Agent ID | Short Name |
|----------|------------|
| `clawdia-assistant` | @clawdia |
| `flux-financeiro` | @flux |
| `atlas-project` | @atlas |
| `kai-personal-assistant` | @kai |
| `pulse-community` | @pulse |
| `sage-strategy` | @sage |
| `pixel-social-media` | @pixel |
| `nex-comercial` | @nex |
| `mentor-courses` | @mentor |

## Workflow

### Creating a Trigger

1. **Understand the request** — extract what event, what action, which agent:
   - **Event source:** GitHub, Stripe, Linear, Telegram, Discord, custom
   - **Event filter:** which specific events to match (e.g., push to main, charge.succeeded)
   - **Action:** what to do when triggered (skill, prompt, or script)
   - **Agent:** which agent should handle the action

2. **Confirm with user** — show summary:
   ```
   Criar trigger:
   - Nome: Deploy Notification
   - Tipo: webhook
   - Source: github
   - Filtro: event=push, branch=main, repo=EvolutionAPI/evolution-api
   - Action: skill discord-send-message Deploy detectado na main
   - Agent: @pulse
   - Enabled: true

   Confirma?
   ```

3. **Create via API:**

   Use `from dashboard.backend.sdk_client import evo` — auto-handles URL + auth.

   ```python
   from dashboard.backend.sdk_client import evo
   trigger = evo.post("/api/triggers", {
       "name": "Deploy Notification",
       "type": "webhook",
       "source": "github",
       "event_filter": {"event": "push", "branch": "main", "repo": "EvolutionAPI/evolution-api"},
       "action_type": "skill",
       "action_payload": "discord-send-message Deploy detectado na main",
       "agent": "pulse-community",
       "enabled": True,
   })
   ```

4. **Show result** — display webhook URL and secret for configuration:
   ```
   Trigger criado!
   - ID: 1
   - Webhook URL: http://localhost:8080/api/triggers/webhook/1
   - Secret: abc123... (configure no GitHub webhook settings)
   ```

### Listing Triggers

```python
from dashboard.backend.sdk_client import evo
triggers = evo.get("/api/triggers")
```

Format as table: ID | Name | Type | Source | Status | Runs

### Testing a Trigger

```python
from dashboard.backend.sdk_client import evo
evo.post("/api/triggers/1/test")
```

### Common Templates

When user selects a source, suggest pre-built event filters:

**GitHub:**
- Push to main: `{"event": "push", "branch": "main"}`
- New PR: `{"event": "pull_request", "action": "opened"}`
- Issue opened: `{"event": "issues", "action": "opened"}`
- Release published: `{"event": "release", "action": "published"}`

**Stripe:**
- Payment succeeded: `{"event_type": "charge.succeeded"}`
- New subscription: `{"event_type": "customer.subscription.created"}`
- Invoice paid: `{"event_type": "invoice.paid"}`

**Linear:**
- Issue created: `{"event_type": "Issue", "action": "create"}`
- Issue updated: `{"event_type": "Issue", "action": "update"}`

Attribution

evolution-foundationevolution-foundation
View sourceSee grades on GitHubMore from evolution-foundation →
SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments (0)

No comments yet. Be the first to comment!

SSkills DirectorySkills Directory

Ship a skill? Prove it's safe.

Free 120-pattern security scan, letter grade, and an embeddable README badge.

Submit a skill

Related Skills

Caveman

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

1100021 votes

Hyperplan

Adversarial multi-agent planning skill. Self-orchestrates 5 hostile category members (unspecified-low, unspecified-high, deep, ultrabrain, artistry) via team-mode for ruthless cross-critique debate, distills only the defensible insights, then MANDATORILY hands the distilled insight bundle to the `plan` agent for executable plan formalization. Use when planning needs maximum rigor and surfacing of weak assumptions, blind spots, and over-engineering. Triggers: 'hyperplan', 'hpp', '/hyperplan', ...

698461 votes

Writing Skills

Create and manage Claude Code skills in HASH repository following Anthropic best practices. Use when creating new skills, modifying skill-rules.json, understanding trigger patterns, working with hooks, debugging skill activation, or implementing progressive disclosure. Covers skill structure, YAML frontmatter, trigger types (keywords, intent patterns), UserPromptSubmit hook, and the 500-line rule. Includes validation and debugging with SKILL_DEBUG. Examples include rust-error-stack, cargo-dep...

3931 votes

Mcp Code Execution

Routes multi-tool workflows through MCP servers for large datasets and pipelines. Use when Bash tool overhead is limiting throughput on data-heavy tasks.

3421 votes

catchup

Recovers the conversation and failed tool calls of a previous Codex, Amp, Claude Code, Antigravity, Cline, Copilot CLI, Cursor, DeepSeek Harness, Grok Build, Kimi, OpenCode, Pi Agent, or ZCode session. Use when the user says "catch up", "what did the last session do", "get me up to speed", "I switched agents", asks to recover/summarize a previous session before continuing, or asks to diagnose or report a catchup failure. Do NOT use for the current conversation, git history, or any non-agent log.

741 votes
View all in ai-agents →