Create banners using AI image generation. Discuss format/style, generate variations, iterate with user feedback, crop to target ratio. Use when user wants to create a banner, header, hero image, cover image, GitHub banner, Twitter header, or readme banner.
93
92%
Does it follow best practices?
Impact
92%
1.80xAverage score across 3 eval scenarios
Passed
No known issues
Quality
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 skill description that follows best practices. It concisely describes specific capabilities in a clear workflow, includes an explicit 'Use when' clause with excellent trigger term coverage spanning multiple banner/header types, and uses third person voice throughout. The description is well-structured and would allow Claude to confidently select this skill when appropriate.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: discuss format/style, generate variations, iterate with user feedback, crop to target ratio. These describe a clear workflow with distinct steps. | 3 / 3 |
Completeness | Clearly answers both 'what' (create banners using AI image generation with discussion, variations, iteration, and cropping) and 'when' (explicit 'Use when' clause listing specific trigger scenarios). | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'banner', 'header', 'hero image', 'cover image', 'GitHub banner', 'Twitter header', 'readme banner'. These are all terms users would naturally use when requesting this type of work. | 3 / 3 |
Distinctiveness Conflict Risk | Highly distinctive niche focused specifically on banner/header image creation. The specific mention of banner types (GitHub banner, Twitter header, etc.) and the workflow (crop to target ratio) clearly distinguishes it from general image generation or design skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured skill with excellent actionability and workflow clarity. The 6-step process is clearly sequenced with user checkpoints and iteration loops. Minor verbosity in the discovery section and some explanatory content that Claude wouldn't need (like listing what GitHub README or Twitter header are) slightly reduce conciseness, but overall the skill is effective and well-organized.
Suggestions
Tighten the Discovery section by condensing the purpose/style/content lists into a compact table or brief bullet points rather than nested sub-lists with explanations
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is mostly efficient but includes some unnecessary verbosity, such as the detailed list of style preferences and content elements that Claude could infer. The prompt pattern templates and common targets are useful additions, but the discovery section could be tighter. | 2 / 3 |
Actionability | Provides fully executable commands for each step including generation, batch generation, image editing, cropping, and HTML preview. Commands include specific flags, paths, and naming conventions that are copy-paste ready. | 3 / 3 |
Workflow Clarity | Clear 6-step sequential workflow with explicit checkpoints: wait for user confirmation after discovery, iterate with user feedback loop (generate → preview → feedback → regenerate), and explicit validation through HTML preview before final cropping. The feedback loop for iteration is well-defined. | 3 / 3 |
Progressive Disclosure | Well-structured with a clear overview workflow in the main file, references to external files for formats (references/formats.md) and examples (examples/opc-banner-creation.md), and a quick reference section at the bottom. References are one level deep and clearly signaled. | 3 / 3 |
Total | 11 / 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.
b18c6e6
Table of Contents
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.