---
name: al-574-stop-writing-client-status-reports-from-scratch-have-an-a
description: "Writing a daily or weekly 'here's what we did' update for each client is valued but tedious. On Oct 30, 2026, founder Filippo Biasiolo (@fil_ships) said he used to spend about half an hour a day on client work reports, so he set up a Grok Bot assistant that checks his team's code commits and sends him a summary at 8 every morning, written in the language and tone suited to the client who reads it. He now spends about 5 minutes checking and copying it, which he says saves 20+ minutes a day, over 7 hours a month (as reported by Artificially Nerdy). The same works for any team that logs work somewhere: a CRM, a transaction management system, a project board or a shared sheet, for example a weekly update to each seller on showings and marketing done. The assistant needs read access to that log, and you still review each update before sending. Use when the user wants help with daily client update drafted from your team's work log (operations) for a small business."
---

# Stop writing client status reports from scratch: have an AI assistant read where your team logs its work each morning and send you a ready-to-copy summary in the client's language

Writing a daily or weekly 'here's what we did' update for each client is valued but tedious. On Oct 30, 2026, founder Filippo Biasiolo (@fil_ships) said he used to spend about half an hour a day on client work reports, so he set up a Grok Bot assistant that checks his team's code commits and sends him a summary at 8 every morning, written in the language and tone suited to the client who reads it. He now spends about 5 minutes checking and copying it, which he says saves 20+ minutes a day, over 7 hours a month (as reported by Artificially Nerdy). The same works for any team that logs work somewhere: a CRM, a transaction management system, a project board or a shared sheet, for example a weekly update to each seller on showings and marketing done. The assistant needs read access to that log, and you still review each update before sending.

## Inputs to collect first
Ask the user for anything below that they haven't already given you. Don't guess missing facts.

- Client
- Reader

## Instructions

Do the task below with the user's inputs in place of each [bracket].

1. Pick where your work is logged: commits, a project board, your CRM activity, a transaction checklist, or a shared sheet. Give your AI assistant read-only access, or export it daily.
2. Write a short note for each client: who reads the update, what they care about, how formal it should be, and what to leave out (internal notes, other clients, anything confidential).
3. Ask: "Every weekday at 8am, read yesterday's entries for [client] and draft an update for [reader]: what was done, what's next, and anything we need from them. Plain language, no jargon, under 150 words. Use only what's in the log."
4. Have it send the draft to you, not the client.
5. Check it, fix anything wrong, then copy and send it yourself. Adjust the client note whenever the tone is off.

## Safety checks (share these with the user)

- Remove names, contact details, account numbers and other personal data the task doesn't need before you paste, and check your AI tool's data and training settings.
- Read and edit the draft before it reaches a customer or goes public. If you later automate this prompt, start with "draft and notify me", not "send automatically".
- Check names, dates, numbers and any claim against your own source material before you use the answer. AI can misread or invent details.
- Say clearly which parts need a person to review or approve before anything is sent, paid, posted or filed.

## About this skill

- Works with: Grok Bot, ChatGPT, Claude
- Based on this real-world example: https://artificiallynerdy.com/use-cases/agency-owner-has-grok-bot-draft-daily-client-reports-from-team-commits/
- Free prompt from AgentPlaybook Real Estate: https://agentic-library.netlify.app/prompt/al-574-stop-writing-client-status-reports-from-scratch-have-an-ai-a/
- To install in an agent that supports Agent Skills, save this file as SKILL.md in a folder with the same name as `name` above (for example in your skills directory). Install steps for Claude.ai, Claude Code, Cursor and Codex: https://agentic-library.netlify.app/skills/