AF brand-mood-board-maker
Turn a brand brief into a mood board spec — palette with hex, display + body type pairing, 6-12 image tile prompts, and a one-sentence brand essence. Maps the brand to a Jungian archetype and picks a board layout before generating tiles. Trigger when the user says "make a mood board", "build a brand mood board", "pull together visual direction", "brand vibes for", or "aesthetic board for".
As a process F 68/100 · Will not run — References files that are not bundled: assets/archetype_visual_cues.md, assets/layout_templates.md, assets/tile_prompt_library.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- 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: 1. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: assets/archetype_visual_cues.md - warning
missing-refreference to a missing file: assets/layout_templates.md - warning
missing-refreference to a missing file: assets/tile_prompt_library.md
Process rating: all ten parameters 68/100
- 0Tools and files. 3 referenced file(s) missing: assets/archetype_visual_cues.md, assets/layout_templates.md, assets/tile_prompt_library.md
- 0Progress reporting. Says nothing while it works
- 30Running it twice. 3 mutating operations with no state check
- 60Result and completion. Output format stated, no completion criterion
- 70Inputs and preconditions. Inputs and preconditions are listed
- 100Steps. 52 steps
- 100When it triggers. States when to use and when not to
- 100Failures and branches. 1 branches, has a failure section
- 100Consistency. Name and required fields are in place
- 100Execution cost. Instruction body is 2110 tokens
- medium Safety rules and hard prohibitions inside a skill: they belong in the system prompt, here they protect nothing
- low The response is described with custom markup (3 tags): a typed call is more reliable
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)
- +1No license
- +2Single-language instructions
- +5Description quotes 5 example trigger phrases
- +3Description length 392: enough signal without eating the budget
- +4Structure: 8 headings
- +3Step-by-step instructions: 52 items
- +3Output format is stated explicitly
- +4Has examples (2 code blocks)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 80.