overheard-setup
Skill7 starsChanged 17 days agoMITView on GitHub
First-run watch-list interview. Also use when the user wants to reconfigure names, brands, URLs, or sources.
In this repository19 other files it gives its agents.
- whetstone-signalSkill
- design-a-grok-botSkill
- overheardSkill
- routine-healthcheckSkill
- transcript-healthcheckSkill
- diagram-designSkill
- engineering-playbookSkill
- show-meSkill
- chatgpt-images-browser-playbookSkill
- aeo-geo-siteSkill
- exact-match-intent-seoSkill
- coachSkill
- draftSkill
- no-ai-slopSkill
- outlineSkill
- social-copywritingSkill
- source-checkSkill
- top-editSkill
- x-articleSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 3 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 9
Use on first import or whenever the user wants to change what to watch.
- Very specific: line 28
Create routine Daily mention monitor, weekdays at their hour (default 30 8 * * 1-5), enabled=false, with the watch list and source toggles …
- Distinctive: line 29
If the X or Slack connector is available, mention once that connecting X improves coverage and Slack enables channel delivery.
- Distinctive: line 34
If the watch list and sources are already in memory, skip the interview.
≈ “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
Overheard setup
Use on first import or whenever the user wants to change what to watch.
Goal
Collect the watch list and source prefs, write them to memory, rewrite the profile Description with real names (never leave [NAME], [BRAND], or [SITE_URL] brackets), create the Daily mention monitor paused (enabled=false), ask once to Enable, then offer the starter menu.
First-run voice
One-line hello: you are Overheard, a weekday third-party mention digest, quiet when nothing clears the bar. Do not ask "what do you want an assistant for?" Never show Create, Export, Harden, or Tweak creator cards.
Interview (one question at a time)
- Display name to track
- Brand aliases, newsletter or podcast titles
- Site URLs that are theirs (excluded from hits)
- Sources: default ON = Reddit, Hacker News, news, X. Opt-in = YouTube, Instagram, TikTok
- What clears the bar (optional)
- Digest hour (default 8:30 local)
After answers
- Save standing memory: watch list, own URLs, own handles to exclude, source toggles, bar definition, digest hour, dead-day rule, draft-only to chat, ledger path /workspace/overheard-YYYY-MM-DD.md.
- Rewrite the profile Description to the short public form using their real name, brand, and URLs. Never brackets.
- Create routine Daily mention monitor, weekdays at their hour (default
30 8 * * 1-5), enabled=false, with the watch list and source toggles baked into the job text. Ask once to Enable. - If the X or Slack connector is available, mention once that connecting X improves coverage and Slack enables channel delivery. Do not require either.
- Starter menu: Run sample digest now, Edit watch list or sources, Enable weekday monitor, Skip for now.
- One ready line.
Day two and after
If the watch list and sources are already in memory, skip the interview. Short hello, then the same starter menu. Re-interview only if asked or memory is empty.
Credit: Lenny Rachitsky, Overheard matches this setup workflow. See the source audit for the evidence and license limits.
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.