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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

80%

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

The content is highly actionable and token-efficient, built from complete executable examples with concrete model selection and helpful summary tables. Its weaknesses are structural: the batch workflow lacks an explicit validation/retry feedback loop, and nothing is split into reference files despite the document's length.

Suggestions

Add an explicit validate→retry→fix feedback loop to the BullMQ batch worker (e.g., retry failed jobs with exponential backoff and verify callback delivery before marking complete), since the rubric caps batch-workflow clarity without it.

Move the more auxiliary examples (e.g., the scheduled health monitor) into a reference file under references/ and link to it from SKILL.md, so the main file stays an overview with one-level-deep navigation.

Tighten the inline comments in the code blocks to only those that encode non-obvious intent (e.g., the 25-RPM limiter rationale), removing restating comments like 'Fire callback on completion'.

Dimension	Reasoning	Score
Conciseness	The body is code-forward and assumes competence — five complete executable TypeScript/Python examples with minimal prose, and no explanation of concepts Claude already knows (e.g., what SSE or a queue is). Length comes from legitimate, distinct code, not padding.	3 / 3
Actionability	Every example is fully executable, copy-paste ready code with imports and concrete model names ('llama-3.3-70b-versatile', 'llama-3.1-8b-instant'), matching the 'fully executable code/commands' anchor.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1–5) and an Error Handling table exists, but the batch-processing workflow (Step 2) has no explicit validate→retry→fix checkpoint in code; the rubric caps batch-operation workflows missing validation at 2.	2 / 3
Progressive Disclosure	Sections are well-organized, but all ~265 lines of content (five full code examples) live inline in a single file with no bundle files (references/scripts/assets absent) and no content split into one-level-deep references; the under-50-line exemption does not apply.	2 / 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 concise and concrete, naming specific event-driven patterns, providing an explicit 'Use when' clause, and listing natural trigger phrases scoped to Groq. It cleanly satisfies all four dimensions with no vague fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'Groq streaming, batch processing, and async patterns' — rather than vague language, matching the 'lists multiple specific concrete actions' anchor.	3 / 3
Completeness	Explicitly answers both what ('Build event-driven architectures with Groq streaming, batch processing, and async patterns') and when ('Use when setting up real-time SSE endpoints...'), with an explicit 'Use when' trigger clause.	3 / 3
Trigger Term Quality	Provides good coverage of natural phrases a user would say — 'groq streaming', 'groq events', 'groq SSE', 'groq batch', 'groq async', 'groq event-driven' — matching the 'good coverage of natural terms' anchor.	3 / 3
Distinctiveness Conflict Risk	The Groq-specific niche plus 'groq'-prefixed triggers make it clearly distinguishable and unlikely to fire for unrelated skills, matching the 'clear niche with distinct triggers' 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: 1628598

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