kondo-owed-reply-sweep
Skill1 starsChanged 17 days agoMITView on GitHub
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".
In this repository67 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- morning-paper-outreachSkill
- client-activation-checkinSkill
- client-churn-autopsySkill
- client-win-backSkill
- late-payment-chaseSkill
- network-path-mappingSkill
- rate-increase-planSkill
- sales-call-debriefSkill
- weekly-funnel-reviewSkill
- buyer-readSkill
- punch-upSkill
- call-topic-miningSkill
- ceo-exec-assistantSkill
- og-image-from-templateSkill
- weekly-site-and-ad-reportSkill
- icp-reviewSkill
- weekly-content-ideas-from-callsSkill
- client-performance-reviewSkill
- cold-email-sequenceSkill
- email-content-reviewerSkill
- scoring-analysis-and-distributionSkill
- delivery-audit-discovery-callSkill
- directionSkill
- rundownSkill
- source-checkSkill
- work-reviewSkill
- demandbird-exact-time-linkedin-postSkill
- linkedin-export-contact-importSkill
- mail-messages-contact-touchesSkill
- riverside-short-social-scheduleSkill
- youtube-transcript-panel-pullSkill
- email-voice-setupSkill
- upsell-opportunity-briefSkill
- ad-creative-content-strategySkill
- klaviyo-account-auditSkill
- facilitator-notesSkill
- local-prospectingSkill
- weekly-linkedin-postsSkill
- linkedin-watchlist-briefSkill
- pipeline-by-scriptSkill
- pre-session-flash-cardSkill
- write-in-the-owners-voiceSkill
- reddit-gtm-sprintSkill
- process-captureSkill
- sales-call-market-analyzerSkill
- linkedin-shoutout-postSkill
- plain-language-copy-checkSkill
- revenue-goal-funnel-mathSkill
- case-study-buildSkill
- cash-runway-forecastSkill
- client-profitability-readSkill
- client-proposalSkill
- content-briefSkill
- quarter-goal-filterSkill
- win-to-anglesSkill
- activity-incentive-sprintSkill
- candidate-interview-coachSkill
- client-list-stack-pitchSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 6 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
Call list_inbox with the "needs my reply" view and an after cutoff 14 days back, computed in UTC epoch milliseconds.
- Distinctive: line 24
If a chat comes back in pages, merge the pages into one thread before judging it.
- Distinctive: line 26
If you can check your email, texts or call log, suppress threads you already answered there after their last message.
- Distinctive: line 40
MUST stay read-only: never send, draft into Kondo, label or archive a chat from this sweep.
- Distinctive: line 41
MUST name people, never show Kondo's internal identifiers.
- Distinctive: line 42
MUST let the human decide who needs a reply.
- Distinctive: line 43
NEVER record anything when Kondo is down or returns an error.
- Very specific: line 44
NEVER fire load_chat calls in parallel.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
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.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

