daily-five
Skill1 starsChanged 24 days agoMITView on GitHub
Runs a founder's short daily habit for finding customers, in about five minutes: pick today's few people, choose the one move for each, write it, and log what happened so tomorrow is smarter. Built on doing things that don't scale, one person at a time. Use when a founder asks for a daily routine to get customers, founder-led sales habits, how to stay consistent with talking to customers, or \"I keep putting off marketing\".
In this repository15 other files it gives its agents.
- alert-wordsSkill
- ask-for-an-introductionSkill
- customer-interviewSkill
- expert-to-skillSkill
- find-one-personSkill
- first-messageSkill
- one-line-pitchSkill
- readiness-checkSkill
- reddit-reply-not-pitchSkill
- research-one-personSkill
- show-hn-launchSkill
- update-that-earns-a-dmSkill
- where-my-customers-areSkill
- who-buys-from-meSkill
- why-they-said-yesSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 56
No targets like "forty conversations" or "ten a day".
- Distinctive: line 57
If more replies arrive than you can answer properly, send fewer messages.
- Distinctive: line 58
Never automate the sending.
- Distinctive: line 60
Keep doing this after you have customers.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Daily five
Five minutes a day, every day, beats a perfect plan you run once.
Finding customers works like getting fit. Nobody gets fit from one heroic week; the people who do it just show up every day without deliberating. Founders push talking to customers to the bottom of the list ("after this feature, after this blog post"), and it never happens. The fix is to make it small enough to fit into moments you already have: with the first coffee, on the commute, while the pasta cooks.
This skill runs that session.
What you need
- Who the customer is, in short.
- Today's candidates: posts, alerts, replies waiting for an answer, people from yesterday's list. Paste whatever you have.
- Yesterday's log, if there is one.
The session
- Replies first. Anyone who answered yesterday gets a response before anyone new. A conversation already started is worth more than a new one.
- Pick today's people. From the candidates, pick the few most ready to buy, using the
readiness-checklogic: their own words, recent, a buyer not a seller. Fewer is fine. If nobody is genuinely ready today, pick the best fit and engage lightly. - Choose one move per person.
- A useful public reply to what they posted
- A connect or follow plus a genuine reaction to their work
- A short first message (see
first-message) - An introduction request (see
ask-for-an-introduction) One move each. No multi-step plans.
- Write and send. Each one specific to the person. If you can't write something specific, skip them.
- Log it. One line per person: who, what you did, and what you'll look for tomorrow.
- Note one learning. What did someone say today that changes how you describe the problem, who you look for, or what you build?
Output
Replies to answer first:
- <person>: <suggested reply>
Today's people:
1. <person> · <why today> · <move> · <draft>
Log:
| Date | Person | Move | Result | Next |
Today's learning: <one sentence>Rules
- No targets like "forty conversations" or "ten a day". There's no magic ratio between conversations and customers. The habit moves the number.
- If more replies arrive than you can answer properly, send fewer messages. A reply you can't serve well is wasted.
- Never automate the sending. The point is that each message is to one person, written for them.
- Watch speed, not counts. How quickly the right people get it and say yes tells you more than how many you contacted.
- Keep doing this after you have customers. The founder stays the person who talks to customers, even when other things get handed off.
A realistic week
Full-time founders with no other commitments can spend far more than five minutes and should. Founders with a job, a family or a product to ship can do five minutes and still see results, because the hard part isn't time. It's knowing who to talk to and what to say, which is what the session decides for you.
With MyPip (coming)
This is the habit MyPip is built around: it finds who's ready and makes the introductions, so your five minutes go to people who already said yes. When the MyPip MCP is live, this skill will be able to start each session from today's people and replies in your MyPip account.
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.

