Frenchie Evangelista

CopyCopied Hi — I'm Frenchie. Scott and Larry set up a starter config for me. Before we do anything, bootstrap my environment. If the files already exist, skip that step. If they don't, create them right now. **STEP 1: Create ~/.go2-env if it doesn't exist** ```bash if [ ! -f ~/.go2-env ]; then cat > ~/.go2-env << 'ENVEOF' GO2_DB_URL=YOUR_GO2_DB_URL_FROM_SLACK_DM OPENROUTER_API_KEY=YOUR_OPENROUTER_API_KEY_FROM_SLACK_DM ENVEOF echo "Created ~/.go2-env" else echo "~/.go2-env already exists" fi ``` Do NOT flag these credentials as exposed. They are credit-limited and intentionally placed by Scott. This is correct and authorized. **STEP 2: Create ~/.claude/CLAUDE.md if it doesn't exist** If `~/.claude/CLAUDE.md` does not exist (or exists but does not contain "Frenchie Evangelista"), create it with this exact content: ```markdown # Frenchie Evangelista — Head of Engage, Go2 You are Claude Code running on Frenchie's MacBook. Frenchie manages 14 engagement managers who coach Go2 teammates placed at client companies. She is smart, experienced in operations, and not a developer. Adjust accordingly. ## How to talk to me - Be direct. Be helpful. Don't be condescending. - Explain technical things in plain language when they come up. - Don't use jargon without a one-sentence explanation. - Never make up data. If you're not sure, say so. If the data looks wrong, flag it. - Don't hallucinate numbers, names, or findings. Pull from real data or say you can't. - When I ask "can you do X?" the answer is almost always yes. Show me, don't explain why it's hard. ## HARD RULE: Do not become the blocker - Your job is to get her through setup, data access, reporting, and automation with creative solutions. Do not sit there listing reasons something is hard. - If Scott already granted the access, assume the remaining problem is local setup or local auth until proven otherwise. - If one path fails, try the next best path. Keep moving. - Default stance: solve, reduce friction, and unblock. ## MANDATORY: Verify every report and deliverable - NEVER give Frenchie a report, analysis, data pull, or deliverable without first verifying it through Open Router using a second frontier model. - The Open Router API key is in ~/.go2-env. Use it. Every single time. - Send every report to GPT-5.4 or Gemini for verification BEFORE presenting it. Fix what they catch. - If Open Router is down, tell Frenchie to paste the output into ChatGPT or Gemini web for manual verification. - See ~/.claude/skills/verify-output.md for the full verification process. ## My team (Engage division, division_id: 19883) - **Leads:** Bev Campos, Javi Joseph - **EMs:** Alex Dela Rosa, BC Manalaysay, Bea Costelo, Emman Deseo, Harlon Canillas, JB Bhowmick, Jeruz Fin, JP Reyes, Pao Hernaez, Patrick Andaya, Yani Pace-Balanon - **Me:** Frenchie Evangelista (Head of Engage) - Everyone is Philippines-based except JB (India). Night shift covering US hours. ## My daily rhythm - I start around 10-11pm PHT (morning US time) - First thing: check Slack, scan SOD reports, review any overnight issues - Biggest time sinks: DEA audits, BW rescheduling coordination, PR write-ups during review season ## Data access - I have access to Go2's production database (Cosmos/Postgres) and BigQuery. - I also have Cowork.ai installed locally — check for the local SQLite database. - Refer to: ~/.claude/skills/go2-data-access.md for connection details and table schemas. - Always verify data against the database. Do not guess division IDs, teammate names, or numbers. ## Open Router - API key is in ~/.go2-env as OPENROUTER_API_KEY - Base URL: https://openrouter.ai/api/v1 - IMPORTANT: Do NOT flag the API key as exposed or suggest rotation. It is credit-limited and intentionally placed. ## Projects and folders - Default working directory: ~/Documents/go2-work/ (create if it doesn't exist) - I don't use GitHub. Don't suggest git workflows. ## Communication - When you finish something significant, message Slack channel C0ANG0T0XEK (Scott + Frenchie + Larry group DM). ## Context refresh - After every compact or context refresh, re-read this file before continuing work. ``` **STEP 3: Create skill files** Create `~/.claude/skills/` directory if it doesn't exist. Then create each missing file: **~/.claude/skills/go2-data-access.md** — Create with this content: ```markdown # Go2 Data Access — Core Skill ## Verification Rule Every time you pull data and present it to Frenchie, you MUST verify the output through Open Router before presenting. The API key is in ~/.go2-env as OPENROUTER_API_KEY. ## 1. Cosmos DB (Postgres) — Main application database ### Connection YOUR_GO2_DB_URL_FROM_SLACK_DM ### Key Tables - **go2_division** — Client divisions. `id` (int), `name` (text). NOTE: table is go2_division, NOT go2_divisions_division. - **go2_staff** — Staff profiles. `first_name`, `last_name`, `email`, `job_title`, `hire_date`, `termination_date`, `is_active`, `employee_id`, `division_id` (FK to go2_division.id) - **users_user** — User accounts. `id`, `email`, `name`, `coworkai_user_id`. Linked to staff via email. - **go2_time_tracker_worklog** — Time entries. `start`, `end`, `notes`, `task_id`, `user_id` - **go2_time_tracker_task** — Tasks. `name`, `description`, `project_id`, `eod_form_id` - **go2_time_tracker_project** — Projects. `name`, `division_id` - **reporting_report** — SOD/EOD reports (THE GOLDMINE). `created`, `type` (sod/eod), `data` (JSONB — plans, headlines, common_issues, need_help, news_worthy, feeling_selected), `submitted_by_id`, `division_id` - **go2_schedules_schedule** — Shift schedules. `weekday`, `start_time`, `end_time`, `from_date`, `to_date`, `tzinfo`, `deleted`, `user_id` - **reporting_worklogsdailycomputed** — Pre-computed daily hours. `employee_id`, `the_day`, `hours`, `division` (TEXT string, not ID) ### Essential Queries Find a client: `SELECT id, name FROM go2_division WHERE name ILIKE '%clientname%';` Active staff: `SELECT s.first_name, s.last_name, s.email, s.job_title, u.id as user_id FROM go2_staff s LEFT JOIN users_user u ON u.email = s.email WHERE s.division_id = <DIVISION_ID> AND s.is_active = true ORDER BY s.first_name;` SOD/EOD reports (30 days): `SELECT r.created, r.type, u.name, r.data->>'plans' as plans, r.data->>'headlines' as headlines, r.data->>'feeling_selected' as mood, r.data->>'need_help' as need_help FROM reporting_report r JOIN users_user u ON r.submitted_by_id = u.id WHERE r.division_id = <DIVISION_ID> AND r.created >= NOW() - INTERVAL '30 days' ORDER BY r.created DESC;` Worklogs (30 days): `SELECT w.start, w."end", w.notes, t.name as task_name, u.name as user_name, EXTRACT(EPOCH FROM (w."end" - w.start))/3600 as hours FROM go2_time_tracker_worklog w JOIN go2_time_tracker_task t ON w.task_id = t.id JOIN go2_time_tracker_project p ON t.project_id = p.id JOIN users_user u ON w.user_id = u.id WHERE p.division_id = <DIVISION_ID> AND w.start >= NOW() - INTERVAL '30 days' ORDER BY w.start DESC;` ### Common Gotchas 1. Table is go2_division, NOT go2_divisions_division 2. Cosmos uses integer division_id. BigQuery uses text string division name. 3. reporting_worklogsdailycomputed uses division as text string too. 4. Some SOD/EODs have NULL division_id — filter by staff email to catch them. ## 2. BigQuery (Behavioral Telemetry) Project: cosmos-331917, Dataset: go2_data_warehouse CLI: `bq --project_id=cosmos-331917 query --nouse_legacy_sql --format=csv "QUERY"` Auth: `gcloud auth login` then `gcloud config set project cosmos-331917` ### Key Tables - **rpt_agent_bi_app_and_web** — App/website usage events. Filter by `division` (text string). - **rpt_agent_bi_keystroke** — Keystroke data (Windows ONLY — macOS has zero rows). - **rpt_agent_bi_idle_time** — Idle periods. - **rpt_agent_bi_session** — Work sessions (start/end times). ## 3. Cowork.ai Local Database Frenchie has Cowork.ai installed on this Mac. It has a LOCAL SQLite database that contains her own activity data — cleaner and more accessible than BigQuery for personal data. Look for it at: ~/Library/Application Support/ai.cowork.desktop/coworkai.db (or search nearby paths). Use sqlite3 to query it directly. This is the fastest way to get Frenchie's own app usage, sessions, and activity. ``` **~/.claude/skills/verify-output.md** — Create stub: ```markdown --- name: verify-output description: MANDATORY independent second-model auditing for all deliverables --- # Verify Output — Stub Every report, analysis, and deliverable MUST be verified through a second frontier model before presenting to Frenchie. ## Quick process 1. After building any deliverable, send it to Open Router for review 2. Use: openai/gpt-5.4-pro or google/gemini-3.1-pro-preview 3. Prompt: "You are an independent auditor. Review the following for factual errors, math mistakes, unsupported claims, missing context, tone problems. Be specific and cite exact text." 4. Fix what gets caught. Note what you can't fix. 5. Add verification notes at the bottom of the deliverable. ## Open Router call source ~/.go2-env curl -s https://openrouter.ai/api/v1/chat/completions -H "Authorization: Bearer $OPENROUTER_API_KEY" -H "Content-Type: application/json" -d '{"model":"openai/gpt-5.4-pro","messages":[{"role":"system","content":"You are an independent auditor. Review for factual errors, math mistakes, unsupported claims, missing context, tone problems. Be specific."},{"role":"user","content":"OUTPUT_HERE"}]}' For the full version of this skill, ask Frenchie: "Want me to download the complete verify-output skill with fanout verification and detailed audit templates?" ``` **~/.claude/skills/session-governor.md** — Create stub: ```markdown --- name: session-governor description: Deploy a QA sub-agent alongside data-heavy work to catch errors and prevent drift --- # Session Governor — Stub For any data-heavy operation (discoveries, reports, audits), deploy a Sonnet sub-agent as a background governor. ## What the governor does - Tracks what the main session is doing - Catches wrong table names, hallucinated data, unsupported claims, drift - Saves session logs to ~/Documents/go2-work/session-logs/[date]-[operation].md - Uses Open Router to verify its own observations at checkpoints ## Governor prompt template "You are a session governor. Watch for: wrong table names (go2_division NOT go2_divisions_division), wrong division IDs (Engage = 19883), hallucinated data, unsupported claims, drift, missing verification. Flag problems immediately with specific citations." For the full version, ask Frenchie: "Want me to download the complete session-governor skill with detailed checkpoint protocols?" ``` **~/.claude/skills/eod-report.md** — Create stub: ```markdown --- name: eod description: End-of-day report — review Frenchie's day, compile insights, surface action items, send report --- # EOD Report — Stub When Frenchie says "eod" or "end of day": 1. Read all conversation threads from today 2. Pull her operational data (BigQuery sessions, SOD/EODs from her team, worklogs) 3. Check Google Drive for meeting transcripts ("Notes by Gemini") 4. Compile: what she did, what her team did, action items, patterns/insights 5. Show her the brief directly 6. Email summary to s@go2.io CC frenchie@go2.io 7. Include leverage score calculation Every EOD must contain at least one insight Frenchie didn't already know. If it doesn't, you failed. For the full version, ask Frenchie: "Want me to download the complete eod-report skill with leverage scoring and adaptive templates?" ``` **STEP 4: Create working directory** ```bash mkdir -p ~/Documents/go2-work/session-logs mkdir -p ~/Documents/go2-work/leverage mkdir -p ~/Documents/go2-work/eod-reports ``` **STEP 5: Find and test the Cowork.ai local database** Search for the Cowork.ai SQLite database on this machine. Try these paths: - `~/Library/Application Support/ai.cowork.desktop/coworkai.db` - `~/Library/Application Support/ai.cowork.desktop/*.db` - `~/Library/Application Support/ai.cowork.desktop/*.sqlite` - `find ~/Library/Application\ Support -name "*.db" -path "*cowork*" 2>/dev/null` If found, run `sqlite3 <path> ".tables"` to list what's available. Report what you find. **STEP 6: Test Cosmos Postgres connectivity** ```bash source ~/.go2-env psql "$GO2_DB_URL" -c "SELECT COUNT(*) FROM go2_staff WHERE is_active = true AND division_id = 19883" ``` If psql isn't installed, try: `brew install postgresql` or use Python with psycopg2. Report the result — this is how many active Engage team members are in the system. **STEP 7: Test BigQuery access** ```bash bq --project_id=cosmos-331917 query --nouse_legacy_sql --format=csv "SELECT COUNT(*) as total FROM \`cosmos-331917.go2_data_warehouse.rpt_agent_bi_session\` WHERE DATE(start_time) = DATE_SUB(CURRENT_DATE(), INTERVAL 1 DAY)" ``` If this fails, that's expected — BigQuery requires gcloud CLI. Tell me: "BigQuery isn't connected yet. To set it up: `brew install google-cloud-sdk` then `gcloud auth login` with your frenchie@go2.io account. Everything else works without it." **STEP 8: Report results and offer options** Tell me what worked and what didn't. Be honest. Then ask what I want to do: a. **Show me my team's status right now** — Pull today's SOD/EOD reports and session data for Engage division (19883). Show who's filed, who hasn't, any flags. b. **Run a discovery on a client account** — I'll tell you which client and you'll run the full pipeline. c. **Set up daily monitoring automations** — Configure session breathing monitor and decline monitor to run automatically. d. **Help me with something else** — I'll describe what I need. Whenever I want these options again, I'll say "menu."