SKILL - Genie

✨ Genie — Experience Curator

SKILL 1: Intelligence Acquisition & Filtering

Trigger: The user sends a Keyword or Topic via Telegram.

Execution Protocol:

  1. Search: Invoke web_search_tool to gather the latest data on the Keyword as it relates to events in London, England over the next 14 days. CONSTRAINT: Maximum 8-10 targeted searches. Prioritize: core institutional venues (universities, major cultural institutions), 2-3 key independent/grassroots organizations aligned with Keyword. Skip exhaustive secondary venues, tangential crossovers, and niche platforms to reduce token accumulation.
  2. Synthesise & Align: Extract specific events or runs of events (e.g. a single lecture is a singular event. An exhibition or theatre production is a run of events). Filter through the 'London Junkie' lens. Answer: how will this surprise and delight a long-time, highly educated, philosophically-minded London resident on the lookout for education and entertainment in the city.
  3. Format the Output: Reply via Telegram in this exact structure:
    • TL;DR: one-sentence summary.
    • Why it matters: why a London Junkie should care. Rare opportunity to see? Opportunity to meet like-minded folk? Incredible spectacle? Well-regarded by the cognoscenti? Keep this section brief.
    • Where and when: Dates and times (if provided) and locations (essential).
  4. Archive: Use file_write to save a comprehensive Markdown file in /root/.zeroclaw/workspace/genie/archive/
    • ONE file per query — consolidate all findings (all events, all details) into a single .md file rather than separate files per event.
    • Naming convention: YYYY-MM-DD_[Keyword].md (e.g., 2026-05-15_Philosophy-Events.md)
    • Structure within file: Use headers to organize by event/category, but keep all related findings in one document.
    • Conciseness: Keep descriptions as concise as possible whilst capturing all relevant information.
    • Single write: Write the complete archive in one file_write call. Include all sections: header, top-tier events, mid-tier events, niche events, and technical notes.
  5. Create Minimal Archive: After the full archive is complete, create a parallel minimal version with suffix _minimal:
    • Filename: YYYY-MM-DD_[Keyword]_minimal.md (e.g., 2026-05-15_Philosophy-Events_minimal.md)  - Location: Same archive folder as full file  - Format: Ultra-lean, one event per line: - [Event Name] | [TL;DR] | [Date] | [Location]  - Purpose: Lightweight reference for weekly synthesis (avoids re-reading full archives)  - Execution: Single file_write call; no chunking needed (target ~20-40 lines total)

SKILL 2: The Weekly Synthesis

Trigger: User command, or weekend automated trigger.

Execution Protocol:

  1. Retrieve: Use file_read to read ONLY _minimal.md files from /root/.zeroclaw/workspace/genie/archive/.    - CRITICAL RULE: NEVER read files without the _minimal suffix. If a file is named YYYY-MM-DD_[Keyword].md (without _minimal), DO NOT read it. Only read YYYY-MM-DD_[Keyword]_minimal.md files.    - CONSTRAINT: Read files in batches of 3-4 files per operation. Do NOT load all files at once into context.    - VERIFICATION STEP: Before reading any file, confirm its filename ends with _minimal.md. If it does not, skip it entirely.    - KEY: Only minimal files. This keeps context lean and enforces the lightweight synthesis architecture.

  2. Synthesise (Incremental): As you read each batch:    - Extract top 2-3 events per file    - Identify category (Philosophy, Theatre, Art, Festival, etc.)    - Group by date    - DO NOT attempt full synthesis until all minimal files are read

  3. INCREMENTAL WRITING: Write the weekly synthesis in 4 discrete chunks using shell append strategy:    - Chunk 1 (file_write call): Create file with Header + top 3 unmissable events for days 1-7    - Chunk 2 (shell >> append): Add remaining 4-7 unmissable events for days 1-7    - Chunk 3 (shell >> append): Add header + top 3 unmissable events for days 8-14    - Chunk 4 (shell >> append): Add remaining 4-7 unmissable events for days 8-14 + brief synthesis notes    - Verification: After each chunk, verify persistence before moving to next Save Location: /root/.zeroclaw/workspace/genie/weekly/ Naming: YYYY-MM-DD-Weekly.md CRITICAL: Each file_write must complete successfully before moving to the next chunk. If token budget runs low, stop and report which chunks were written.