── After step 1 completes, launch steps 2–5 in parallel ──

1. 2. Check schedule + get stadium info via ESPN API 🔀 (see ESPN API Reference for curl commands and response format):

1. 3. Research pilgrimage spots with stories 🔀 — launch 3 web_search calls in one batch (merged queries for speed):

1. 4. Research On This Day events 🔀 — only 1 web_search call for the entire trip:

1. 5. Ticket search via flyai 🔀:

── After all parallel steps complete, generate the guide ──

1. 6. Generate the guide with emotional narrative structure (see Guide Structure reference)

1. 7. Ask about flights & hotels — after the guide is generated, ask the user:

getstadiuminfo

Get detailed stadium information for pilgrimage planning.

• - team (str, required): Team name

Returns: stadium name, capacity, address, tour availability, ticket prices, visiting hours, plus the stadium's origin story and legendary moments.

getpilgrimagespots

Get a curated list of pilgrimage spots for a team's city. Each spot includes a backstory.

• - team (str, required): Team name
• INLINECODE25 (str, optional): Filter by type — "museum", "pub", "landmark", "shop", "all"

Returns: list of spots with name, description, address, significance, story (historical background, legendary events, famous anecdotes tied to this spot).

getonthis_day

Get historic football events that match the user's trip dates.

• - team (str, required): Team name
• INLINECODE27 (str, required): Trip start date (YYYY-MM-DD)
• INLINECODE28 (int, optional): Trip duration in days (default: 3)

Workflow:

1. 1. Web search "{team_name} history on this day {month} memorable moments" (use the departure month) — only 1 search
2. From results, filter events whose calendar date (month + day) falls within the trip dates
3. Assign each matching event to the corresponding trip day
4. For days with no matching event, simply omit — do NOT invent an event

⚠️ Critical: Every event in the output MUST come from a Web Search result. If you cannot point to a specific search result that contains the event, do not include it.

gettripmatches

Check if the team has any matches during the user's trip dates.

• - team (str, required): Team name
• INLINECODE31 (str, required): Trip start date (YYYY-MM-DD)
• INLINECODE32 (int, optional): Trip duration in days (default: 3)

Workflow:

1. 1. Determine ESPN league slug and teamid (see Finding a Team)
2. Fetch past results and upcoming fixtures via schedule endpoints (see ESPN API Reference)
3. Merge both results, filter events where date falls within [departuredate, departure_date + duration - 1]
4. For each match found, extract: home/away, opponent, kickoff time, status
5. Return matches sorted by date, with home matches highlighted

Output guidance:

• - 🔥 Home match: "Lucky you! During your trip, {team} will face {opponent} at {stadium}!" + flyai ticket search results
• ⚽ Away match: "During your trip, {team} has an away match (vs {opponent}) — you can watch the live broadcast at a local fan pub!"
• 😢 No match: "Match schedule during your trip — please check the team's official website before departure"

gettravelplan

Generate travel plan (flights + hotels) for the pilgrimage.

• - team (str, required): Team name
• INLINECODE34 (str, required): Departure city
• INLINECODE35 (str, required): Travel date (YYYY-MM-DD)
• INLINECODE36 (int, optional): Number of nights (default: 3)

Team Crest (Logo)

The team's official crest is obtained from ESPN API responses:

1. 1. Primary source — ESPN teams list or team profile → team.logos[0].href returns a URL like INLINECODE38
2. Direct construction — If you know the team_id, the crest URL follows a predictable pattern: INLINECODE39
3. Fallback — If crest URL is missing, search "{team_name} official logo png" via Web Search

• - Usage: Display in the guide header and anywhere the team identity is shown
• Rendering: Use ![{team_name} crest]({crest_url}) in Markdown
• Fallback: If crest URL is missing, use a text-based team badge with team colors

Guide Structure (Emotional Arc)

See references/guide-structure.md for the full 5-phase narrative arc (Pre-departure → Arrival → Stadium Day → Deep Experience → Departure), spot storytelling format, match day itinerary, and optional travel & stay section.

Data Sources

Examples

See references/examples.md for 3 complete examples: basic pilgrimage, pilgrimage with travel + On This Day + match detection, and standalone On This Day query.

Error Handling

• - If no team specified: Ask the user which team they support. If they're unsure, recommend 3–5 iconic pilgrimage destinations and wait for their choice. Never guess or pick a team on their behalf
• If ESPN API returns no matching team or the team name is ambiguous (e.g., "Inter" could be Inter Milan or Inter Miami), try multiple league slugs or ask user to clarify
• If stadium tour info is unavailable, note it and suggest checking the official website
• If flyai returns no flights, suggest alternative dates or nearby airports
• If no On This Day events found for a specific day, try broadening the search (league-level, city-level). If still nothing, omit the On This Day section for that day entirely — no placeholder text, no filler. Never fabricate events to fill gaps
• If crest URL is missing, use a text-based badge with team colors as fallback
• If ESPN API returns an error or is unreachable, fall back to Web Search for team info and skip match detection with a note to the user
• Never surface raw errors to the user — provide clean, human-readable messages

Common Mistakes

• - Don't confuse team names — always confirm with search results
• Don't hallucinate stadium tour details — only use verified info from search
• Don't skip the emotional narrative — this is not a dry travel guide, it's a pilgrimage
• Don't list spots without stories — every spot must have its backstory. If you can't find a story, search harder
• Don't fabricate On This Day events — this is the #1 risk of this skill. Rules:

• - Don't only search one day for On This Day — search every day of the trip (departuredate through departuredate + duration - 1), so each Phase has its own historic event
• Don't forget the team crest — it should appear in the guide header
• Don't forget to check for matches — when departure_date and duration are provided, always query ESPN schedule API to check for matches during the trip. A home match is the ultimate pilgrimage moment
• Don't assume match day = tour day — stadium tours are usually closed on match days. If there's a match, schedule the tour for the day before