CtrlK
BlogDocsLog inGet started
Tessl Logo

ideogram-reference-architecture

Implement Ideogram reference architecture with prompt templates, asset pipelines, and CDN delivery. Use when designing new Ideogram integrations, building brand asset systems, or establishing architecture for image generation at scale. Trigger with phrases like "ideogram architecture", "ideogram project structure", "ideogram brand assets", "ideogram pipeline design", "ideogram at scale".

65

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

Fix and improve this skill with Tessl

tessl review fix ./plugins/saas-packs/ideogram-pack/skills/ideogram-reference-architecture/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

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

Highly actionable, executable content with clear sequencing, but it is a monolithic file with no progressive disclosure and lacks validation checkpoints for its batch generation workflow.

Suggestions

Add an explicit validation/verification step to the asset pipeline (e.g., verify each generated file opens and is non-empty, and confirm the manifest matches written files before declaring success).

Split the template library and API client into one-level-deep reference files (e.g., references/templates.md, references/client.md) and keep SKILL.md as a concise overview with signaled links.

Add a retry/error-recovery loop for transient API failures (rate limits, expired URLs) in the generation service rather than only a fixed 3s delay.

DimensionReasoningScore

Conciseness

Mostly lean: code, an architecture diagram, and a compact error table with little concept-explanation padding, though the full four-template library and four code systems run ~270 lines that could be trimmed.

4 / 5

Actionability

Provides fully executable TypeScript hitting real Ideogram endpoints (generate, describe, remix) with real imports and complete functions, copy-paste ready and covering the common cases.

5 / 5

Workflow Clarity

Steps 1–4 are clearly sequenced, but the batch asset-generation pipeline has no validation or verification checkpoints before/after writes, capping this dimension at 3 per the batch-operation rule.

3 / 5

Progressive Disclosure

Well-sectioned with clear headers, but no bundle files exist and the full template library, API client, and pipeline are all inlined in a monolithic SKILL.md rather than split into one-level-deep reference files.

3 / 5

Total

15

/

20

Passed

Description

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

A strong description that clearly answers both 'what' and 'when' with concrete, Ideogram-specific triggers and low conflict risk. Specificity and trigger-term coverage are good but could be more comprehensive.

DimensionReasoningScore

Specificity

Names the Ideogram domain plus several concrete actions ('prompt templates, asset pipelines, and CDN delivery'), but the 'reference architecture' framing stays somewhat abstract rather than enumerating a comprehensive action set.

4 / 5

Completeness

Explicitly states what it does ('Implement Ideogram reference architecture with prompt templates, asset pipelines, and CDN delivery') and when to use it ('Use when designing new Ideogram integrations...'), plus concrete trigger phrases.

5 / 5

Trigger Term Quality

Lists five natural trigger phrases ('ideogram architecture', 'ideogram project structure', 'ideogram brand assets', 'ideogram pipeline design', 'ideogram at scale'), all ideogram-prefixed, but lacks synonyms and file/extension variants.

4 / 5

Distinctiveness Conflict Risk

Scoped to a single named API (Ideogram) with ideogram-prefixed triggers, giving it a clear niche and minimal overlap with other skills.

5 / 5

Total

18

/

20

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.