JETAASC Event Publisher

Publish JETAASC events to multiple platforms: Wix Blog, Google Calendar, Discord, and Facebook.

Workflow

1. Collect Event Information

Gather from user:

• Title: Event name
• Date/Time: Start (and end if applicable)
• Location: Venue name and address
• Description: What the event is about
• Cost: Price (optional, include member/non-member pricing if applicable)
• RSVP Link: Partiful or Google Form link (optional — see below)
• Flyer/Image: Event artwork URL or local file path

Handling Flyer Images:

The flyer must be a publicly accessible URL for Wix import. Resolve the image based on what the user provides:

Storage, naming, permissions, URL forms, and the Drive gotchas are in [../../references/public-flyers.md](../../references/public-flyers.md). Read it before uploading — the upload and permission steps have non-obvious failure modes that fail silently.

1. Local file path (e.g., ~/Downloads/flyer.png):

- Upload to the Public Flyers folder per the reference above, and confirm anyone:reader afterward - Use https://lh3.googleusercontent.com/d/FILE_ID for Wix - For Discord and Facebook, use the original local file path directly (both take local paths)

1. Google Drive share link (e.g., https://drive.google.com/file/d/FILE_ID/view):

- Convert to direct image URL: https://lh3.googleusercontent.com/d/FILE_ID

1. Direct image URL (e.g., https://example.com/flyer.png):

- Use as-is

2. RSVP Link

If the user did not provide an RSVP link and one cannot be extracted from the event description or flyer:

Ask the user: "No RSVP link provided. Would you like me to create an RSVP page?"

• Partiful (recommended) — creates an RSVP page with event details. Read the partiful skill (.claude/skills/partiful/SKILL.md) for conventions and gotchas, and partiful create --help for the command reference. Pass the event details you already collected — do not re-ask the user. Partiful can also ask guests questions at RSVP time (dietary restrictions, sizes, email, social handles), so it covers most cases that used to need a form.
• Google Form — use when the questions outgrow what Partiful collects: long-form answers, per-question branching, or a response sheet someone needs to work in directly. Read [references/google-form-rsvp.md](references/google-form-rsvp.md) for the full creation workflow.
• Skip — no RSVP needed

3. Confirm Details and Select Platforms

Display a summary of the event details for user confirmation.

Then ask two questions using AskUserQuestion:

Question 1 (multiSelect: true): "Which platforms do you want to publish to?"

• Wix Blog
• Discord
• Google Calendar
• Facebook

Question 2: "How should I publish to the selected platforms?"

• In parallel (Recommended) - Publish to all platforms simultaneously
• Sequential - Publish one at a time, confirming each before proceeding

4. Publish to Selected Platforms

Execute publishing based on user selections. If parallel, launch all platform tasks simultaneously. If sequential, complete each platform before moving to the next.

Read the reference doc for each selected platform before publishing:

Facebook is the one platform that does not publish on its own. The agent fills the entire event form and stops; Adrian reviews it in the browser and clicks "Create event" himself.