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

Quality

83%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Low

Low-risk findings worth noting

Quality

Content

80%Weight 40%Scale 1-5

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

A well-structured, actionable skill body with clean progressive disclosure and copy-paste-ready code. The main weakness is workflow clarity: batch operations need explicit validation/retry feedback loops rather than only implicit verification.

Suggestions

Add an explicit validate→fix→retry feedback loop for the batch worker (e.g., after processing, assert the callback payload shape and re-enqueue on failure with backoff) so the batch workflow has real checkpoints.

Tighten the Authentication and Overview prose by cutting SDK key-handling basics Claude already knows, keeping only Groq-specific guidance.

Make the per-step verification concrete with a checklist (e.g., 'confirm 200 + first token frame', 'confirm 202 ack + classification object') rather than the generic 'drive it with curl to confirm behavior'.

Dimension	Reasoning	Score
Conciseness	The body is largely lean and assumes competence (compact prerequisites, code-forward steps), with only minor over-explanation in the Authentication and Overview prose that could be trimmed.	4 / 5
Actionability	Step 1 is fully executable copy-paste TypeScript inline, and Steps 2–5 plus worked curl examples live in real, complete bundle files (implementation.md, examples.md), covering the common cases.	5 / 5
Workflow Clarity	Steps are clearly sequenced and "drive it with curl to confirm behavior" plus observable artifacts provide verification, but the batch-processing workflow lacks explicit validate→fix→retry checkpoints, so the batch-operations cap at 3 applies.	3 / 5
Progressive Disclosure	SKILL.md is a concise overview with one-level-deep, clearly signaled references to references/implementation.md and references/examples.md (both real files), with bulk detail appropriately split out for easy navigation.	5 / 5
	Total	17 / 20 Passed

Description

87%Weight 40%Scale 1-5

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, well-formed description that clearly states capabilities, gives explicit use-when guidance, and lists concrete trigger phrases in a distinct Groq niche. Minor room to sharpen action specificity and add a few more natural trigger synonyms.

Dimension	Reasoning	Score
Specificity	Names the Groq domain and several concrete patterns ("streaming", "batch processing", "async patterns", "real-time SSE endpoints", "batch processing pipelines"), but the actions are pattern-level rather than maximally granular, leaving minor coverage gaps.	4 / 5
Completeness	Explicitly answers what ("Build event-driven architectures with Groq streaming, batch processing, and async patterns") and when ("Use when setting up real-time SSE endpoints...") plus concrete trigger phrases, matching the top anchor.	5 / 5
Trigger Term Quality	Lists six natural trigger phrases ("groq streaming", "groq events", "groq SSE", "groq batch", "groq async", "groq event-driven") giving good keyword coverage with synonyms, though a few natural variations are absent.	4 / 5
Distinctiveness Conflict Risk	The Groq-specific niche and consistently "groq"-prefixed triggers make it clearly distinguishable from generic streaming/webhook skills with minimal conflict risk.	5 / 5
	Total	18 / 20 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/tons-of-skills-marketplace
Path: plugins/saas-packs/groq-pack/skills/groq-webhooks-events/SKILL.md
Commit: 88dcf65

Reviewed: 3 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.