make-webhook
Skill4 starsChanged 2 months agoMITView on GitHub
Use when the application should receive webhooks from an external service such as Stripe or GitHub.
In this repository24 other files it gives its agents.
- AGENTS.mdAGENTS.md
- cli-conventionsSkill
- componentsSkill
- configurationSkill
- discoverSkill
- make-ciSkill
- make-commandSkill
- make-controllerSkill
- make-crudSkill
- make-decoratorSkill
- make-entitySkill
- make-formSkill
- make-listenerSkill
- make-migrationSkill
- make-registration-formSkill
- make-reset-passwordSkill
- make-security-customSkill
- make-security-form-loginSkill
- make-testSkill
- make-twig-extensionSkill
- make-userSkill
- make-voterSkill
- servicesSkill
- templatesSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 32
Verification: Check the service's signature header in the parser and throw RejectWebhookException on mismatch.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Webhook receiver
symfony console make:webhook stripeThe name is the argument (letters, digits, underscores, dots and dashes) and becomes the
key the webhook is reachable under. The maker installs symfony/webhook itself and adds
the entry to config/packages/webhook.yaml.
What you get
Two classes, and the split is the point: a request parser extending
AbstractRequestParser that turns the HTTP request into a RemoteEvent, and a consumer
marked #[AsRemoteEventConsumer] that reacts to it. Parsing and verification live in
the parser; what the application does about the event lives in the consumer.
What is yours
- The request matcher. Interactively the maker asks which matchers apply (method,
path, host, IPs, JSON); non-interactively it asks nothing, so the generated
getRequestMatcher()starts wide. Tighten it to what the sender actually does. - Verification. Check the service's signature header in the parser and throw
RejectWebhookExceptionon mismatch. A webhook endpoint without verification accepts events from anyone who finds the URL.
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
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.