weekly-funnel-review
Skill1 starsChanged 17 days agoMITView on GitHub
Use this skill on the same day every week to see where new business actually comes from, when the numbers live in five different places and nobody agrees what a qualified call is. Produces one row per week, appended to a running history: traffic and outbound by channel, calls booked against calls held, fit, signed work, and revenue split by segment, with the one thing that changed. Also use for "weekly numbers", "where are leads coming from", "how many calls did we hold", "refresh the funnel".
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
- 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
- kondo-owed-reply-sweepSkill
- 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
9 rules. About 0 are common, 9 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈9
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 33
Write one line on what changed and why, and nothing else.
- Distinctive: line 45
MUST name one source of truth per metric and keep it fixed.
- Distinctive: line 46
MUST record booked and held separately, from different sources.
- Distinctive: line 47
MUST append each week to a stored history, never overwrite.
- Distinctive: line 48
MUST split revenue by segment.
- Distinctive: line 49
MUST keep the start date of the history fixed.
- Distinctive: line 50
MUST note any definition change in the record, with the date.
- Distinctive: line 51
NEVER compare a stage to a stage measured a different way.
- Distinctive: line 52
NEVER let a channel with no activity read as a channel with no demand.
≈ “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 on a fixed weekday, every week, to the firm's own new-business funnel. Produces one appended row and a short read of what moved.
The play
- Name one source of truth per metric before measuring anything, and write the list down. Two systems will always disagree about how many calls happened, and a week spent arguing about which is right is a week with no numbers. The rules for choosing, and the ones worth copying, are in references/definitions.md.
- Fix the start date of the history and never move it. A rolling twelve-week window hides the trend that matters after a repositioning or a new service launch. Pick the date the current motion began and count from there.
- Pull the stages in order: traffic, outbound activity by channel and by sender, calls booked, calls held, fit, opportunities, signed, revenue. The full chain and what each stage must exclude are in references/definitions.md.
- Record booked and held as separate numbers, every week, from different sources. The gap between them is the no-show rate, it is usually the largest unmanaged leak in a small firm's funnel, and it is invisible to anyone tracking only one of the two.
- Split revenue by segment, not as a single total. A legacy base and a new motion inside one number means the new motion is unreadable for a year. The split to use is in references/definitions.md.
- Append the week to the history rather than overwriting a dashboard. A dashboard showing only this week cannot answer whether anything is working, and the history is the entire value of doing this weekly.
- Branch by what the week shows:
- A stage down with everything above it flat: a conversion problem at that stage. Look there, not at the top.
- Everything down together: an input problem. Check whether the outbound actually went out.
- Calls booked up, held flat: a no-show problem, which is a booking and reminder problem, not a demand problem.
- A channel at zero that was not zero: check it ran before concluding anything about demand.
- One channel producing everything: note the concentration. It is a risk even in a good week.
- Write one line on what changed and why, and nothing else. The numbers are the artifact; the commentary is for the one thing a reader would otherwise have to work out themselves.
What good looks like
- First thing I check that most people skip: booked minus held. Everyone tracks calls booked because it feels like progress, and the no-shows quietly delete a third of the week.
- The mediocre version: a dashboard rebuilt from scratch each week, with whatever metrics were handy, no stored history, and no fixed definitions. It produces a number nobody can compare to anything.
- I know the review is working when a disagreement about a number ends by naming the source rather than by debating the number.
- Second test: the history can answer "has this channel ever worked" without anyone opening another system.
- Red flag: a definition changing mid-quarter. Whatever the reason, the history before and after is no longer one series, and the change needs noting in the record.
Rules
- MUST name one source of truth per metric and keep it fixed.
- MUST record booked and held separately, from different sources.
- MUST append each week to a stored history, never overwrite.
- MUST split revenue by segment.
- MUST keep the start date of the history fixed.
- MUST note any definition change in the record, with the date.
- NEVER compare a stage to a stage measured a different way.
- NEVER let a channel with no activity read as a channel with no demand.
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.

