ideogram-common-errors
Diagnose and fix Ideogram common 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".
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-common-errors77
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
89%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This is a well-structured skill description with strong completeness and excellent trigger term coverage. The explicit 'Use when' and 'Trigger with phrases' sections make it easy for Claude to select appropriately. The main weakness is that the specific capabilities could be more concrete - listing actual error types or debugging actions would strengthen specificity.
Suggestions
Add specific concrete actions like 'parse API error codes', 'validate authentication', 'check rate limits', or 'resolve timeout issues' to improve specificity
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (Ideogram) and general actions (diagnose, fix, debug), but lacks specific concrete actions like 'parse error codes', 'validate API keys', or 'check rate limits'. The actions remain somewhat abstract. | 2 / 3 |
Completeness | Clearly answers both what ('Diagnose and fix Ideogram common errors and exceptions') and when ('Use when encountering Ideogram errors, debugging failed requests, or troubleshooting integration issues') with explicit trigger guidance. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural trigger terms users would say: 'ideogram error', 'fix ideogram', 'ideogram not working', 'debug ideogram'. Also includes variations like 'debugging failed requests' and 'troubleshooting integration issues'. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive with 'Ideogram' as a specific product/service name. The combination of Ideogram + error handling creates a clear niche that is unlikely to conflict with other skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill has decent structure and progressive disclosure but underdelivers on its promise of '10 most common errors' by only documenting 3. The boilerplate sections (Overview, Prerequisites, Instructions, Output) consume tokens without adding value, and some solutions defer to other skills rather than providing complete guidance.
Suggestions
Remove the generic Instructions steps 1-3 and Output section - they add no actionable value and waste tokens
Either document all 10 promised errors or change the overview to accurately reflect the 3 errors covered
Add a verification step after each solution (e.g., 'Verify fix: run your request again and confirm 200 response')
Inline the rate limit exponential backoff code rather than deferring entirely to another skill
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill has some unnecessary scaffolding (Overview, Prerequisites, Instructions steps 1-3, Output section) that adds little value. The actual error solutions are reasonably concise, but the framing could be tightened significantly. | 2 / 3 |
Actionability | Provides some executable commands (curl, bash, typescript snippets) but several solutions are incomplete - the rate limit solution just defers to another skill, and only 3 of the promised '10 most common errors' are actually documented. | 2 / 3 |
Workflow Clarity | The escalation path provides a clear sequence, but the main diagnostic workflow (Steps 1-3) is generic and unhelpful. No validation checkpoints to confirm fixes worked beyond 'Verified resolution' in the Output section. | 2 / 3 |
Progressive Disclosure | Good structure with clear references to related skills (ideogram-rate-limits, ideogram-debug-bundle) and external resources. Content is appropriately organized with one-level-deep references. | 3 / 3 |
Total | 9 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 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 | 9 / 11 Passed | |
- Reviewed
Table of Contents
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.