Vercel Webhooks
ListedAutomates webhooks from Robinbg's tools to trigger actions on external services via Vercel Functions.
Install on your platform
Showing Claude Code. One command installs this skill into any of the agents below.
- 1
Run this in your project
terminal$ npx skills add robinbg/webhook-skills --skill vercel-webhooks -a claude-code Uses the open-source
skillsCLI and needs Node.js. Add-gto install it for your user instead of this project.
What we know about this skill
Publisher
robinbg
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.
Automated safety checks
This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.
No undeclared network calls: failed
Contacts 1 host that is neither well-known infrastructure nor declared in the skill's frontmatter: test-app.vercel.app.
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.
Hosts contacted
test-app.vercel.appundeclaredWhat it found (3 of 7)
- skills/vercel-webhooks/examples/express/test/webhook.test.js:45contacts test-app.vercel.app
url: 'https://test-app.vercel.app' - skills/vercel-webhooks/examples/express/test/webhook.test.js:117contacts test-app.vercel.app
url: 'https://test-app.vercel.app', - skills/vercel-webhooks/examples/fastapi/test_webhook.py:71contacts test-app.vercel.app
"url": "https://test-app.vercel.app"
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 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 robinbg/webhook-skills at a950a4a6b2.
The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.
- Commit
- a950a4a6b2
- Manifest
- skills/vercel-webhooks/SKILL.md
- Scanned
- 18 files, 2,642 lines
About this skill
What it does
This skill allows your AI agent to send HTTP requests (POST, PUT, DELETE) to Vercel webhook endpoints. It's designed to integrate with Vercel deployments and trigger actions based on events or data changes within your AI workflow. The skill handles the complexities of constructing and sending these requests, simplifying integration for users.
When to use it
- Automated Deployments: Trigger a deployment pipeline in Vercel after an agent completes a specific task.
- Data Synchronization: Send updated data from your AI agent to a Vercel-hosted application or database.
- Event Notifications: Notify a Vercel webhook of events happening within the AI agent's environment, such as completion of a complex process.
- API Interactions: Interact with Vercel functions and APIs programmatically through webhooks.
Key capabilities
- Sends HTTP requests (POST, PUT, DELETE) to Vercel endpoints.
- Handles request construction based on provided parameters.
- Integrates seamlessly with Vercel deployments.
Example prompts
- "Send a POST request to
https://your-vercel-app.com/api/updatewith the data{ "status": "completed" }." - "Delete the resource at
https://your-vercel-app.com/api/resource/123." - “Send a PUT request to update the status of order #456789”
Tips & gotchas
- Ensure you have proper authentication or authorization headers configured for your Vercel webhook endpoints. The skill does not handle authentication directly; this must be managed externally and passed in the request.