Update to Moodle: Mood Board plan+design

{
  "description": "Compare two or three creative directions in Mood Board when the user wants alternative visual routes, help choosing an aesthetic, or a structured comparison before committing to a board. Hold shared requirements constant and deliver comparable boards plus tradeoffs. Do not use for a single straightforward board request, a cohesion review, or widget layout changes.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 307
    }
  ],
  "name": "compare-mood-board-directions",
  "skill_md_contents": "---\nname: compare-mood-board-directions\ndescription: \"Compare two or three creative directions in Mood Board when the user wants alternative visual routes, help choosing an aesthetic, or a structured comparison before committing to a board. Hold shared requirements constant and deliver comparable boards plus tradeoffs. Do not use for a single straightforward board request, a cohesion review, or widget layout changes.\"\n---\n\n# Compare Mood Board Directions\n\n## Inputs\n\nUse the project brief, audience, intended impression, fixed ingredients, and any\nsupplied references. Use the latest model-visible board contents when the user\nis exploring alternatives to an existing board.\n\n## Workflow\n\n1. Establish the shared brief and the criteria for choosing a route. Retain\n   fixed colors, references, wording, and other stated constraints across all\n   alternatives. Ask a focused question if a missing constraint would materially\n   change the routes; otherwise state reasonable assumptions.\n2. Develop two routes by default, or three when requested. Give each a name and\n   a one-sentence idea. Make the alternatives differ in at least two meaningful\n   ingredients, such as palette, typography, imagery, or materials.\n3. Use the same ingredient categories and a similar item count for each route\n   so the comparison is fair. Target four to six items per route. Include a\n   `note` naming the route and its defining idea; add a palette, font previews,\n   and any relevant references that have reusable image sources.\n4. Render one complete board per route through `display-mood-board`, using the\n   registered schema, at most ten `moodBoard.items` per call, and an optional\n   `reason`. Omit output IDs and unsupported title, grouping, or position fields.\n   Use the note card to identify each route and the returned\n   `structuredContent.moodBoard` to describe what was rendered.\n5. Compare the routes in a short table against the shared criteria. Explain\n   their audience fit, strongest benefit, and practical tradeoff. Recommend the\n   route that best fits the user's priorities without inventing numerical scores.\n6. Ask the user to choose a route or a specific combination when the choice is\n   still open. If they already chose one, refine that route directly while\n   retaining the fixed anchors and using the latest visible contents.\n\n## Image and state handling\n\n- Use source URLs rather than signed delivery URLs. Describe references only\n  when visible or described by the user. If imagery is unavailable, represent\n  the intended imagery in a note and render concrete palette and font items.\n- For attachments without reusable image URLs, guide the user to upload the\n  selected images into the route's widget. Never fabricate a hosted source or\n  pass file IDs as URL arguments.\n- Use separate search or generation tools only when available and appropriate\n  to an additional user request. Do not present them as Mood Board capabilities.\n- Treat route boards as separate renderings with fresh item UUIDs. Do not\n  promise an in-place update, retained positions, transferred private upload\n  mappings, persistent versions, or a side-by-side comparison interface.\n- Leave the app-only `resolve-mood-board-images` helper to the widget. Do not\n  assume access to `privateContent` or inspect unseen imagery from URL names.\n\n## Deliverable\n\nProvide the named route boards, the compact comparison, and one recommendation\nwith its reason. Preserve a text-only comparison when the user requests text\nonly or no tools; do not render solely because this skill was selected.\n"
}