The Monday Report: your weekly numbers written up in your voice

Use the Autoploy MCP for every read and save in this task. If it is not connected, stop and tell me instead of improvising. What to build: The Monday Report: your weekly numbers written up in your voice. Every Monday morning, read the week from your numbers list and write the weekly report in your saved voice, emailed to you ready to forward. Runs on your Claude subscription, or on your own AI key. Autoploy never bills you for the AI. This is for founders and non-technical builders. How it behaves: 1. Runs every Monday at 08:00 UTC. 2. Read this week's rows from your Weekly numbers list. 3. If any numbers this week, then go to "Read your business context", otherwise go to "Send an honest nudge". 4. No numbers were logged this week, so email a short honest note asking you to log them, instead of inventing a report. 5. Read the saved business fields this automation is locked to: your voice, offer, audience, method, proof, guardrails, and links. 6. If enough context to sound like you, then go to "Write the report with Claude", otherwise go to "Note the gaps". 7. Note which saved fields are empty or thin, so the report opens with an honest line instead of pretending. 8. Write the weekly report from this week's numbers in your saved voice, never using the words your guardrails forbid. 9. Email the finished report to you, once, ready to forward. The tools: - Anthropic (for "What should read your numbers and write the report?"). I will need you to create the key ANTHROPIC_API_KEY (Anthropic API key). I add the values in Autoploy myself; you only need their names. - Resend (for "Which email service should send the report?"). I will need you to create the key RESEND_API_KEY (Resend API key), provide the setting NOTIFY_EMAIL_FROM (From address), provide the setting NOTIFY_EMAIL_TO (Your inbox). I add the values in Autoploy myself; you only need their names. Shared memory: This automation remembers its work in a list called "Weekly numbers" (The numbers you want in your Monday report. Add a row for each; the report reads them.) that I can open in the Context section of my dashboard and see every row. Its columns are: metric ("Metric"), value ("Value"), note ("Note"), week ("Week"). Before anything runs, make sure the list exists: check with list_collections over my Autoploy MCP, and create it with create_collection (exactly that name, that purpose, and those columns) only if it is missing. Never create a second list under a similar name; reuse this one. The platform never creates a list silently at run time, so a missing list stops the work with a plain refusal. In the automation's code, write rows through ctx.collections.insert with an idempotency key built from the id of the thing the row is about (for example the booking id), so a replayed trigger can never write the same row twice. Read prior rows with ctx.collections.query when the automation must know what it already did. The platform: Connect to my Autoploy MCP server, call get_authoring_guide to read the authoring guide, and build the automation with the Autoploy SDK contract. Model every yes/no fork as a condition step with truthful labeled branches, keep every external side effect idempotent and keyed, and deploy it with deploy_automation. Before you build: Repeat the plan back to me in plain English and ask follow-up questions about anything unclear or ambiguous. Do not guess. Ask me for each key by name when it is time, and never ask me to paste a key anywhere except my own secure setup.