Ade Webhooks
arul28/ADE
A skill your agent uses when someone wants an agent to run whenever something happens in another service — a GitHub issue or PR, a Stripe payment, a Linear issue, a Sentry error, a failed deploy…
Create, manage, and test reactive triggers (webhook & event-based).
Install Trigger Registry
$ npx skills add evolution-foundation/evo-nexus --skill trigger-registry -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install evolution-foundation/evo-nexus trigger-registry --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.claude/skills/trigger-registry .claude/skills/trigger-registry && rm -rf skills-srcUse ~/.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/
Install the "trigger-registry" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/trigger-registry into .claude/skills/trigger-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-registry", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/trigger-registryType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add evolution-foundation/evo-nexus --skill trigger-registry -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install evolution-foundation/evo-nexus trigger-registry --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .agents/skills && cp -r skills-src/.claude/skills/trigger-registry .agents/skills/trigger-registry && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "trigger-registry" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/trigger-registry into .agents/skills/trigger-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-registry", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add evolution-foundation/evo-nexus --skill trigger-registry -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install evolution-foundation/evo-nexus trigger-registry --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/.claude/skills/trigger-registry .cursor/skills/trigger-registry && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "trigger-registry" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/trigger-registry into .cursor/skills/trigger-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-registry", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/evolution-foundation/evo-nexus.git --path .claude/skills/trigger-registry--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add evolution-foundation/evo-nexus --skill trigger-registry -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install evolution-foundation/evo-nexus trigger-registry --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/.claude/skills/trigger-registry .gemini/skills/trigger-registry && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "trigger-registry" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/trigger-registry into .gemini/skills/trigger-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-registry", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install evolution-foundation/evo-nexus trigger-registryInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add evolution-foundation/evo-nexus --skill trigger-registry -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .github/skills && cp -r skills-src/.claude/skills/trigger-registry .github/skills/trigger-registry && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "trigger-registry" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/trigger-registry into .github/skills/trigger-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-registry", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add evolution-foundation/evo-nexus --skill trigger-registry -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install evolution-foundation/evo-nexus trigger-registry --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/evolution-foundation/evo-nexus.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/.claude/skills/trigger-registry .opencode/skills/trigger-registry && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "trigger-registry" agent skill from https://github.com/evolution-foundation/evo-nexus/tree/main/.claude/skills/trigger-registry into .opencode/skills/trigger-registry/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "trigger-registry", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
trigger-registry- GitHub stars
- 544
- Token cost
- ~1.4k tokens
- SKILL.md length
- 418 words
- Files
- 1
- Skills in repo
- 117
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Create, manage, and test reactive triggers (webhook & event-based).
- Works in 4 steps: Understand the request — extract what… → Confirm with user — show summary → Create via API → …
- (webhook & event-based)
- SKILL.md covers When to Use, API Reference, Trigger Types and Sources & Event Examples, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Trigger Registry is an agent skill from evolution-foundation/evo-nexus. 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.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Backend & APIs, covering Webhooks. It works with GitHub, Stripe and Linear. The repository describes itself as: The open source operating system for AI-powered businesses.
When your agent uses it
- (webhook & event-based)
- Routines in response to external events (GitHub push
- User says create trigger
- Quando acontecer
Example prompts
- “create trigger”
- “list triggers”
- “novo trigger”
- “/trigger-registry”
Requirements
- Python 3
Workflow steps
4 steps, taken from the first numbered list in SKILL.md.
- Understand the request — extract what event, what action, which agent
- Confirm with user — show summary
- Create via API
- Show result — display webhook URL and secret for configuration
What it can do on your machine
Read from SKILL.md and the folder at commit 7f5dd76. 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
No scripts in the folder and no shell commands in SKILL.md (its code samples are python).
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
Trigger Registry loads about 1.4k tokens when it runs. Until then it costs about 96 tokens; SKILL.md has 418 words of instructions outside code blocks.
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
Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 418 words (~1,426 tokens).
“Create and manage triggers that execute skills or routines in response to external events (webhooks, integrations).”
- name
- trigger-registry
- metadata.author
- evonexus
- metadata.version
- 1.0
Files
Just SKILL.md in .claude/skills/trigger-registry of evolution-foundation/evo-nexus.
Open the folder on GitHubat commit 7f5dd76
Compare with similar skills
Trigger Registry 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Trigger Registry this skillevolution-foundation/evo-nexus | 544 | — | ~1.4k | Automated safety check: Pass | Custom licence | |
| Ade Webhooksarul28/ADE | 113 | — | ~2.1k | Automated safety check: Pass | AGPL-3.0 | |
| Webhook SubscriptionsTommy-yw/RunbookHermes | 546 | 1 repos | ~1.7k | Automated safety check: Notes | MIT | |
| Production Auditsickn33/agentic-awesome-skills | 47k | 1 repos | ~2.7k | Automated safety check: Pass | MIT | |
| Webhook Subscriptionsmateaix/mateclaw | 1.1k | — | ~1.7k | Automated safety check: Notes | Apache-2.0 | |
| Emulate Seedyonatangross/orchestkit | 288 | — | ~4.5k | Automated safety check: Pass | MIT |
Similar skills
Webhook Subscriptions
Tommy-yw/RunbookHermes
Create and manage webhook subscriptions for event-driven agent activation, or for direct push notifications (zero LLM cost).
Production Audit
sickn33/agentic-awesome-skills
Audit a shipped repo for production-readiness gaps across RLS, webhooks, secrets, grants, Stripe idempotency, mobile UX, and deployment health.
Webhook Subscriptions
mateaix/mateclaw
Webhook subscriptions: event-driven agent runs. An agent skill from mateaix/mateclaw.
Emulate Seed
yonatangross/orchestkit
Generate emulate seed configs for stateful API emulation. An agent skill from yonatangross/orchestkit.
Webhook Subscriptions
RedWoodOG/Hermes-Desktop
Create and manage webhook subscriptions for event-driven agent activation.
More from evolution-foundation/evo-nexus
All 117 skills in this repoAI Image Creator
evolution-foundation/evo-nexus
Generates PNG images through OpenRouter models, with transparent backgrounds and reference-image edits, and describes existing images with multimodal vision.
MongoDB Query Client
evolution-foundation/evo-nexus
Runs read-only MongoDB finds, aggregations and collection listings against databases named in your .env, choosing the connection by label or index.
MySQL and MariaDB Query Tool
evolution-foundation/evo-nexus
Queries MySQL or MariaDB databases declared in .env by label, read-only by default unless a connection explicitly allows writes.
Postgres Query Client
evolution-foundation/evo-nexus
Runs read-only SQL queries and schema exploration against PostgreSQL databases declared in .env, chosen by label or index, with writes blocked unless a connection allows them.
Redis Inspector
evolution-foundation/evo-nexus
Reads keys and server state from Redis instances configured in .env through a read-only Python client, choosing connections by label or index.
Int Bling
evolution-foundation/evo-nexus
Bling ERP integration via API v3. An agent skill from evolution-foundation/evo-nexus.
Related
Categories
Questions about Trigger Registry
What does Trigger Registry do?
Create, manage, and test reactive triggers (webhook & event-based). Trigger Registry is an agent skill from evolution-foundation/evo-nexus. Create, manage, and test reactive triggers (webhook & event-based).
When should I use Trigger Registry?
Trigger Registry fits situations like: (webhook & event-based); routines in response to external events (GitHub push; user says create trigger; quando acontecer.
How do I install Trigger Registry in Claude Code?
Run `npx skills add evolution-foundation/evo-nexus --skill trigger-registry -a claude-code`. Or copy the skill folder (.claude/skills/trigger-registry in evolution-foundation/evo-nexus) into .claude/skills/trigger-registry in your project. Claude Code loads it when a task matches its description.
How do I install Trigger Registry in Codex?
Run `npx skills add evolution-foundation/evo-nexus --skill trigger-registry -a codex`. Or copy the skill folder (.claude/skills/trigger-registry in evolution-foundation/evo-nexus) into .agents/skills/trigger-registry in your project. Codex loads it when a task matches its description.
Can I use Trigger Registry 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 evolution-foundation/evo-nexus --skill trigger-registry -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/trigger-registry, .gemini/skills/trigger-registry, .github/skills/trigger-registry and .opencode/skills/trigger-registry in your project.
What does Trigger Registry need to run?
SKILL.md names no scripts, command-line tools or credentials: Trigger Registry is instructions for the agent only. Our summary lists: Python 3.
Does Trigger Registry 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 Trigger Registry 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 Trigger Registry use?
Trigger Registry has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.
How many tokens does Trigger Registry use?
About 1.4k tokens (SKILL.md is roughly 5.7k 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 Trigger Registry?
Skills that share tags, products or a category with Trigger Registry: Ade Webhooks (arul28/ADE, 113 stars), Webhook Subscriptions (Tommy-yw/RunbookHermes, 546 stars), Production Audit (sickn33/agentic-awesome-skills, 47k stars) and Webhook Subscriptions (mateaix/mateclaw, 1.1k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Trigger Registry?
evolution-foundation (a GitHub organization) maintains it in evolution-foundation/evo-nexus, which has 544 GitHub stars. The repository holds 117 skills in this directory. The repository was last updated on May 13, 2026.
Source: evolution-foundation/evo-nexus on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.