openai-image-gen
Generate images using OpenAI's DALL-E 3 API. Use when needing to create graphics, icons, backgrounds, or any visual assets. Requires OPENAI_API_KEY in environment.
81
71%
Does it follow best practices?
Impact
97%
3.46xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./data/skills-md/0xbigboss/claude-code/openai-image-gen/SKILL.mdQuality
Discovery
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.
This is a strong, well-crafted description that clearly identifies the tool (DALL-E 3), lists concrete use cases (graphics, icons, backgrounds, visual assets), includes an explicit 'Use when' clause, and mentions a practical prerequisite (OPENAI_API_KEY). It follows the third-person voice convention and is concise without being vague.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'generate images', 'create graphics, icons, backgrounds, or any visual assets'. Also specifies the concrete tool (DALL-E 3 API) and a prerequisite (OPENAI_API_KEY). | 3 / 3 |
Completeness | Clearly answers both what ('Generate images using OpenAI's DALL-E 3 API') and when ('Use when needing to create graphics, icons, backgrounds, or any visual assets') with an explicit 'Use when' clause. | 3 / 3 |
Trigger Term Quality | Includes strong natural trigger terms users would say: 'images', 'graphics', 'icons', 'backgrounds', 'visual assets', 'DALL-E', 'generate'. These cover common variations of how users request image generation. | 3 / 3 |
Distinctiveness Conflict Risk | Clearly scoped to image generation via DALL-E 3 specifically, which is a distinct niche. The mention of OpenAI's DALL-E 3 API and specific visual asset types makes it unlikely to conflict with other skills like general code generation or document processing. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
42%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The skill provides excellent actionability with concrete, executable commands, but is severely undermined by poor content organization. The vast majority of the document consists of project-specific Gothic cathedral presets that should be in a separate file, making the core skill hard to find. The tips and cost sections add marginal value while consuming tokens.
Suggestions
Move all Gothic Cathedral presets to a separate file (e.g., GOTHIC-PRESETS.md) and link to it from the main skill with a one-line reference.
Remove the 'Tips for Better Results' section — Claude already knows prompt engineering techniques for DALL-E.
Remove or move the cost reference to a separate file, as it contains time-sensitive pricing that will become stale.
Add a validation step after generation (e.g., check file exists and has non-zero size) and a retry workflow for failed generations.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is heavily bloated with project-specific preset prompts (Gothic Cathedral section) that are not generalizable and consume the majority of the document. The cost reference includes time-sensitive pricing. The tips section explains prompt engineering basics Claude already knows. | 1 / 3 |
Actionability | All commands are fully executable and copy-paste ready with concrete shell commands, specific file paths, and complete prompt examples. The parameter table is clear and the usage patterns are immediately actionable. | 3 / 3 |
Workflow Clarity | The basic usage flow is clear (run script with parameters), but there are no validation steps for checking if the API key is valid before running, no error handling workflow, and no feedback loop for when generation fails or produces unsatisfactory results. The batch generation section lacks any verification step. | 2 / 3 |
Progressive Disclosure | The entire document is a monolithic wall of text with all Gothic presets inline rather than in a separate file. The project-specific presets should be in a separate reference file, and the batch script details could be linked rather than embedded. No clear separation between general skill and project-specific content. | 1 / 3 |
Total | 7 / 12 Passed |
Validation
100%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- NeverSight/skills_feed
- Commit
f772de4
- 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.