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

—

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Quality

Content

65%

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

Highly actionable with executable end-to-end TypeScript, but the body is a monolithic wall of inline code that would benefit from progressive disclosure into reference files, and the destructive cleanup workflow lacks validation checkpoints.

Suggestions

Move the S3 persistence, lifecycle cleanup, and search/query implementations into separate reference files (e.g., references/cloud-storage.md, references/lifecycle.md) and keep SKILL.md as an overview pointing to them.

Add an explicit validation/dry-run step before destructive deletions in cleanupOldAssets (e.g., log planned deletions and require confirmation, or guard with a retention floor).

Verify the download actually succeeded and the record was persisted before marking generation complete, adding a checkpoint between download and metadata tracking.

Dimension	Reasoning	Score
Conciseness	Prose is lean and the URL-expiration fact earns its place, but ~250 lines of full inline TypeScript (S3, lifecycle, search) could be tightened or moved to reference files rather than kept monolithic in SKILL.md.	2 / 3
Actionability	Provides complete, copy-paste-ready TypeScript with real API calls, the GenerationRecord schema, and concrete functions for generate/download, S3 persist, reproduce, cleanup, and search.	3 / 3
Workflow Clarity	Steps are clearly sequenced (Step 1–6) with response-ok checks in the generation flow, but the destructive batch cleanupOldAssets lacks any validation, dry-run, or confirmation checkpoint, capping clarity at 2.	2 / 3
Progressive Disclosure	Sections are organized, but with no bundle/reference files everything is inline; substantial chunks (S3 storage, lifecycle, search) that should be one level deep are kept in the SKILL.md body.	2 / 3
	Total	9 / 12 Passed

Description

100%

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, well-formed description: it states concrete capabilities in third person, gives explicit 'Use when' guidance, and supplies natural trigger phrases scoped to a clear Ideogram niche. No fluff or over-claims.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions in third person — 'Manage Ideogram generated image assets, metadata tracking, and lifecycle management' — rather than a single vague verb.	3 / 3
Completeness	Explicitly answers both what (asset/metadata/lifecycle management) and when ('Use when implementing image persistence, tracking generation history...') with explicit trigger guidance.	3 / 3
Trigger Term Quality	Provides five natural phrases a user would actually say ('ideogram data', 'ideogram images', 'ideogram asset management', 'ideogram metadata', 'ideogram image storage'), giving good coverage.	3 / 3
Distinctiveness Conflict Risk	Tightly scoped to Ideogram with 'ideogram'-prefixed triggers, making it unlikely to fire for unrelated asset-management skills.	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
Commit: 1628598

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