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".
64
77%
Does it follow best practices?
Impact
—
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./plugins/saas-packs/ideogram-pack/skills/ideogram-data-handling/SKILL.mdQuality
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 solid skill description that clearly identifies its niche (Ideogram image asset management) and provides explicit trigger guidance. Its main weakness is that the capability descriptions lean toward abstract terms like 'lifecycle management' and 'metadata tracking' rather than listing concrete specific actions. The explicit trigger phrase list and clear 'Use when' clause are strong points.
Suggestions
Replace abstract terms like 'lifecycle management' and 'metadata tracking' with concrete actions such as 'store image URLs and prompts', 'query generation history by date or prompt', 'delete or archive expired assets'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain (Ideogram image assets) and mentions some actions like 'metadata tracking' and 'lifecycle management', but these are somewhat abstract. It doesn't list concrete specific actions like 'store image URLs', 'query generation history', or 'delete expired assets'. | 2 / 3 |
Completeness | The description clearly answers both 'what' (manage Ideogram image assets, metadata tracking, lifecycle management) and 'when' (implementing image persistence, tracking generation history, building asset management) with explicit trigger phrases listed. | 3 / 3 |
Trigger Term Quality | The description explicitly lists natural trigger phrases including 'ideogram data', 'ideogram images', 'ideogram asset management', 'ideogram metadata', 'ideogram image storage'. These are terms users would naturally use when working with Ideogram-generated content. | 3 / 3 |
Distinctiveness Conflict Risk | The description is highly specific to Ideogram-generated image assets, which is a clear niche. The repeated use of 'Ideogram' as a qualifier makes it very unlikely to conflict with generic image management or other AI image generation skills. | 3 / 3 |
Total | 11 / 12 Passed |
Implementation
64%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill provides highly actionable, executable TypeScript code for Ideogram asset management with a critical domain insight about URL expiration. However, it's overly long for a single SKILL.md — search utilities, lifecycle management, and cloud storage could be split into referenced files. The workflow lacks explicit validation checkpoints for destructive operations like cleanup and post-download integrity checks.
Suggestions
Add validation checkpoints: verify downloaded file size > 0 and image integrity after download; add a dry-run mode to cleanupOldAssets before actual deletion.
Split cloud storage (S3), lifecycle management, and search/query into separate referenced files to improve progressive disclosure and reduce the main file's token footprint.
Remove the 'Output' section which merely summarizes what the code already demonstrates — it adds no new information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is fairly long with extensive code blocks. Some content is reasonable (the URL expiration warning is critical domain knowledge), but the search/query functions, storage report, and lifecycle management sections add bulk that Claude could easily derive. The error handling table is useful but the 'Output' section is redundant summary. | 2 / 3 |
Actionability | The code is fully executable TypeScript with concrete API calls, file I/O, S3 integration, and complete function signatures. Every step provides copy-paste ready code with real endpoints, headers, and data structures. | 3 / 3 |
Workflow Clarity | Steps are numbered and sequenced logically, and the critical 'download immediately' checkpoint is well-highlighted. However, there are no explicit validation steps after download (e.g., verify file size > 0, verify image integrity), and the cleanup operation is destructive without a dry-run or confirmation step, which should cap this at 2. | 2 / 3 |
Progressive Disclosure | The content is structured with clear sections and a table, but it's monolithic — the S3 storage, lifecycle management, and search/query sections could be split into separate reference files. No bundle files exist to offload this content, and the single reference to 'ideogram-enterprise-rbac' is the only cross-reference. | 2 / 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 | |
- Commit
a04d1a2
- 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.