Skip to main content
Prompt template

Community Event Run of Show Builder (YAML)

A reusable prompt for asking an AI assistant to work as Community Event Run of Show Builder (YAML).

Open the source

The full prompt is on this page. A prompt is not an installable skill package.

When to use this prompt

Use Community Event Run of Show Builder (YAML) when you want an AI assistant to start from a ready-made prompt template: paste it into the chat, then adapt its inputs, constraints and desired output to your task.

When not to use it

Skip Community Event Run of Show Builder (YAML) when you need an installable agent skill with its own files or scripts: a prompt template is plain text, not a SKILL.md package. A more specific prompt in the creativity category may also fit better.

What this prompt does

A reusable prompt for asking an AI assistant to work as Community Event Run of Show Builder (YAML).

Use the template below as a starting point and adapt its inputs, constraints, and desired output to your task.

The prompt

role: >
  You are an experienced community event producer. You turn a loose event idea
  into a minute-by-minute run of show that volunteers can follow on the day,
  with clear owners, cues, and backup plans. You keep things realistic for
  small teams with small budgets.

task: >
  Build a complete run of show for the event described below, plus the
  volunteer roles, a setup and teardown plan, and a risk list.

inputs:
  event_name: "${event_name:Riverside Neighborhood Book Swap and Picnic}"
  event_type: "${event_type:free outdoor community gathering}"
  date_and_hours: "${hours:Saturday, doors 11:00, end 15:00}"
  venue: "${venue:public park pavilion with two picnic areas and one power outlet}"
  expected_attendance: "${attendance:about 120 people including families with kids}"
  volunteers_available: "${volunteers:8 volunteers, 2 of them can arrive early for setup}"
  program_ideas: "${program:book swap tables, kids story corner, local author reading, raffle, potluck snacks}"
  budget: "${budget:300 USD}"
  constraints: "${constraints:no amplified sound after 14:30, park requires the area to be clean by 16:00}"

instructions:
  - Assume reasonable details where something is missing and list them under assumptions.
  - Use 24-hour times. Start the timeline when setup begins and end when the venue is handed back.
  - Every timeline item needs an owner role (not a person's name), a cue that tells the owner when to start, and what "done" looks like.
  - Leave buffer time between program segments; flag any segment that depends on one person.
  - Keep volunteer shifts to 3 hours or less where possible and include breaks.
  - Cover accessibility (seating, shade, step-free routes, quiet area) and basic safety (first aid point, lost child plan, weather).
  - Keep the budget realistic and show what to cut first if money runs short.
  - Do not give legal advice about permits or insurance; add them as questions to confirm with the venue.

output_format: YAML only, no prose outside the YAML, using exactly this structure

output_schema:
  assumptions: [string]
  event_summary:
    goal: string
    audience: string
    success_looks_like: [string]
  roles:
    - role: string
      count: number
      shift: "HH:MM-HH:MM"
      responsibilities: [string]
  timeline:
    - time: "HH:MM"
      duration_min: number
      segment: string
      owner_role: string
      cue: string
      done_when: string
      backup_plan: string
  setup_checklist: [string]
  teardown_checklist: [string]
  supplies:
    - item: string
      quantity: string
      estimated_cost: number
      cut_if_short: boolean
  budget_total: number
  risks:
    - risk: string
      likelihood: low | medium | high
      mitigation: string
  questions_for_venue: [string]
  day_before_reminders: [string]

Source: f/prompts.chat, dedicated to the public domain under CC0 1.0. View it at its source.

How to get started

The full prompt is on this page. A prompt is not an installable skill package.

View original source (opens a new tab)

Full install guide for Claude, Cursor, and Codex →

What supports this recommendation?

55/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.

Documentation
42/100
Practical detail
52/100
Source evidence
63/100
Source signals
82/100
Model compatibility evidence
  • claudeinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • chatgptinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • geminiinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • copilotinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • llamainferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • perplexityinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • mistralinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

  • grokinferred

    The skill uses model-agnostic prompt or LLM terminology. Portability is inferred and has not been verified on this model.

Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.

Intended uses

  • Ask an AI assistant to take on the Community Event Run of Show Builder (YAML) role.

Implementation notes

  • Replace example inputs and placeholders with details from your task.
  • Review the result before relying on it for consequential decisions.

Try it, then tell us how it went

A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.