ideogram-core-workflow-a
tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-core-workflow-aExecute Ideogram primary workflow: Core Workflow A. Use when implementing primary use case, building main features, or core integration tasks. Trigger with phrases like "ideogram main workflow", "primary task with ideogram".
Validation
75%| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 12 / 16 Passed | |
Implementation
42%This skill is essentially a template with no actual content - all code examples are placeholders, error handling is generic, and no concrete guidance is provided. While the structure and organization are reasonable, the complete lack of actionable, executable content makes this skill unusable in its current form.
Suggestions
Replace all placeholder code blocks with actual executable TypeScript examples showing real Ideogram API calls
Fill in the error handling table with actual errors, causes, and solutions specific to Ideogram workflows
Add validation checkpoints between steps (e.g., 'Verify initialization succeeded before proceeding to Step 2')
Remove or condense the Prerequisites section - Claude doesn't need to be told it needs valid credentials
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The structure is reasonable but contains placeholder content and some unnecessary sections like 'Prerequisites' that explain things Claude would know. The template-like nature adds tokens without value. | 2 / 3 |
Actionability | All code blocks are empty placeholders ('// Step 1 implementation'), the error handling table has placeholder values ('Error 1', 'Cause', 'Solution'), and no actual executable guidance is provided. | 1 / 3 |
Workflow Clarity | Steps are numbered and sequenced (Initialize, Execute, Finalize), but there are no validation checkpoints, no feedback loops for error recovery, and the steps themselves are empty placeholders with no actual instructions. | 2 / 3 |
Progressive Disclosure | Good structure with clear sections, appropriate references to external resources and related workflows (ideogram-core-workflow-b), and content is organized logically without deep nesting. | 3 / 3 |
Total | 8 / 12 Passed |
Activation
32%This description fails to communicate what the skill actually does, relying entirely on placeholder-like language ('Core Workflow A', 'primary use case') that provides no actionable information. While it attempts proper structure with trigger phrases, the content is too abstract for Claude to make informed skill selection decisions. The description reads like a template that was never filled in with actual capability details.
Suggestions
Replace 'Core Workflow A' and 'primary use case' with specific concrete actions (e.g., 'Generate AI images from text prompts, create variations, upscale images').
Add natural trigger terms users would actually say based on what Ideogram does (e.g., 'AI image generation', 'text-to-image', 'create artwork').
Define the distinct niche by specifying what makes this different from other image or AI skills (e.g., specific Ideogram features, file formats, or use cases).
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'primary workflow', 'Core Workflow A', 'primary use case', 'main features', and 'core integration tasks' without describing any concrete actions. No specific capabilities are listed. | 1 / 3 |
Completeness | Has a 'Use when' clause and trigger phrases, but the 'what' is essentially undefined - 'Core Workflow A' and 'primary use case' tell Claude nothing about what this skill actually does. The when clause exists but references equally vague concepts. | 2 / 3 |
Trigger Term Quality | Includes 'ideogram' as a relevant keyword and provides explicit trigger phrases, but the phrases are artificial ('ideogram main workflow', 'primary task with ideogram') rather than natural terms users would actually say. Missing domain-specific terms about what Ideogram actually does. | 2 / 3 |
Distinctiveness Conflict Risk | Extremely generic terms like 'primary workflow', 'main features', and 'core integration tasks' could apply to virtually any skill. Only 'ideogram' provides any distinctiveness, but without knowing what Ideogram does, this could easily conflict with other Ideogram-related skills. | 1 / 3 |
Total | 6 / 12 Passed |
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.