/team-performance-dashboard

name: team-performance-dashboard
category: get-qualified-meetings
type: use-case
tags: [analysis, coaching]
description: "Generate your Team Performance Dashboard from your La Growth Machine data: a head-of-sales cockpit that ranks each sender (rep) on reply rate, your success event (signups/meetings/deals) and conversion, surfaces hot leads going cold, and turns your best reps' campaigns into a coaching playbook for the rest. Pulls only YOUR live LGM data into one sortable all-KPI team table plus a value (€) layer, classifies real replies, and renders a live artifact. This is the PER-REP team view, not the per-campaign weekly-performance-advisor. Use when a head of sales, SDR manager, GTM engineer or RevOps wants per-member outbound stats, who converts best and why, which replies are unanswered, or what to clone across the team. Triggers on: 'stats by member', 'team performance dashboard', 'per-rep outbound', 'who converts best', 'weekly team performance', 'sales team cockpit', 'coach my SDRs', 'per-identity reply rate'. First run does a short setup (~10-15 min); later runs just rebuild. Maintained by La Growth Machine."

Team Performance Dashboard

Generate the user's **own** Team Performance Dashboard: a four-tab live artifact built from **their** La Growth Machine (LGM) data, ranked by **sender identity** (rep). This skill is **fully self-contained** — every rule needed to detect the environment, pull data, score, classify, mine patterns, and fill the dashboard is written below. It references no other document except the generic skill-download links table inlined in the handoff section.

Job to be done

Every week, show a head of sales **who's generating the most replies *and* the most actual conversions and why**, which hot leads are going cold, and how to spread what the best campaigns do across the reps who are behind — as coaching, not a scoreboard.

Three hard rules, always

1. **Only ever show the downloading user's data.** Pull exclusively from *their* connected MCPs. Never inject numbers, rep names, leads, campaign names, replies or examples from anyone else or from this skill's author. **The template ships empty**; it is filled at runtime with their live values. If a value can't be pulled, render the documented empty state — never a placeholder number and never a value borrowed from somewhere else. 2. **Rank for visibility, coach without punishing.** Reps are sorted by performance and a recommendation may name the rep a winning pattern came from ("apply what {rep}'s campaign does"). This is a manager-facing internal tool, so that transparency is intended. The line not to cross: never frame a low performer as failing — a rep below the account average gets "here's the proven fix", never "you're behind". No rep is hidden to spare feelings. 3. **The output is a LIVE, INTERACTIVE ARTIFACT — never a saved .html file and never a raw code block.** This is the single most common failure: do NOT write the filled HTML to a file on disk and stop, and do NOT paste it as a fenced code block. You MUST publish it through whatever **artifact / canvas / live-preview mechanism your current environment exposes** so the user gets a rendered, clickable dashboard they can open and interact with (sort the table, switch tabs, click Fix). On claude.ai and Claude Code this is the Artifacts/canvas surface; in a plain terminal with no artifact surface, say so and offer to open the rendered HTML in a browser instead — but the default and correct output is a live artifact, not a file. Do not hard-code a specific tool name; use the artifact capability that exists. On a refresh, **update the existing artifact** rather than creating a new one. `assets/dashboard-template.html` is the **build source only** — you fill its single `{{DASHBOARD_DATA}}` token in memory and render the result live.

---

Two modes

• **Setup mode** (first run, or LGM isn't connected / no config yet): interactive, conversational,

~10-15 minutes. Detect, guide connections, ask the setup questions, persist the config.

• **Generate mode** (every run once `./.wtp/config.json` exists and LGM is connected): run the

engine, fill the template, emit the artifact + a short handoff. No step-by-step narration.

---

Phase 0 — Detect (silent, no questions)

Check your **own tool list** — never ask what's installed.

• **LGM MCP present?** True if tools like `list_identities`, `list_campaigns`, `get_campaign_stats`,

`get_conversations_to_reply`, `search_conversations`, `get_conversation_messages` are available.

• **CRM / deal MCP present?** (HubSpot/Salesforce/Pipedrive) · **Airtable MCP?** · **Stripe?**
• **Companion skills available?** `campaign-challenger`, `campaign-impact-analyzer`.

Record these booleans and move on. Do not announce the detection.

Phase 1 — LGM MCP gate

**If present:** say "LGM connected" in one line, continue. **If absent:** the dashboard is built entirely from LGM data, so guide the install (don't ask "is it installed?" — you already know it isn't): 1. Connect the La Growth Machine MCP at https://lagrowthmachine.com/mcp/ (browser OAuth, no API key), or run `sh install.sh` from the gtm-system repo. 2. No LGM account yet → register at https://app.lagrowthmachine.com/register?utm_source=claude_skill&utm_medium=mcp&utm_campaign=team-performance-dashboard and re-run. 3. **Re-detect** and loop until the LGM tools appear, then continue.

Phase 2 — Setup questions (~6, one at a time)

Detect before asking; propose a default each time; validate each connection with a test call. Open with: *"This takes about 10-15 minutes to get everything wired properly."*

**Q1 — Success event (keystone).** > "What's the outcome you want to measure — a meeting booked, a signup, a deal, an account created, > or something else?" Capture `outcomeLabel` + `outcomeType`. Propose a default if detectable (a CRM with deals → "deal"). This drives the header KPI, the *