CtrlK
BlogDocsLog inGet started
Tessl Logo

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".

59

Quality

70%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./plugins/api-development/api-event-emitter/skills/emitting-api-events/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%Weight 40%Scale 1-3

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

The skill is well-structured with excellent progressive disclosure — a concise overview pointing to real, one-level-deep reference files. It loses marks for providing no executable code in the main body and for lacking explicit validation feedback loops inside the multi-step workflow.

Suggestions

Add at least one copy-paste-ready code snippet in the body (e.g., the HMAC-SHA256 signing function or the outbox publish loop) so guidance is executable without opening references.

Insert explicit validate-then-fix checkpoints into the numbered workflow for delivery and replay operations, rather than relegating them to the Error Handling table.

Trim the Output section to the non-obvious deliverables; several src/ paths are implied by the steps and could be condensed.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's intelligence rather than explaining basics, but it is padded with enumerated prerequisites and an Output section that lists seven file paths largely derivable from the instructions, so it could be tightened.

2 / 3

Actionability

Steps name concrete specifics (HMAC-SHA256, exponential backoff schedule, endpoint paths, event envelope fields) but provide no executable code in the body — guidance is descriptive rather than copy-paste ready, and code lives only in references/examples.

2 / 3

Workflow Clarity

The eight steps are clearly sequenced and include validation via integration tests (step 8), but for risky batch/destructive operations (webhook delivery, dead-letter replay) there are no explicit validate-fix-retry feedback checkpoints within the workflow itself — those live only in the Error Handling table.

2 / 3

Progressive Disclosure

The body is a well-organized overview that signals three one-level-deep references (implementation.md, errors.md, examples.md), all of which are real files with no nested .md chaining, so navigation is clear and content is appropriately split.

3 / 3

Total

9

/

12

Passed

Description

80%Weight 40%Scale 1-3

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 answers both what and when with explicit, distinctive trigger phrases for a clear niche, so completeness and distinctiveness are strong. Specificity and trigger-term coverage fall just short of top marks because capabilities are stated as a noun phrase and the trigger set is somewhat narrow.

Suggestions

Convert the capability list from a noun phrase into concrete actions, e.g. "Emit, deliver, and subscribe to API events via webhooks and SSE" to lift specificity.

Broaden trigger phrases with natural variations users say, such as "send webhooks", "set up SSE", "publish events", or "real-time notifications".

DimensionReasoningScore

Specificity

It names a concrete domain ("event-driven APIs with webhooks, Server-Sent Events, and real-time notifications") but lists capabilities as a single noun phrase rather than multiple discrete actions like the score-3 example ("extract, fill, merge").

2 / 3

Completeness

It explicitly answers what (build event-driven APIs with webhooks/SSE/notifications) and when ("Use when building event-driven API architectures") plus trigger phrases, matching the score-3 anchor of clear what-and-when with explicit triggers.

3 / 3

Trigger Term Quality

It offers explicit phrases ("add webhooks", "implement events", "create event-driven API"), but the set is narrow and omits common natural variations a user might say such as "SSE", "subscribe", "publish events", or "real-time notifications".

2 / 3

Distinctiveness Conflict Risk

The webhook/SSE/real-time-notification niche with its specific trigger phrases is distinct from general API or messaging skills and unlikely to fire for the wrong skill.

3 / 3

Total

10

/

12

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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
Reviewed

Table of Contents

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.