emitting-api-events

Build event-driven APIs with webhooks, Server-Sent Events, and real-time notifications. Use when building event-driven API architectures. Trigger with phrases like "add webhooks", "implement events", or "create event-driven API".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

70%

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

The body is well-structured with a clear sequenced workflow, validation, and clean one-level-deep references, but it leans verbose in places and delegates all executable code to examples.md rather than including a compact inline snippet.

Suggestions

Add one compact, copy-paste-ready code snippet inline for the highest-value step (e.g. the transactional outbox emitter) so the body is directly actionable without opening examples.md.

Tighten or relocate the Prerequisites and speculative Output file-path listing (e.g. into implementation.md) to improve token efficiency.

Curate references/errors.md and references/implementation.md to match the event-specific content — currently they contain generic API scaffolding/auth/rate-limit material that does not extend the webhook/SSE/outbox guidance in the body.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and free of concept-explanation fluff, but the Prerequisites list, the speculative Output file-path listing, and the inline error table/examples overlap with the reference files and could be tightened.	2 / 3
Actionability	Guidance is specific (exact endpoints, schema fields, HMAC-SHA256, retry schedule 1min/5min/30min/2hr/24hr) but the body itself contains no executable code — the copy-paste-ready code lives in examples.md — so it is not fully copy-paste ready.	2 / 3
Workflow Clarity	An explicit 8-step sequence ends with a verification step (integration tests covering emission, signature verification, SSE reconnection, dead-letter), and the Error Handling table supplies retry/deactivation/dead-letter feedback loops.	3 / 3
Progressive Disclosure	The body is an overview that signals three real one-level-deep references (implementation.md, errors.md, examples.md) with clear navigation; content is appropriately split across files.	3 / 3
	Total	10 / 12 Passed

Description

100%

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

The description is concrete, gives explicit "Use when" trigger guidance plus natural trigger phrases, and occupies a clear niche. It satisfies all four dimensions at the top of the scale.

Dimension	Reasoning	Score
Specificity	"Build event-driven APIs with webhooks, Server-Sent Events, and real-time notifications" names the domain plus three concrete delivery mechanisms, matching the multi-specific-action anchor rather than the single-action level 2.	3 / 3
Completeness	It states what (build event-driven APIs with webhooks/SSE/notifications) and an explicit "Use when building event-driven API architectures" trigger clause, so both what and when are clearly answered.	3 / 3
Trigger Term Quality	Explicit natural phrases — "add webhooks", "implement events", "create event-driven API" — are things a user would actually say, giving good coverage rather than just some relevant keywords.	3 / 3
Distinctiveness Conflict Risk	The event-driven-API/webhook/SSE niche with distinct trigger phrases is unlikely to fire for unrelated skills, fitting the clear-niche anchor.	3 / 3
	Total	12 / 12 Passed

Validation

87%

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 — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
allowed_tools_field	'allowed-tools' contains unusual tool name(s)	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	14 / 16 Passed

Repository: jeremylongshore/claude-code-plugins-plus-skills
Commit: 607d11b

Reviewed: 5 days 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.