Skip to content
TrustedSkillsbeta
Back to all skills

Webhook Receiver Hardener

Checked
patricio0312rev·vlatest·backend·MIT

Secures webhook integrations by validating payloads, limiting request rates, and preventing common injection attacks.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add patricio0312rev/skills --skill webhook-receiver-hardener -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

patricio0312rev

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned patricio0312rev/skills at 79ea6af485.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
79ea6af485
Manifest
backend/webhook-receiver-hardener/SKILL.md
Scanned
1 file, 200 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

The webhook-receiver-hardener skill secures incoming webhook requests by validating signatures and filtering malicious payloads before they reach your application logic. It acts as a protective gateway, ensuring only authenticated and safe data triggers downstream actions.

When to use it

  • Protecting public APIs that receive frequent external calls from unauthorized access attempts.
  • Filtering out malformed or suspicious JSON payloads in production environments.
  • Enforcing strict signature verification for services like Stripe, GitHub, or Slack integrations.
  • Preventing denial-of-service attacks by rejecting requests with invalid headers or excessive size.

Key capabilities

  • Validates webhook signatures using configurable secret keys.
  • Inspects request headers and body content for anomalies.
  • Blocks unauthenticated or tampered payloads automatically.
  • Logs security events for audit and monitoring purposes.

Example prompts

  • "Set up a hardened webhook receiver for my Stripe payment notifications with signature validation."
  • "Filter incoming GitHub webhooks to only accept signed requests from trusted repositories."
  • "Configure the webhook hardener to reject any payload larger than 10KB or missing the X-Signature header."

Tips & gotchas

Ensure you store your webhook secrets securely and never expose them in client-side code. This skill requires a backend endpoint capable of handling raw HTTP requests with signature verification logic enabled.