CtrlK
BlogDocsLog inGet started
Tessl Logo

ideogram-performance-tuning

Optimize Ideogram API performance with caching, model selection, and parallel generation. Use when experiencing slow generation, implementing caching strategies, or optimizing throughput for Ideogram integrations. Trigger with phrases like "ideogram performance", "optimize ideogram", "ideogram latency", "ideogram caching", "ideogram slow", "ideogram speed".

67

Quality

82%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

65%Weight 40%Scale 1-3

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

The content is highly actionable with executable, copy-paste-ready code and a clear four-step sequence, but it is held back by redundant prose sections, missing validation checkpoints in the batch workflow, and no progressive disclosure into bundle files.

Suggestions

Add explicit validation/retry checkpoints to the parallel generation workflow (e.g., verify cache hits, retry on 429 with backoff, confirm images downloaded before declaring success) to lift workflow clarity.

Trim the Overview, Performance Tips, and Output sections to remove content already demonstrated by the code examples, improving token efficiency.

Move the cache layer and CDN upload implementations into reference files (e.g., references/caching.md, references/cdn.md) and link to them from SKILL.md to improve progressive disclosure.

DimensionReasoningScore

Conciseness

Mostly value-dense (latency table, concrete model configs), but the Overview, Performance Tips, and Output sections restate what the code already shows and could be tightened; it avoids explaining concepts Claude already knows, so it is not a 1, but the redundancy keeps it off 3.

2 / 3

Actionability

The TypeScript examples use real endpoints, real imports, and complete functions (cachedGenerate, parallelGenerate, generateWithCDN) that are copy-paste ready, matching the fully-executable anchor.

3 / 3

Workflow Clarity

Steps 1–4 are clearly sequenced, but the batch/parallel generation workflow has no explicit validation checkpoints or retry feedback loops, and the rubric caps batch operations without validation at 2.

2 / 3

Progressive Disclosure

Sections are clearly labeled and well-organized, but all content lives inline in a single ~200-line file with no bundle references, and substantial code blocks (cache layer, CDN upload) could be split out; not a 1 because organization is clear, not a 3 because nothing is offloaded.

2 / 3

Total

9

/

12

Passed

Description

100%Weight 40%Scale 1-3

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 cleanly answers both what it does and when to use it, with concrete actions and natural trigger phrases scoped to a distinct niche. It is a strong, low-conflict description.

DimensionReasoningScore

Specificity

"Optimize Ideogram API performance with caching, model selection, and parallel generation" lists multiple concrete actions, matching the score-3 anchor of naming several specific actions.

3 / 3

Completeness

It states what ("Optimize Ideogram API performance with caching, model selection, and parallel generation") and explicitly when ("Use when experiencing slow generation, implementing caching strategies, or optimizing throughput"), satisfying both halves with explicit triggers.

3 / 3

Trigger Term Quality

Phrases "ideogram performance", "optimize ideogram", "ideogram latency", "ideogram caching", "ideogram slow", and "ideogram speed" are natural terms a user would say, giving good coverage.

3 / 3

Distinctiveness Conflict Risk

The narrow Ideogram-performance niche with distinctive trigger phrases is unlikely to overlap with or conflict against other skills.

3 / 3

Total

12

/

12

Passed

Validation

87%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

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