Name: webiny-event-handler-pattern
Rating: 68 (1 reviews)
Author: webiny

webiny-event-handler-pattern

EventHandler implementation pattern — handle method, event payloads, filtering, DI, domain event definition, publishing events from UseCases, and reacting to external events. Use this skill to implement any Webiny EventHandler (before/after hooks) or to define and publish your own domain events.

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

80%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A technically rich, highly actionable pattern reference with lean, copy-paste-ready code and strong mandatory guardrails. The main gaps are the absence of an explicit validation feedback loop and the lack of bundle files to progressively disclose the longer worked examples.

Suggestions

Add an explicit ordered checklist (define payload → define event class → register abstraction → publish from UseCase → react) with a validation checkpoint so the multi-step flow is unambiguous.

Move the full define/publish/react worked examples into a references/ file (e.g. DOMAIN_EVENTS.md) and link to it from SKILL.md to improve progressive disclosure.

Add a short validate/build step after the registration example (e.g. run a typecheck or deploy dry-run) to close the workflow feedback loop.

Dimension	Reasoning	Score
Conciseness	Lean and dense for its depth — uses a naming-convention table, concise 'Key Rules' bullets, and inline TS examples that assume competence; the few 'Why' rationales earn their place rather than padding.	3 / 3
Actionability	Multiple complete, copy-paste-ready TypeScript blocks with concrete imports, constructor DI, createImplementation wiring, and explicit registration syntax, plus specific commands like 'yarn webiny deploy api --env=dev'.	3 / 3
Workflow Clarity	Implementation and type-resolution steps are sequenced and include a MANDATORY 'read the source to verify types' checkpoint, but there is no validate→fix→retry feedback loop and some sequences (define events → publish → react) are described by example rather than as an explicit ordered checklist.	2 / 3
Progressive Disclosure	Sections are well organized with clear headers and one-level pointers to related skills, but all reference material (full abstractions/events/UseCase code) is inline in SKILL.md with no bundle files to offload the longer worked examples.	2 / 3
	Total	10 / 12 Passed

Description

85%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong, specific description that covers what the skill does and when to use it, with a distinct Webiny EventHandler niche. The main weakness is trigger phrasing that is slightly framework-jargon heavy and second-person in voice.

Suggestions

Reword the trigger in third person and surface the natural terms users say, e.g. 'Use when implementing Webiny before/after event hooks, defining domain events, or publishing events from UseCases'.

Lead with the most common user-facing phrasing ('before/after hooks', 'domain events') before the internal mechanism names to improve trigger term quality.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions — 'handle method, event payloads, filtering, DI, domain event definition, publishing events from UseCases, and reacting to external events' — rather than vague language.	3 / 3
Completeness	Clearly answers 'what' via the enumerated capabilities and 'when' with the explicit trigger 'Use this skill to implement any Webiny EventHandler (before/after hooks) or to define and publish your own domain events.'	3 / 3
Trigger Term Quality	Includes relevant terms like 'Webiny EventHandler', 'before/after hooks', and 'domain events', but the phrasing leans on framework jargon and 'Use this skill to implement' reads as second person rather than natural user speech.	2 / 3
Distinctiveness Conflict Risk	The Webiny-specific EventHandler niche with before/after-hook triggers is clearly distinguishable and unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: webiny/webiny-js
Path: skills/user-skills/api/event-handler-pattern/SKILL.md
Commit: 484553b

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.