ideogram-data-handling

Manage Ideogram generated image assets, metadata tracking, and lifecycle management. Use when implementing image persistence, tracking generation history, or building asset management for Ideogram outputs. Trigger with phrases like "ideogram data", "ideogram images", "ideogram asset management", "ideogram metadata", "ideogram image storage".

Quality

90%

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

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

A highly actionable, concise skill body built around complete executable code and a clear step sequence. Its weaknesses are the missing validation/feedback loop around the destructive cleanup operation and a monolithic single-file structure with no progressive disclosure.

Suggestions

Add a validation/confirmation checkpoint before destructive operations: e.g., in cleanupOldAssets, log a dry-run summary of records to delete and require confirmation, then verify deletion counts match before pruning the metadata store.

Split the large inline implementations into bundle files (e.g., references/schema.md for the GenerationRecord schema, scripts/persist.ts for the generation/storage code) and reference them one level deep from SKILL.md to improve progressive disclosure.

Remove or tighten the redundant "## Output" section, which restates capabilities already demonstrated by the code, to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Lean prose that assumes Claude's competence (no explaining of S3, images, or basic APIs); the bulk is purposeful executable code with only mild restatement in the "## Output" section.	3 / 3
Actionability	Full executable TypeScript with real imports, real API endpoints (api.ideogram.ai/generate), and complete functions that are copy-paste ready rather than pseudocode.	3 / 3
Workflow Clarity	Steps 1–6 are sequenced and the download flow throws on failure, but the destructive cleanupOldAssets operation has no validation/confirmation checkpoint or fix-and-retry feedback loop, capping this dimension at 2 per the rubric.	2 / 3
Progressive Disclosure	No bundle files exist and the ~250-line SKILL.md is monolithic with full implementations inline that could be split into reference files; sections are well-organized but there is no one-level-deep internal referencing.	2 / 3
	Total	10 / 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.

A strong, specific description that names concrete actions, includes natural trigger phrases, and answers both what and when. Minor formatting noise (stray blank lines splitting sentences) does not undermine clarity.

Dimension	Reasoning	Score
Specificity	"Manage Ideogram generated image assets, metadata tracking, and lifecycle management" plus "image persistence, tracking generation history" lists multiple specific concrete actions rather than vague language.	3 / 3
Completeness	It explicitly states what ("Manage Ideogram generated image assets, metadata tracking, and lifecycle management") and when ("Use when implementing image persistence, tracking generation history") with explicit triggers.	3 / 3
Trigger Term Quality	Trigger phrases "ideogram data", "ideogram images", "ideogram asset management", "ideogram metadata", "ideogram image storage" are natural terms a user would say, with good coverage of variations.	3 / 3
Distinctiveness Conflict Risk	The Ideogram-specific niche and distinct trigger phrases make it clearly distinguishable and unlikely to fire for the wrong skill.	3 / 3
	Total	12 / 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
Path: plugins/saas-packs/ideogram-pack/skills/ideogram-data-handling/SKILL.md
Commit: 4c47e33

Reviewed: 3 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.