report-backlisted

# Report Back Turn a day's outreach activity into a clear digest the user can drop into Slack, email a manager, or paste into their weekly review doc. ## When this skill triggers - User asks for an end-of-day summary - User asks to "wrap up the day" - User pastes activity data and asks for a report - User is prepping a Slack update, weekly review, or CRM notes - User asks about outbound performance today or this week ## Inputs the skill expects The user provides some subset of these numbers (missing ones get flagged, not fabricated): - Sends today (LinkedIn DMs, connection notes, emails) - Replies received - Reply breakdown (positive / objection / DNC / no-fit) - Meetings booked - Meetings held - Drafts pending review - Follow-ups sent - Any specific wins or losses worth noting ## Output format Return a clean structured digest. Two formats depending on what the user needs: ### Format A — Slack-ready digest (default) ``` 📊 OUTREACH DIGEST · [Day, Date] SENDS → LinkedIn: [X] → Email: [X] → Connection notes: [X] Total: [X] REPLIES ([X] total) → Positive: [X] → Objections: [X] → Not-a-fit / DNC: [X] MEETINGS → Booked today: [X] → Held today: [X] IN THE QUEUE → Drafts pending review: [X] → Follow-ups scheduled tomorrow: [X] WORTH FLAGGING [1-2 lines on the most important thing that happened — a big reply, an objection worth learning from, a signal that fired, etc. This is where operator taste comes in.] TOMORROW'S FIRST MOVE [The single most important thing to do