ideogram-common-errors

Diagnose and fix Ideogram API errors and exceptions. Use when encountering Ideogram errors, debugging failed requests, or troubleshooting integration issues. Trigger with phrases like "ideogram error", "fix ideogram", "ideogram not working", "debug ideogram", "ideogram 422", "ideogram 429".

Quality

86%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

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

The content is a well-structured, highly actionable error reference with executable code for the common Ideogram failure modes and a diagnostic script that provides clear status-based feedback. Its main weaknesses are minor redundancy between the summary table/diagnostic script and the per-error sections, and a monolithic single-file structure that underuses progressive disclosure.

Suggestions

Remove the duplicated connectivity curl from the Quick Diagnostic Script or the 401 section, keeping the test in one place and referencing it from the other, to tighten conciseness.

Break the per-error Reference into a separate ERRORS.md reference file (one level deep) and keep SKILL.md as an overview + diagnostic script, improving progressive disclosure.

Add an explicit numbered diagnostic workflow (check key -> run diagnostic script -> map status -> apply fix -> verify) before the script so the validate/fix/retry loop is explicit rather than implied.

Dimension	Reasoning	Score
Conciseness	The body is efficient: one-line overview, terse Cause/Fix structure, tables and code blocks with no padding or explanations of concepts Claude already knows. It is not a 5 because the Error Handling summary table and the Quick Diagnostic Script rehash the auth/connectivity test already shown in the 401 section, a minor redundancy that could be trimmed.	4 / 5
Actionability	It provides copy-paste-ready curl, bash (ImageMagick), and TypeScript examples plus a wrong/correct parameter table that cover the common cases, matching the 'fully executable; specific examples cover the common cases' anchor.	5 / 5
Workflow Clarity	The Quick Diagnostic Script gives a clear status-code-branched sequence that maps each HTTP response to a diagnosis (a feedback loop), and the Output section lists expected results. It is not a 5 because the diagnostic flow is implied by the script rather than laid out as an explicit validate-then-fix-then-retry checklist.	4 / 5
Progressive Disclosure	Content is well-organized into clear sections (Overview, Prerequisites, per-error Reference, Diagnostic Script, Error Handling, Output, Resources, Next Steps) with no nested references. It is not a 5 because the ~260-line error reference is a single monolithic file that could be split, and the Next Steps pointer to 'ideogram-debug-bundle' is not a navigable one-level-deep reference within the bundle.	4 / 5
	Total	17 / 20 Passed

Description

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

The description is strong, explicitly stating what the skill does and when to use it with a comprehensive set of natural trigger phrases and a clearly distinct Ideogram-specific niche. The only weaker area is specificity, which states only two generic actions (diagnose, fix) rather than enumerating the concrete error categories it covers.

Suggestions

Expand the 'what' clause to name concrete capabilities, e.g. "Diagnose and fix Ideogram API errors and exceptions across auth, safety, rate-limit, credit, and request-format failures" to lift specificity.

Consider adding the file/endpoint context (e.g. "/generate and /v1/ideogram-v3 endpoints") to make the capability scope even more concrete.

Dimension	Reasoning	Score
Specificity	"Diagnose and fix Ideogram API errors and exceptions" names the domain and two concrete actions (diagnose, fix) but does not enumerate several specific actions, matching the anchor for 1-2 concrete actions rather than the 'several specific actions' of a 4.	3 / 5
Completeness	It explicitly answers 'what' ("Diagnose and fix Ideogram API errors and exceptions") and 'when' ("Use when encountering Ideogram errors, debugging failed requests, or troubleshooting integration issues") with concrete trigger phrases, matching the anchor that requires both with explicit triggers.	5 / 5
Trigger Term Quality	It lists six natural phrases users would actually say ("ideogram error", "fix ideogram", "ideogram not working", "debug ideogram", "ideogram 422", "ideogram 429"), including status-code variants, giving comprehensive coverage of natural trigger terms.	5 / 5
Distinctiveness Conflict Risk	The Ideogram-specific niche and ideogram-prefixed trigger phrases make it clearly distinguishable from other skills with minimal conflict risk, matching the 'clear niche with distinct triggers' anchor.	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/claude-code-plugins-plus-skills
Path: plugins/saas-packs/ideogram-pack/skills/ideogram-common-errors/SKILL.md
Commit: 0540a62

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.