agentleFS
Sign inStart free
Martin-HausleitnerMartin-Hausleitner/martins-awesome-skills/skills/devops/webhook-subscriptions/SKILL.md

webhook-subscriptions

Skill3 starsChanged 6 months agoMITView on GitHub

Use when external services should trigger agent runs through webhook events

6 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 6 edited versions we read keep these.

  • 4

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Test with a synthetic payload.

    line 17
  2. Distinctive:

    Keep webhook secrets in environment variables or a private config file.

    line 39
  3. Distinctive:

    Do not commit event payloads from production systems.

    line 40
  4. Distinctive:

    Prefer dry-run delivery until the prompt is proven safe.

    line 41

“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Webhook Subscriptions

Overview

Webhook-triggered agents are powerful because they turn external events into work. Treat every webhook as an untrusted public input unless proven otherwise.

Setup Pattern

  1. Confirm the gateway or webhook receiver is available.
  2. Generate a strong per-subscription secret outside the repo.
  3. Subscribe to the smallest event set that solves the task.
  4. Test with a synthetic payload.
  5. Log only event metadata, not secret headers or private payload fields.

Example Shape

hermes webhook subscribe repo-issues \
  --events "issues" \
  --prompt "Triage this issue event and propose next steps." \
  --skills "github-issues,github-code-review"

Verification

hermes webhook list
hermes webhook test repo-issues --payload '{"action":"opened"}'

Safety

  • Require HMAC validation or an equivalent signature check.
  • Keep webhook secrets in environment variables or a private config file.
  • Do not commit event payloads from production systems.
  • Prefer dry-run delivery until the prompt is proven safe.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free