Sales
Kondo owed-reply sweep
Use this skill at the start or end of a day of LinkedIn prospecting, when you need to know which DMs are waiting on you. Produces a short list of people whose message is last, for you to decide which to answer. Uses Kondo's MCP server. "Who replied?", "check my DMs", "what LinkedIn replies do I owe".
R. Hunter HarrisFounder, Hunter Software ConsultingSay something like
“Who replied?”“check my DMs”“what LinkedIn replies do I owe”
SKILL.mdView on GitHub
Applies when you prospect on LinkedIn and replies get lost in the inbox. Produces a list of the one-to-one threads where the other person spoke last, by name, for you to decide.
Needs Kondo connected to your agent through its MCP server. The sweep only reads, covers the last 14 days, and sees only LinkedIn.
The play
- Call
list_inboxwith the "needs my reply" view and anaftercutoff 14 days back, computed in UTC epoch milliseconds. Use a fixed helper or a one-line script for the cutoff, never the agent's head. Save the raw response to a file. - An error or missing response means the sweep failed: say so and stop, never log it as done. A valid empty inbox means nothing is owed.
- Drop group chats; they are never a reply owed. Drop threads you already marked "no reply needed", unless the person has written since.
- For each remaining chat, call
read_chat. If it comes back empty, callload_chat(also a read), spacing calls 3 seconds apart. If rate limited, wait as told and retry once. - If a chat comes back in pages, merge the pages into one thread before judging it.
- Sort by time and look at the last real message. It is owed when the last message is theirs. An attachment with no text still counts as a message.
- If you can check your email, texts or call log, suppress threads you already answered there after their last message. If you can't, keep them on the list.
- List the owed people by name and ask once which to answer. For each one you say needs no reply, store the thread and the time of their last message, so it comes back only when they write again.
- Close with one line: owed, answered, not owed.
The failure log behind steps 1 to 7 is in references/sweep-gotchas.md. Open it when a count looks wrong.
What good looks like
- First check: the sweep really ran. An error string logged as "done" means a day of replies nobody saw.
- The mediocre version trusts Kondo's "needs reply" view as-is. It flags group chats, splits one paged chat into several, and asks every morning about people you answered by text.
- The output is right when every name on the list has their message last, nobody you answered elsewhere is on it, and the list is short enough to act on before the day's messaging starts.
Rules
- MUST stay read-only: never send, draft into Kondo, label or archive a chat from this sweep.
- MUST name people, never show Kondo's internal identifiers.
- MUST let the human decide who needs a reply; record their words when they say "no reply needed".
- NEVER record anything when Kondo is down or returns an error.
- NEVER fire
load_chatcalls in parallel.
1 reference file
references/sweep-gotchas.md
Sweep gotchas
Each of these broke a real sweep before it was fixed.
| Symptom | Cause | Fix |
|---|---|---|
| The inbox call asked for 13 months of history | the agent worked out after by hand | compute the cutoff with code: now minus 14 days, epoch milliseconds |
| The cutoff was an hour off around a clock change | local time without a timezone | compute it in aware UTC |
| A day's sweep was logged as done but nothing was read | "No browser tab connected" was taken as a result | count the sweep only when Kondo returns real inbox data |
| Three chats came back rate limited | load_chat calls fired at once | one at a time, 3 seconds apart, one retry after the stated wait |
| One chat turned into eight records | the chat was read in pages | merge pages into one thread, dedupe on time plus text |
| Your own message looked last | their last message was an attachment with no text, and it was dropped | keep blank messages when deciding who spoke last |
| The same person was raised every morning | you had answered by text or email, which Kondo can't see | check your other channels' last outbound after their message |
| A thread you dismissed kept coming back | Kondo's activity time differs slightly from the message time | allow about a minute of slack before treating it as new activity |
| A date-only "replied" note looked older than their message | Kondo times are UTC; your notes are local dates | convert to local time first, and count a date-only note from the next day |
Things to leave out of the human's summary
- Chats skipped because they were group chats or already dismissed. Mention counts only if asked.
- Any Kondo identifier (thread keys, profile URNs). Use names and, if asked, the person's public profile link.