Update to Simplified

{
  "name": "cross-platform-campaign",
  "description": "Turn a launch, promotion, event, announcement, or marketing brief into a coordinated campaign of channel-native social posts. Use when the user asks to launch or promote something across multiple platforms, create a campaign sequence, coordinate social messaging, generate campaign visuals, prepare drafts, or schedule a multi-channel rollout.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 613
    },
    {
      "relative_path": "assets/simplified-icon-256.png",
      "size_in_bytes": 8191
    },
    {
      "relative_path": "assets/simplified-logo.png",
      "size_in_bytes": 6726
    }
  ],
  "skill_md_contents": "---\nname: cross-platform-campaign\ndescription: Turn a launch, promotion, event, announcement, or marketing brief into a coordinated campaign of channel-native social posts. Use when the user asks to launch or promote something across multiple platforms, create a campaign sequence, coordinate social messaging, generate campaign visuals, prepare drafts, or schedule a multi-channel rollout.\n---\n\n# Cross-Platform Campaign\n\nBuild one coherent campaign while respecting how each social channel works. Compose the `generate-image` and `simplified-social` capabilities when campaign visuals are needed.\n\n## Guardrails\n\n- Do not publish or schedule without explicit approval of the final campaign matrix.\n- Create safe previews with `action: \"draft\"` when the user asks to prepare the campaign.\n- Image generation spends credits. Proceed when the image request is explicit; confirm first when visual generation is ambiguous.\n- Carry a generated image's permanent `asset_id` into social `media`; never rely on its expiring signed URL.\n- Stop on authorization failure or when no target accounts are connected.\n- Present all returned URLs as clickable links, never inline images.\n\n## Workflow\n\n1. Distill the brief into audience, objective, offer, proof, CTA, dates, channels, tone, constraints, and success metric. State sensible assumptions instead of requesting a long questionnaire.\n2. Call `social_getSocialMediaAccounts` once and map requested channels to returned account IDs.\n3. Define the campaign spine: one promise, supporting proof, CTA, and a sequence such as tease, launch, proof, reminder, and last call.\n4. Create channel-native variants. Change hook, length, CTA, format, and platform settings; do not paste the same caption everywhere.\n5. Plan media by post. If generation is requested, follow `$generate-image`, discover the current model schema, and use `storage: \"asset\"` for anything that will be attached to a post.\n   For a user-supplied local file, follow `$simplified-social` through signed\n   upload and `api_registerAsset`, wait for `api_getAsset`, and carry the UUID.\n6. Show a campaign matrix containing phase, date, account, copy, media, objective, and CTA.\n7. When drafts are authorized, call `social_createSocialMediaPost` with `action: \"draft\"` for each post. Pass generated asset UUIDs in `media` and use `../simplified-social/references/platform-settings.md` for `additional` fields.\n8. Offer a stakeholder review package via `$campaign-review` when several drafts need approval.\n9. Schedule or queue only after the user explicitly approves the final matrix. `add_to_queue` means publish as soon as possible.\n\n## Quality Bar\n\n- Keep the promise and visual identity consistent across the campaign.\n- Make each post useful on its own while advancing the sequence.\n- Match media to platform format requirements; never attach an image to a reel or short that requires video.\n- Do not invent product claims, prices, deadlines, testimonials, or availability.\n- Surface missing landing-page URLs, legal copy, offer terms, or media before publishing.\n\n## Output\n\nLead with the campaign idea and rollout. Then show the channel matrix, asset plan, drafts created, and any items blocking approval or scheduling.\n"
}