ideogram-core-workflow-a

Execute Ideogram primary workflow: text-to-image generation with text rendering. Use when generating images from text prompts, creating designs with embedded text, or building the main image generation pipeline. Trigger with phrases like "ideogram generate image", "ideogram text to image", "create image with ideogram", "ideogram primary workflow".

Quality

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

A highly actionable skill with complete, executable code for both API endpoints, but it is held back by duplicated use-case content, a missing validation checkpoint in the batch workflow, and a monolithic structure that keeps reference material inline instead of splitting it into bundle files.

Suggestions

Remove the Overview's inline use-case list ('social media graphics, marketing banners, product mockups, posters, logos...') since Step 1's parameter table already conveys use-case guidance; let the table carry that information.

Move the 30+ V3 style-preset enumeration (and optionally the full V3 endpoint code) into a references/ file such as STYLE_PRESETS.md and link to it from the body, so SKILL.md stays a lean overview.

Add a validation checkpoint to the batch generation workflow (Step 5): verify each generated image downloaded successfully and retry on failure before proceeding to the next variation.

Dimension	Reasoning	Score
Conciseness	Mostly efficient code-and-tables body, but the Overview's use-case enumeration ('social media graphics, marketing banners, product mockups, posters, logos...') duplicates Step 1's parameter table, and the 30-item style-preset list is a long inline enumeration that could be tightened.	2 / 3
Actionability	Provides two complete, executable TypeScript functions (legacy fetch + download, and V3 multipart) plus concrete text-in-image and batch examples that are copy-paste ready.	3 / 3
Workflow Clarity	Steps 1-5 are numbered and sequenced, but Step 5 (batch generation) has no validation/feedback checkpoint -- images are not verified after download and there is no retry-on-failure loop, which caps batch workflow clarity at 2 per the rubric.	2 / 3
Progressive Disclosure	Well-organized into sections, but it is a monolithic ~190-line SKILL.md with no bundle files; reference-like material (the 50+ style presets, full V3 endpoint code, error tables) sits inline rather than being split into one-level-deep reference files.	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.

A well-crafted description that follows the recommended pattern: a concrete capability statement, an explicit 'Use when' clause, and natural trigger phrases tied to a distinct, named service. It scores at the top of every dimension.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions -- 'text-to-image generation with text rendering', 'generating images from text prompts', 'creating designs with embedded text', 'building the main image generation pipeline' -- rather than vague language.	3 / 3
Completeness	Explicitly answers both 'what' ('Execute Ideogram primary workflow: text-to-image generation with text rendering') and 'when' via an explicit 'Use when...' clause plus 'Trigger with phrases like...', matching the top anchor.	3 / 3
Trigger Term Quality	Provides natural trigger phrases a user would say ('ideogram generate image', 'ideogram text to image', 'create image with ideogram'); only 'ideogram primary workflow' reads as internal jargon, but natural-term coverage is strong.	3 / 3
Distinctiveness Conflict Risk	Targets a clear niche -- the named Ideogram service with service-specific triggers -- 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: 3022dd3

Reviewed: 1 day 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.