AC image-prompt
Use as the foundation and router for any image a post needs — turn a social need into a clear image brief, describe it with model-agnostic prompt craft, and route to the right tool. Run when the user says "I need a visual/image for this post," "what image should I use," "make a graphic," "help me prompt an image," or is unsure which image tool/model to use. Reads brand-profile for the visual brand. Teaches the image brief, the universal anatomy of a strong prompt in natural language, and a tool router (typographic -> ideogram/nano-banana; photoreal -> nano-banana/flux; surreal -> Midjourney; editing -> nano-banana/flux; vector -> Recraft; video -> veo-3). Includes a "should this even be AI-generated?" gate (a real photo, screenshot, or chart often beats generic AI), accessibility, and honest scope (disclose AI, never real identifiable people or copyrighted IP, verify text/data). Hands off to the tool-specific mini-skills; WoopSocial publishes via Media and doesn't generate images.
Use as the foundation and router for any image a post needs — turn a social need into a clear image brief, describe it with model-agnostic prompt craft, and…
As a process C 62/100 · Has gaps — weak spots: result and completion, inputs and preconditions, running it twice
How to improve
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 6. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
✓ No remarks against the Agent Skills spec
Process rating: all ten parameters 62/100
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 6 mutating operations with no state check
- 50Failures and branches. 0 branches, has a failure section
- 70When it triggers. States when to use, but not when not to
- 100Tools and files. No external tools needed
- 100Steps. 29 steps
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 1327 tokens
- low 10 top-level sections: this looks like several domains in one skill
- medium 8 test cases, all positive: not one "should refuse" or "should ask first"
- low No test case covers injection arriving through data
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +4Description does not say when NOT to use the skill (false activations)
- +3Description length 995: 120–800 characters recommended
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +4Structure: 11 headings
- +3Step-by-step instructions: 29 items
- +4Reference files are cited in the instructions (4 of 4)
- +1License stated
Quality base 70; lint remarks subtract, signals add up to 100. Result: 87.