ceo-weekly-review
Skill9 starsChanged 6 months agoMITView on GitHub
Weekly CEO review — 10 questions, dashboard, self-deception check, next week focus
2 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- yiyan-yixing/skillstheir own version, first seen Aug 5, 2026
- Layneformalized225/ai-cofounderedited, first seen Mar 22, 2026
Other versions2 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Layneformalized225/ai-cofounder★ 183% same
Wrote their own version · 1
- yiyan-yixing/skills★ 1same name
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
- 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
- morning-briefSkill
- 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
Show its rules and text
We split this skill into the rules it gives an agent
17 rules. About 0 are common, 13 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈13
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 32
If compliance < 3/5 days → diagnose friction: "GTM X/5 дней.
- Very specific: line 40
Read MEMORY.md — current wedge, stage, hypotheses, constraint
- Very specific: line 41
Read memory/hypotheses.json — experiment status
- Very specific: line 42
Read daily logs for this week (memory/YYYY-MM-DD.md x 7)
- Distinctive: line 43
If PostHog is available — query key metrics for the week
- Distinctive: line 63
Search/chat weekly active users
- Distinctive: line 107
If we were starting the company today, would we choose the same wedge?
- Distinctive: line 113
Only warm intros convert?
- Distinctive: line 116
Every early customer wants a different product?
- Distinctive: line 124
If 3+ signals fire — flag hard.
- Distinctive: line 128
Before final recommendations — challenge your own analysis:
- Distinctive: line 130
Consistency: do my dashboard conclusions contradict my answers to the 10 questions?
- Distinctive: line 132
Constraint alignment: do my next-week recommendations exploit the constraint (market learning speed)?
- Distinctive: line 135
If issues are found — fix recommendations BEFORE sending.
- Very specific: line 149
Update MEMORY.md if any of these changed: stage, wedge, key learnings.
- Distinctive: line 153
Don't send everything in one message.
- Distinctive: line 158
Follow output preferences from USER.md (language, format, platform constraints).
≈ “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
CEO Weekly Review
Runs every Sunday evening (cron) or manually on the founder's command.
Process
Step 0: System Throughput (Critical Chain — DO THIS FIRST)
How many validated beliefs changed this week?
- Hypotheses resolved (keep/kill/reframe): X
- ICP assumptions updated: X
- Decisions on pricing/positioning/message: X
- Target: >= 1 meaningful change/week
Constraint check:
- Read
MEMORY.md -> System Constraint - CEO time on constraint-work (conversations, discovery, sales) vs non-constraint: X/Y hours
- Target: >35% on constraint
- Has the constraint shifted? If yes -> update MEMORY.md
Focus discipline (from memory/focus-state.json + memory/focus-history.jsonl):
- GTM minimum completed: X/Y days this week
- Waivers: N (list reasons — are they legit or avoidance?)
- Streak: N days
- Most common MVNA type completed (research/outreach/strategy)
- If compliance < 3/5 days → diagnose friction: "GTM X/5 дней. Что мешало? (friction, RSD, energy, priorities)" — don't shame
WIP check:
- Active hypotheses: X (limit: 3). Active experiments: X (limit: 2).
- Relay race: are there hypotheses with enough evidence for a decision right now?
Step 1: Gather Data
- Read
MEMORY.md— current wedge, stage, hypotheses, constraint - Read
memory/hypotheses.json— experiment status - Read daily logs for this week (
memory/YYYY-MM-DD.mdx 7) - If PostHog is available — query key metrics for the week
Step 2: CEO Weekly Dashboard (Bible Section H.1)
Build the dashboard across 9 categories. PostHog for 2,3,5,6,9. The rest — ask the founder.
Header: Current stage | Wedge | System constraint | Biggest risk this week
1. Learning (ASK the founder):
- Qualified conversations this week (target: 8-12)
- Repeated pain rate (same problem/trigger recurring?)
- What changed our beliefs?
2. Product (PostHog):
- TTFV: median timeSincePrevious for First Value Moment
- Activation: funnel_next_stage_available -> first_value_delivered stage
- Funnel: signup -> activated -> return -> regular -> power (compare to last week)
3. Usage (PostHog):
- Retained active: Weekly Active milestone count
- Search/chat weekly active users
- Deep workflow usage: deep_workflow_started
4. Pipeline (ASK the founder):
- New pipeline in wedge
- Win rate trend
- Sales cycle
5. Retention (PostHog + manual):
- Healthy accounts: regular_usage+ stage
- Expansion pull: team_invitation_sent events
6. B2C -> B2B (PostHog — KEY):
- Target signups: Account Created + qualified filters
- Active companies: unique organizationId
- Companies with 2+ users
- Same-company emergence rate
7. Execution (ASK the founder):
- Experiment cycle time, belief changes this week
8. Economics (ASK the founder):
- Burn/runway
9. PMF signals (MIX):
- Wedge repeatability (last wins look alike?)
- Organic pull (sharing events, inbound, referrals)
Attribution (PostHog):
- Top sources by $initial_utm_source for activated users
Step 3: 10 Weekly Questions (Bible Section P)
Go through each question and provide a brief answer based on gathered data:
- What did we learn this week that actually changed our beliefs?
- Which segment showed the strongest pain, fastest value, and repeatability?
- Did I (the founder) personally talk to enough customers, buyers, and lost prospects?
- Which metric moved, and what decision follows from it?
- Is the B2C layer creating enterprise signal or just activity?
- Are recent wins becoming more similar or more bespoke?
- Is time-to-first-value decreasing?
- Are healthy accounts asking for more on their own?
- What are we calling progress because it feels good?
- If we were starting the company today, would we choose the same wedge?
Step 4: Self-Deception Check (Bible Section P)
Check 10 self-deception signals:
- Only warm intros convert?
- Traffic/signups grow, but target-cohort activation doesn't?
- Calling pilot revenue "ARR"?
- Every early customer wants a different product?
- Buyers love demos but don't use the product?
- Annual contracts look OK, but engagement is dead?
- Hiring because learning feels slow?
- Founder can't explain the last 5 deals?
- B2C grows, but doesn't create accounts or pipeline?
- Team is very busy, but beliefs and priorities don't change?
If 3+ signals fire — flag hard.
Step 5: Adversarial Self-Review
Before final recommendations — challenge your own analysis:
- Consistency: do my dashboard conclusions contradict my answers to the 10 questions?
- Proxy skepticism: am I assessing real progress toward PMF or convenient metrics?
- Constraint alignment: do my next-week recommendations exploit the constraint (market learning speed)?
- Inversion: what would have to happen next week for [YOUR_PRODUCT] to get WORSE? Do my bets protect against that?
If issues are found — fix recommendations BEFORE sending.
Step 6: Next Week
Formulate:
- Top 3 bets for next week (tied to constraint)
- Top 3 kills (what to stop — Jobs's subtraction)
- Top 3 asks (what is needed from the founder or externally)
For each bet: reversibility (two-way / one-way door) and kill signal.
Step 7: Save
Log the result to memory/weekly/YYYY-WW.md.
Update MEMORY.md if any of these changed: stage, wedge, key learnings.
Chat Output Format
Don't send everything in one message. Split into 3-4 short ones:
- Dashboard summary (5-7 lines)
- Key answers + self-deception flags (5-7 lines)
- Next week focus (3-5 lines)
Follow output preferences from USER.md (language, format, platform constraints).
Tone
Like an honest Chief of Staff: facts -> implications -> actions. Don't sugar-coat.
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.

