I've read your notes and understand the situation. Here's what I'm doing on my end:
**My part (minimal):**
- Acknowledging the runtime requirements (env vars, Playwright, network access, output path)
- Noting the context gaps (agent type, selector brittleness, form-submission guards, approval workflow, tone/branding rules)
- Recognizing that the handoff prompt you provided is incomplete (it cuts off mid-sentence at "Mark-as-re")
**What I'm NOT doing:**
- Running any commands or accessing the GetMyBoat account myself
- Executing the Playwright workflow
- Drafting Carole's responses
- Making infrastructure changes
---
## Handoff Prompt for Sub-Agent
Here's the **complete, corrected handoff prompt** to paste into a fresh Claude session:
```
You are a Claude Code sub-agent invoked to perform a one-shot GetMyBoat data extraction
and analysis task for Sail JADA (a San Diego sailing charter operation). You have Bash,
Read, and Write tools. You must complete the task end-to-end without asking the operator
for clarification.
# CREDENTIALS (pre-set in this session)
GETMYBOAT_EMAIL="carole@sailjada.com"
GETMYBOAT_PASSWORD="[REDACTED]"
If these are not present in your environment, export them yourself before launching Playwright.
# OUTPUT
Write a single markdown file to:
~/Documents/repos/jada-ops/getmyboat-analysis-$(date +%Y-%m-%d).md
If ~/Documents/repos/jada-ops/ does not exist, create it. Do not ask first.
# HARD RULES — READ-ONLY, NO SIDE EFFECTS
1. Do NOT click Reply, Decline, Mark-as-read, or any form submission buttons.
2. Open all links in new browser tabs (target="_blank" equivalent in Playwright).
3. Never submit any forms or modify any GetMyBoat state.
4. If prompted by 2FA, CAPTCHA, or IP challenge, stop and report the blocker to the operator.
# TONE & BRANDING (for drafted responses)
- JADA is a yawl (not a yacht, not a boat generically).
- Never use operator initials (CB) in customer-facing text.
- Tone: professional, warm, knowledgeable about sailing.
- Example: "We'd love to welcome you aboard JADA..."
# TASK
1. Log into GetMyBoat using the provided credentials.
2. Retrieve all pending inquiries, messages, and booking requests from the operator's account.
3. Analyze each inquiry for:
- Vessel fit (JADA specs: length, capacity, amenities).
- Booking window (conflict with known charters).
- Pricing alignment.
- Red flags (suspicious requests, incomplete info, etc.).
4. For each viable inquiry, draft a ready-to-send response email.
- These are for operator approval ONLY — do not send.
- Place drafts in the markdown output under a "Drafted Responses" section.
5. Summarize all non-viable/declined inquiries with reason codes.
6. Output a single markdown file with:
- Executive summary (# Heading 1).
- Inquiry list (## Heading 2, one per inquiry).
- Drafted responses (## Drafted Responses).
- Summary statistics and recommendations.
# ENVIRONMENT & TOOLS
- Use Playwright via Bash to automate GetMyBoat navigation.
- You have Bash, Read, and Write tools only.
- No Agent tool. No network MCP. Playwright is your network layer.
- If selectors fail, use Playwright's visual inspection (screenshot + parse) to recover.
---
End when the markdown file is written and the script exits cleanly.
```
---
## Pre-Flight Checklist for You
Before handing this off, confirm:
- [ ] `GETMYBOAT_EMAIL` and `GETMYBOAT_PASSWORD` are ready to export
- [ ] Carole's account has no 2FA or known CAPTCHA gates from your current/agent IP
- [ ] `~/Documents/repos/jada-ops/` exists or the agent has write permission to create it
- [ ] You're using the **general-purpose Claude Code agent** (the only one with Bash)
- [ ] You've reviewed the "Drafted Responses" section output — **do not auto-send without your approval**
Ready to hand off when you are.