Update to LeadJourney

{
  "description": "Find a specific lead in LeadJourney and summarize their full journey from first touch to conversion, including which channel and campaign brought them in.",
  "included_files": [],
  "name": "lead-journey-summary",
  "skill_md_contents": "---\nname: lead-journey-summary\ndescription: Find a specific lead in LeadJourney and summarize their full journey from first touch to conversion, including which channel and campaign brought them in.\n---\n\nUse this skill when the user asks about a single lead: \"where did this lead come from\", \"show me the journey of\", \"summarize lead X\", or pastes a LeadJourney lead URL such as `?slug=lead-overview&lead_id=<uuid>`.\n\n## Inputs to establish\n\n1. **Workspace.** Call `get_current_workspace`; switch with `switch_workspace` if the user names another brand.\n2. **Which lead.** Accept an email, phone number, name, or lead id.\n   - If given an id or URL containing `lead_id`, go straight to `get_lead_journey`.\n   - Otherwise call `get_leads` with the search term. If more than one lead matches, list them (name, email, created date) and ask the user to pick before continuing. Do not guess.\n\n## Steps\n\n1. Call `get_lead_journey` for the chosen lead.\n2. Read the timeline in order. Identify:\n   - First touch: channel, source/medium, campaign, landing page, timestamp.\n   - Any later touches and what changed (returning via a different channel, a specific ad creative, a retargeting click).\n   - Conversion event: form, call, purchase, or CRM stage, and when.\n   - Revenue attributed, if present.\n\n## Output\n\nPresent in this order:\n\n1. One-line identity: name, email, company if available, date created.\n2. **Journey**: a numbered list, one line per touchpoint, oldest first — `date · channel · campaign/creative · page`.\n3. **Attribution**: which channel gets first-touch credit and which gets last-touch credit, in one sentence each.\n4. **Status**: converted or not, revenue if any.\n\nKeep the whole summary under 200 words unless the user asks for full detail.\n\n## Do not\n\n- Do not include raw internal ids, tokens, or debug fields from the tool response.\n- Do not infer intent, sentiment, or buying stage that the data does not show.\n- Do not modify the lead, add tags, or trigger agents unless the user explicitly asks.\n\nExplicit user instructions override these defaults.\n"
}