morning-brief
Skill9 starsChanged 6 months agoMITView on GitHub
Daily Morning Brief for CEO (09:30 cron). Reports what bot DID overnight, presents pre-staged GTM action for approval, shows pipeline status. Replaces old morning-briefing skill. Output = one Telegram message, max 15 lines.
25 other projects use a version of this.
Adopted by
Most recently taken up by
- chrisblattman/claudeblattmantheir own version, first seen Nov 8, 2026
- MaguiSella/second-brain-startertheir own version, first seen Nov 8, 2026
- heypastel/pastel-outbound-systemtheir own version, first seen Nov 8, 2026
- amanuelmamo7/Skillstheir own version, first seen Nov 7, 2026
- rami-maalouf/skillstheir own version, first seen Nov 1, 2026
- rgourley/quant-garagetheir own version, first seen Nov 1, 2026
Other versions25 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 25
- chrisblattman/claudeblattman★ 479same name
- jezweb/vite-flare-starter★ 49same name
- chacosoldier/compabob★ 34same name
- MaximeGaudin/second-brain-starter★ 8same name
- rgourley/quant-garage★ 7same name
- TheCraigHewitt/cowork-starter-pack★ 5same name
- megandmartin/agent-skills-repo★ 3same name
- DScardini91/agentic-os★ 2same name
- heypastel/pastel-outbound-system★ 2same name
- rami-maalouf/skills★ 2same name
15 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository78 other files it gives its agents.
- anti-pattern-auditSkill
- brand-storytellingSkill
- business-investigationSkill
- ceo-weekly-reviewSkill
- cold-emailSkill
- community-buildingSkill
- company-intelSkill
- competitive-analysisSkill
- competitor-researchSkill
- composio-cliSkill
- conducting-user-interviewsSkill
- content-strategySkill
- copywritingSkill
- daily-recapSkill
- decision-playbookSkill
- designing-growth-loopsSkill
- discovery-debriefSkill
- email-sequenceSkill
- enterprise-salesSkill
- evening-recapSkill
- exa-code-searchSkill
- exa-company-researchSkill
- exa-lead-genSkill
- exa-people-researchSkill
- exa-personal-siteSkill
- exa-x-searchSkill
- feedback-trackerSkill
- find-email-by-nameSkill
- focus-keeperSkill
- founder-salesSkill
- fpf-problem-solvingSkill
- github-stars-monitorSkill
- google-calendarSkill
- grafana-monitoringSkill
- humanizerSkill
- hypothesis-trackerSkill
- idea-generatorSkill
- install-openclaw-to-digitaloceanSkill
- install-openclaw-to-hetznerSkill
- install-openclaw-to-ycSkill
- launch-marketingSkill
- lead-enrichmentSkill
- measuring-product-market-fitSkill
- meeting-prepSkill
- metrics-briefingSkill
- openclaw-guideSkill
- openclaw-user-onboardingSkill
- orthogonalSkill
- outreach-senderSkill
- person-lookupSkill
- ph-launch-timelineSkill
- pipeline-managerSkill
- positioning-messagingSkill
- positioning-workshopSkill
- posthog-analyticsSkill
- prepare-yc-workshopSkill
- pricing-strategySkill
- problem-definitionSkill
- product-hunt-launchSkill
- product-led-salesSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 20 edited versions we read keep these.
9
Distinctive
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
Read MEMORY.md for: constraint, ICP, wedge, metrics.
- Distinctive: line 10
Read today's and yesterday's memory files.
- Distinctive: line 11
Follow output preferences from USER.md.
- Very specific: line 41
Run focus-keeper (Mode: Morning Plan) to generate ONE pre-staged action.
- Distinctive: line 50
If pipeline has warm leads → prioritize follow-up over cold outreach
- Distinctive: line 58
If outreach-feedback has new responses, mention them.
- Distinctive: line 87
No meta-questions ("how many conversations this week?")
- Distinctive: line 88
No shaming or compassion protocols — just report + action
- Distinctive: line 89
If CEO has ignored 5+ consecutive briefs, shrink to 3-line format
- Distinctive: line 90
After 3+ missed days, use fairy method (Dorofeyev) once, then just report
“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
[YOUR_PRODUCT] Context
Read MEMORY.md for: constraint, ICP, wedge, metrics. Read today's and yesterday's memory files. Follow output preferences from USER.md. For chat platforms: keep under ~15 lines.
Morning Brief
The CEO's primary daily touchpoint. Runs at 09:30 via cron. The brief is a REPORT of what was done + ONE action for approval. Not a nudge or question.
Data Sources (read all before composing)
memory/autonomous-actions.jsonl— what bot did since last briefmemory/pipeline.json— current pipeline statememory/outreach-feedback.jsonl— any responses receivedmemory/focus-state.json— GTM streak, daily minimum statusmemory/initiatives.json— active multi-day projectsmemory/hypotheses.json— active hypothesesmemory/pr-opportunities.json— found PR opportunitiesmemory/github-stars.json— recent stars
Compose the Brief
Section 1: Overnight Report (2-4 lines)
What the bot autonomously did since yesterday's recap:
- Enrichments completed
- Community replies published
- Pipeline changes (new prospects, updated scores)
- Signal scanner results
- PR opportunities found
If nothing happened: "Ночью без изменений."
Section 2: GTM Action (3-5 lines)
Run focus-keeper (Mode: Morning Plan) to generate ONE pre-staged action.
Show the actual draft/deliverable inline.
Format: "→ [what CEO does]. Reply 'go' — сделаю."
Rules:
- ONE action only, no A/B/C menus
- Draft must be ready (not "I could draft...")
- Monkey-friendly: describe what CEO does, not the task
- Include time commitment (e.g., "3 мин")
- If pipeline has warm leads → prioritize follow-up over cold outreach
- RSD-aware: async email > LinkedIn comment > cold call
Section 3: Status Line (1-2 lines)
Pipeline: N prospects | Streak: N дн | Hypotheses: N activeIf outreach-feedback has new responses, mention them.
Section 4: Pending Tier B Approvals (0-3 lines, only if items exist)
Items from autonomous work that need CEO approval:
- Draft emails to send
- LinkedIn posts to publish
- Content to approve
Format: "Tier B: [N] items pending. Reply 'show' to review."
Output Template
Доброе утро.
Ночью:
- [action 1]
- [action 2]
→ [GTM action description] (N мин)
[draft inline]
Reply "go" — отправлю. "Позже" — вечером.
●○○○○○○ (N/7) | Pipeline: N | Hypotheses: NRules
- Max 15 lines total
- No meta-questions ("how many conversations this week?")
- No shaming or compassion protocols — just report + action
- If CEO has ignored 5+ consecutive briefs, shrink to 3-line format
- After 3+ missed days, use fairy method (Dorofeyev) once, then just report
- Log brief delivery to autonomous-actions.jsonl
Related Skills
- focus-keeper — generates the GTM action
- evening-recap — the other daily touchpoint
- pipeline-manager — manages pipeline data
- structured-log — logging
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.

