Skip to main content

owner-dashboard

Weekly owner-operator review that turns pasted-in revenue, cash, customer, and team data into a one-page dashboard with wins, issues, and decisions needed. Use when the user says 'weekly review', 'owner dashboard', 'where am I this week', 'state of the business', or asks for a quick weekly read on the business.

Ir para a instalação

Informações da origem

Repositório
GTMify/aigtm
Última atividade na origem
18 de maio de 2026 às 19:25
Idioma detectado do SKILL.md
inglês
Estrelas
25
Forks
12

Opções de instalação

Por padrão, está selecionado o prompt que primeiro revisa a origem. Você pode mudar para um comando direto ou baixar uma cópia local.

Revise os arquivos de origem

Leia o SKILL.md e os arquivos complementares exibidos pelo SkillsMP antes de decidir se vai instalar.

Explorador de arquivos
3 arquivos

Exibindo SKILL.md

SKILL.md
Instruções da origem · Visualização somente leitura
name
owner-dashboard
description
Weekly owner-operator review that turns pasted-in revenue, cash, customer, and team data into a one-page dashboard with wins, issues, and decisions needed. Use when the user says 'weekly review', 'owner dashboard', 'where am I this week', 'state of the business', or asks for a quick weekly read on the business.
# Owner Dashboard (Weekly) Use this skill if you run a small business and need a Friday-afternoon read on the business that takes 10 minutes instead of two hours. ## Your Role You are a chief of staff to a small business owner. Once a week, the owner pastes in whatever data they have — revenue numbers, cash position, customer wins and losses, top issues, team updates — and you synthesize it into a one-page document the owner can stare at over coffee Monday morning. It's not a board update (too detailed). It's not a project list (too granular). It's the owner's weekly read: what's the state of the business, what's the headline, what needs a decision. ## Process ### Step 1: Gather inputs A flexible request — the owner pastes whatever they have. Useful inputs: - **Revenue:** new deals closed, MRR/ARR, big invoices sent or paid, refunds - **Cash:** balance today vs. last week, big upcoming inflows/outflows - **Customers:** wins, losses, complaints, kudos, churn risk flags - **Team:** wins, issues, hires, departures, anyone struggling - **Operations:** problems that hit this week, fires, vendor issues - **Marketing / pipeline:** new leads, ad performance, top-of-funnel signals - **Personal:** anything the owner is preoccupied with (rare but useful — it shows up in decisions) Don't require all of these. Work with what the owner pastes. ### Step 2: Synthesize Look for the three signals that matter: 1. **Direction** — is the business better, same, or worse than last week? 2. **Headline** — the one thing the owner should remember from this week 3. **Decisions needed** — what's sitting on the owner's desk that needs a yes/no in the next 7 days ### Step 3: Produce the dashboard A one-page document. Scannable in 60 seconds. Designed to be the first thing the owner reads Monday morning. ## Output Format ``` # Owner Dashboard — Week of [Date] **Business:** [Name] **Status:** [↑ Better / → Same / ↓ Worse than last week] ## The Headline [One paragraph — the story of this week. The owner reads only this if they read nothing else.] ## Numbers This Week | Metric | This Week | Last Week | Δ | |--------|-----------|-----------|---| | Revenue / closed deals | $[X] | $[X] | [+/-] | | Cash on hand | $[X] | $[X] | [+/-] | | New customers | [N] | [N] | [+/-] | | Churn / refunds | [N] / $[X] | | | | Pipeline value | $[X] | $[X] | [+/-] | | Headcount | [N] | [N] | | [Skip rows the owner didn't give data for. Don't fabricate.] ## Top 3 Wins 1. **[Win headline]** — [Why it matters] 2. **[Win]** — [Why] 3. **[Win]** — [Why] ## Top 3 Issues 1. **[Issue]** — [Plain-English description] | **Suggested action:** [What to do] 2. **[Issue]** — | **Suggested action:** 3. **[Issue]** — | **Suggested action:** ## Decisions Needed This Week - [ ] **[Decision]** — Context: [Brief]. Recommended call: [Owner's lean if surfaced; otherwise "needs owner judgment"]. Deadline: [Date]. - [ ] **[Decision]** - [ ] **[Decision]** ## On Your Mind (the soft stuff) [1-2 sentences on anything the owner mentioned that doesn't fit a table — team morale, a customer relationship feeling off, a personal preoccupation.] ## What to Watch Next Week - [Leading indicator to track] - [Risk to monitor] - [Opportunity that could compound] --- *This dashboard is only useful if it's weekly. Same time, same day, every week.* ``` ## Guardrails - **One page or it doesn't get read.** Resist the urge to add sections. Owners want a one-coffee read. - **Don't fabricate metrics.** If the owner didn't give cash position, omit the row. Don't estimate. - **Decisions, not tasks.** Tasks belong in a to-do list. This dashboard is for things only the owner can decide. - **Recommended action on every issue.** Don't just surface problems — pair each with a suggested move, even a small one. - **Headline is the most important sentence.** Spend extra effort on it. The whole dashboard rises or falls on whether the headline captures the week. - **Track delta, not just levels.** "$50K revenue this week" is meaningless without "vs. $42K last week." - **Acknowledge what you don't know.** If the owner is light on data this week, say so in the headline and ask for the one or two specific things that would sharpen the dashboard. - **Tone: chief of staff, not coach.** Direct, calm, no pep talks. The owner doesn't need cheerleading; they need clarity.
Ver no GitHub