emitting-api-events

tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill 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".

48%

Overall

Validation — 81%

Implementation — 7%

Activation — 82%

SKILL.md

Review

Evals

Validation

81%

Warnings & errors only

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

	Total	13 / 16 Passed

Implementation

This skill content is a generic template that fails to address its stated purpose of building event-driven APIs with webhooks and Server-Sent Events. It contains no concrete code examples, no webhook-specific guidance, no SSE implementation details, and relies entirely on vague instructions and external file references. The content appears to be boilerplate that could apply to any API development task.

Suggestions

Add concrete, executable code examples for webhook registration, payload signing, retry logic, and SSE streaming endpoints

Include specific workflow steps for event-driven patterns: event definition → webhook subscription → payload delivery → acknowledgment handling

Remove generic prerequisites and overview text; replace with webhook-specific configuration (e.g., signature verification, delivery guarantees)

Add validation checkpoints for webhook delivery (verify signatures, handle retries, log delivery status) with explicit error recovery steps

Dimension	Reasoning	Score
Conciseness	Contains significant padding with generic boilerplate text ('This skill provides automated assistance for...'), redundant overview statements, and prerequisites that explain basic concepts Claude already knows (what testing tools are, what authentication strategies are).	1 / 3
Actionability	Provides only vague, abstract guidance with no concrete code examples, no executable commands, and no specific implementation details. Instructions like 'Generate boilerplate code' and 'Implement endpoint handlers' describe rather than instruct.	1 / 3
Workflow Clarity	Steps are poorly organized with duplicate numbering (two separate lists both starting at 1), no validation checkpoints, and no feedback loops for error recovery. The workflow for event-driven APIs (webhooks, SSE) is completely absent despite being the skill's stated purpose.	1 / 3
Progressive Disclosure	References external files (implementation.md, errors.md, examples.md) which is appropriate structure, but the main content is poorly organized and the references feel like placeholders rather than well-signaled navigation to specific advanced topics.	2 / 3
	Total	5 / 12 Passed

Activation

82%

This description has strong completeness with explicit 'Use when' and trigger phrases, and good trigger term coverage. However, it lacks specificity in describing concrete actions beyond 'build' and has moderate overlap risk with related real-time communication skills. The description would benefit from more specific capability details.

Suggestions

Add specific concrete actions like 'configure webhook endpoints, implement retry logic, manage event subscriptions, handle payload validation'

Differentiate from related skills by specifying what this skill does NOT cover (e.g., 'for HTTP-based event delivery, not WebSocket connections')

Dimension	Reasoning	Score
Specificity	Names the domain (event-driven APIs) and lists some technologies (webhooks, Server-Sent Events, real-time notifications), but doesn't describe concrete actions beyond 'build'. Missing specific operations like 'configure webhook endpoints', 'handle retry logic', or 'manage subscriptions'.	2 / 3
Completeness	Explicitly answers both what (build event-driven APIs with webhooks, SSE, real-time notifications) and when (with explicit 'Use when' clause and 'Trigger with phrases' providing clear activation guidance).	3 / 3
Trigger Term Quality	Includes good natural trigger terms: 'add webhooks', 'implement events', 'create event-driven API', 'Server-Sent Events', 'real-time notifications'. These are phrases users would naturally say when needing this functionality.	3 / 3
Distinctiveness Conflict Risk	Reasonably specific to event-driven patterns, but 'real-time notifications' and 'events' could overlap with WebSocket skills, push notification skills, or general API design skills. The webhook focus helps but isn't fully distinctive.	2 / 3
	Total	10 / 12 Passed

Reviewed

18 days ago

Table of Contents

Validation Implementation Activation

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.