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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

77%

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

A dense, highly actionable error reference with copy-paste code and a clear status-code diagnostic flow. Its main gaps are some internal redundancy and a large monolithic body that lacks real progressive-disclosure file splits.

Suggestions

De-duplicate the Quick Diagnostic Script against the 401 curl test (reference it instead of repeating it) and consider whether the closing Error Handling summary table adds enough over the per-error sections to justify its tokens.

Split the inline error catalog into one-level-deep reference files (e.g. references/errors.md or per-category files) and link them from a leaner SKILL.md overview, so the body acts as a navigational index.

Resolve the 'see ideogram-debug-bundle' pointer in Next Steps: either make it a real linked bundle file or remove the dangling reference.

Dimension	Reasoning	Score
Conciseness	The catalog is mostly efficient and avoids explaining concepts Claude already knows, but the Quick Diagnostic Script duplicates the 401 curl test almost verbatim and the closing Error Handling table rehashes each section's cause/fix, so not every token earns its place (anchor 2).	2 / 3
Actionability	Provides fully executable, copy-paste-ready guidance throughout: curl probes, TypeScript retry/download helpers, ImageMagick commands, a FormData example, and an exact wrong-vs-correct enum table for 400 errors.	3 / 3
Workflow Clarity	As a reference skill the core workflow is the diagnostic script, which sequences run-curl → branch on status code → map to fix via a case statement, an unambiguous single-action diagnostic that fits the simple-skill scoring note.	3 / 3
Progressive Disclosure	The body is a ~260-line inline error catalog — matching anchor 2's '200 lines of API reference that could be in a separate file' — that is well organized internally but monolithic, and the one cited reference ('see ideogram-debug-bundle') is neither a real link nor an existing bundle file.	2 / 3
	Total	10 / 12 Passed

Description

90%

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-formed description that clearly states capability, usage context, and natural trigger phrases for a distinct Ideogram-specific niche. Its only weakness is that the stated actions ('diagnose and fix') are somewhat broad rather than enumerating multiple concrete operations.

Dimension	Reasoning	Score
Specificity	Names the domain ('Ideogram API errors and exceptions') and two actions ('Diagnose and fix'), but these are broad verbs rather than the multiple granular concrete actions (e.g. extract, fill, merge) expected at anchor 3, so it sits at anchor 2.	2 / 3
Completeness	Explicitly answers what ('Diagnose and fix Ideogram API errors and exceptions') and when ('Use when encountering Ideogram errors, debugging failed requests...') with an explicit 'Use when' clause and trigger phrases, matching anchor 3.	3 / 3
Trigger Term Quality	Provides natural user phrasings — 'ideogram error', 'fix ideogram', 'ideogram not working', 'debug ideogram', plus error codes 'ideogram 422', 'ideogram 429' — giving good coverage of terms users would actually say.	3 / 3
Distinctiveness Conflict Risk	Targets a clear narrow niche (Ideogram API errors) with all triggers 'ideogram'-prefixed, making it unlikely to fire for unrelated skills.	3 / 3
	Total	11 / 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: about 4 hours 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.