CtrlK
BlogDocsLog inGet started
Tessl Logo

groq-webhooks-events

Build event-driven architectures with Groq streaming, batch processing, and async patterns. Use when setting up real-time SSE endpoints, batch processing pipelines, or event-driven LLM processing with Groq. Trigger with phrases like "groq streaming", "groq events", "groq SSE", "groq batch", "groq async", "groq event-driven".

71

Quality

88%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

77%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.

A well-structured, highly actionable skill with executable code and clean progressive disclosure into two real reference files. Its main gap is the absence of explicit validation/retry checkpoints for batch and async operations, and some restated background prose that could be trimmed.

Suggestions

Add explicit validation/retry checkpoints to the batch and webhook workflows (e.g. verify the callback was received, retry failed queue items with backoff) so workflow_clarity can reach 3.

Trim restated background in the Overview and Prerequisites sections (e.g. explanations of SSE and Groq's latency) to tighten conciseness toward the lean anchor.

Make the Event Pattern Summary table's redundancy with the inline step descriptions explicit or consolidate, since model/latency values are time-sensitive and duplicate information already in the step list.

DimensionReasoningScore

Conciseness

Mostly efficient with executable code and tight tables, but the Overview/Prerequisites/Authentication prose and the Event Pattern Summary table restate context (e.g. explaining that Groq has sub-second latency, what SSE is) that partially pads beyond what Claude needs.

2 / 3

Actionability

Provides fully executable TypeScript/Python/bash code with specific headers, rate-limit settings, models, and concrete curl examples — copy-paste ready across every pattern.

3 / 3

Workflow Clarity

Steps are clearly numbered and summarized, but there are no validation/verification checkpoints for batch and async operations — the batch worker and webhook processor lack an explicit confirm-or-retry loop, which caps workflow clarity at 2 per the rubric's batch-operation rule.

2 / 3

Progressive Disclosure

SKILL.md is a clear overview with well-signaled one-level-deep references to references/implementation.md and references/examples.md (both real files); content is appropriately split and navigation is explicit.

3 / 3

Total

10

/

12

Passed

Description

100%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.

A strong, specific description that names concrete capabilities, provides explicit trigger phrases prefixed with 'groq', and clearly answers both what and when. It is well-scoped to the Groq event-pattern niche and unlikely to conflict with other skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: 'Build event-driven architectures with Groq streaming, batch processing, and async patterns' — streaming, batch, and async are named capabilities, not vague language.

3 / 3

Completeness

Explicitly answers what (build event-driven architectures with streaming/batch/async) and when ('Use when setting up real-time SSE endpoints...') with explicit trigger guidance.

3 / 3

Trigger Term Quality

Good coverage of natural trigger phrases ('groq streaming', 'groq events', 'groq SSE', 'groq batch', 'groq async', 'groq event-driven') that a user would plausibly say.

3 / 3

Distinctiveness Conflict Risk

Clear Groq-specific niche with distinct triggers; the repeated 'groq' qualifier on each trigger term makes it unlikely to fire for unrelated skills.

3 / 3

Total

12

/

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.