ideogram-core-workflow-b
Execute Ideogram secondary workflow: Core Workflow B. Use when implementing secondary use case, or complementing primary workflow. Trigger with phrases like "ideogram secondary workflow", "secondary task with ideogram".
Overall
score
31%
Does it follow best practices?
Validation for skill structure
Install with Tessl CLI
npx tessl i github:jeremylongshore/claude-code-plugins-plus-skills --skill ideogram-core-workflow-bActivation
7%This description fails to communicate what the skill actually does, relying entirely on placeholder-like language ('secondary workflow', 'Core Workflow B') that provides no meaningful information. The trigger terms are artificial and would never match natural user requests. This description would be nearly useless for skill selection in a multi-skill environment.
Suggestions
Replace abstract terms like 'secondary workflow' and 'Core Workflow B' with specific concrete actions (e.g., 'Generate image variations', 'Apply style transfers', 'Batch process images')
Add natural trigger terms that users would actually say, such as specific task names, file types, or outcome descriptions related to Ideogram's actual capabilities
Rewrite the 'Use when' clause to describe actual user scenarios and needs rather than referencing undefined workflow concepts
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description uses vague, abstract language like 'secondary workflow', 'secondary use case', and 'complementing primary workflow' without describing any concrete actions or capabilities. There is no indication of what the skill actually does. | 1 / 3 |
Completeness | The 'what' is completely missing - we have no idea what this skill does beyond vague references to 'secondary workflow'. While there is a 'Use when' clause, it provides no meaningful guidance since it references undefined concepts like 'secondary use case'. | 1 / 3 |
Trigger Term Quality | The trigger phrases 'ideogram secondary workflow' and 'secondary task with ideogram' are artificial constructs that users would never naturally say. No natural keywords describing actual tasks or outcomes are present. | 1 / 3 |
Distinctiveness Conflict Risk | The specific mention of 'Ideogram' and 'Core Workflow B' provides some distinctiveness from other skills, but the lack of concrete capability description means it could still conflict with other Ideogram-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
22%This skill is essentially a template or skeleton with no actual content. All code blocks are empty placeholders, the error handling section contains an irrelevant comparison table, and there's no actionable guidance whatsoever. The structure exists but serves no purpose without real implementation details.
Suggestions
Replace all placeholder code comments with actual executable TypeScript code showing real Ideogram API calls and operations
Add concrete step-by-step instructions explaining what each step accomplishes and how to verify success
Replace the comparison table in 'Error Handling' with actual error handling code and recovery procedures
Include at least one complete, working example that demonstrates the full workflow from start to finish
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is relatively brief but includes placeholder comments instead of actual code, and the comparison table in 'Error Handling' section doesn't actually handle errors - it's misplaced content that wastes tokens. | 2 / 3 |
Actionability | All code blocks contain only placeholder comments like '// Step 1 implementation' with no actual executable code. Claude cannot perform any concrete actions from this skill. | 1 / 3 |
Workflow Clarity | Steps are labeled but completely empty with no actual instructions. There are no validation checkpoints, no feedback loops, and the 'Error Handling' section contains a comparison table instead of error handling guidance. | 1 / 3 |
Progressive Disclosure | Structure is reasonable with clear sections and references to related skills (ideogram-install-auth, ideogram-core-workflow-a, ideogram-common-errors), but the main content is hollow, making the organization meaningless. | 2 / 3 |
Total | 6 / 12 Passed |
Validation
75%Validation — 12 / 16 Passed
Validation for skill structure
| 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 | |
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.