ideogram-webhooks-events

Build event-driven workflows around Ideogram's synchronous API. Use when implementing async generation queues, batch processing, callback patterns, or image processing pipelines. Trigger with phrases like "ideogram webhook", "ideogram events", "ideogram async", "ideogram queue", "ideogram batch pipeline".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

72%

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

The body delivers highly actionable, executable code across four concrete async patterns, but the single-file inline approach and absence of validation checkpoints in the batch pipeline limit conciseness and workflow clarity. Strong on actionability, weaker on progressive disclosure and feedback loops.

Suggestions

Add an explicit validation/checkpoint step to the batch generation flow (e.g., wait for job completion and verify outputs before declaring the campaign done) to raise workflow clarity.

Move the longer code blocks (callback handler, sharp pipeline) into referenced files under scripts/ or references/ so SKILL.md stays a lean overview with one-level-deep links.

Trim redundant inline comments and consolidate the four examples to reduce token load without losing actionability.

Dimension	Reasoning	Score
Conciseness	The body is mostly executable code rather than prose, but it is lengthy (~225 lines) and embeds full working implementations inline (queue, worker, callback server, batch loop, sharp pipeline) that could be trimmed or referenced; it assumes Claude's competence yet earns its tokens unevenly.	2 / 3
Actionability	Each step provides complete, copy-paste-ready TypeScript with concrete endpoints, options (attempts, backoff, concurrency: 5), and real library usage (BullMQ, sharp, express), giving fully executable guidance.	3 / 3
Workflow Clarity	Steps are sequenced as Step 1-4, but the batch-generation pipeline lacks explicit validation/verification checkpoints for a destructive/batch operation (no post-submit confirmation that jobs completed, no verify-after-download step), which caps workflow clarity at 2.	2 / 3
Progressive Disclosure	Content is well-sectioned, but there are no bundle files and all detail is inline in one SKILL.md; the single cross-reference to 'ideogram-performance-tuning' is the only navigation, so material that could be split into references stays monolithic.	2 / 3
	Total	9 / 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 specific, trigger-rich, and explicitly answers both what the skill does and when to use it, with a clear Ideogram-scoped niche. It is slightly padded with blank lines and somewhat verbose phrasing but remains effective.

Dimension	Reasoning	Score
Specificity	Lists several concrete actions — 'async generation queues, batch processing, callback patterns, or image processing pipelines' — naming specific deliverables rather than vague language.	3 / 3
Completeness	Answers both what it does (build event-driven async workflows) and when to use it via an explicit 'Use when...' clause plus 'Trigger with phrases like...' guidance.	3 / 3
Trigger Term Quality	Provides natural trigger phrases users would say ('ideogram webhook', 'ideogram events', 'ideogram async', 'ideogram queue', 'ideogram batch pipeline') with good coverage of likely phrasings.	3 / 3
Distinctiveness Conflict Risk	The Ideogram-specific triggers carve a clear niche around this provider's async/event patterns, making it unlikely to fire for unrelated skills.	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: 4 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.