Agent skill
campaign-dashboard
This skill should be used when the user says 'campaign status', 'show me campaigns', 'visualize campaigns', 'what's the state of campaigns', 'campaign dashboard', 'open campaign view', 'how are outreach campaigns doing visually', 'show campaign pipeline', 'show me the leads for [campaign]', or any variant indicating they want a visual browser-based campaign dashboard.
Filed under Analytics and reporting.
From Othmane-Khadri/YALC-the-GTM-operating-system · 61 skills · 290 · pushed 2026-08-20
What it does when it runs
This skill should be used when the user says 'campaign status', 'show me campaigns', 'visualize campaigns', 'what's the state of campaigns', 'campaign dashboard', 'open campaign view', 'how are outreach campaigns doing visually', 'show campaign pipeline', 'show me the leads for [campaign]', or any variant indicating they want a visual browser-based campaign dashboard.
Read from the skill and the 0 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.
- Keys and connectors you must supply
- None found.
- Hosts it reaches
- No third-party host appears in the skill or its bundled files.
- Tool permissions it declares
- No
allowed-toolsin the frontmatter. It does act, so it runs under whatever permissions your session already grants. - Actions present in the files
- shell
Install it
View source on GitHub ↗git clone --depth 1 --filter=blob:none --sparse https://github.com/Othmane-Khadri/YALC-the-GTM-operating-system.git /tmp/YALC-the-GTM-operating-system git -C /tmp/YALC-the-GTM-operating-system sparse-checkout set ".claude/skills/campaign-dashboard" mkdir -p ~/.claude/skills/campaign-dashboard cp -R "/tmp/YALC-the-GTM-operating-system/.claude/skills/campaign-dashboard/." ~/.claude/skills/campaign-dashboard/
Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗
The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.
The skill
Source on GitHub ↗Reproduced in full from Othmane-Khadri/YALC-the-GTM-operating-system/blob/5686d1f2f526346133f78eef3349fc5a655757b4/.claude/skills/campaign-dashboard/SKILL.md, which is licensed MIT (repository). 384 words, 11 headings.
Campaign Dashboard Skill
Opens the GTM-OS campaign visualization dashboard in the browser — Heyreach/Lemlist-style cards grid with per-lead timelines and variant comparison.
When This Skill Applies
- "campaign status" / "campaign dashboard"
- "show me campaigns" / "visualize campaigns"
- "what's the state of campaigns"
- "open campaign view" / "campaign pipeline"
- "show me the leads for [campaign name]"
- "how are outreach campaigns doing" (when visual context is implied)
NOT this skill (use campaign-intelligence instead):
- "campaign report" / "weekly campaign report" → generates a Notion text report
- "compare variants" / "which angle is winning" → text analysis
What This Skill Does
- Starts the GTM-OS server (if not already running)
- Opens the campaign dashboard at
http://localhost:3847/campaigns - Shows campaign cards with live metrics from SQLite
- Drill into any campaign for per-lead timeline + variant A/B comparison
What This Skill Does NOT
- Generate Notion reports (that's campaign-intelligence)
- Modify campaigns, leads, or variants
- Send any LinkedIn messages
Workflow
Step 1: Start the GTM-OS Dashboard
npx tsx src/cli/index.ts campaign:dashboard
This starts the Hono.js server on port 3847 and opens /campaigns in the browser.
Step 2: If User Wants a Specific Campaign
If the user mentioned a specific campaign name:
- Query the campaign ID:
npx tsx -e "
import { db } from './src/lib/db/index.ts';
import { campaigns } from './src/lib/db/schema.ts';
const rows = await db.select({ id: campaigns.id, title: campaigns.title }).from(campaigns);
console.log(JSON.stringify(rows, null, 2));
"
- Open the specific campaign detail page:
open "http://localhost:3847/campaigns/{campaignId}"
Step 3: Report Back
After opening the dashboard, tell the user:
- The URL that was opened
- A quick summary of what they'll see (number of campaigns, active count, total leads)
- Remind them they can filter by status and search leads in the UI
Dashboard Pages
| URL | What it shows |
|---|---|
/campaigns | All campaigns as cards with metrics, funnel progress bars, status filters |
/campaigns/:id | Single campaign: variant comparison cards + per-lead horizontal timeline |
Port
Default: 3847. If port is in use, pass --port <number> to the CLI command.
Dependencies
- SQLite database with campaign data (
gtm-os.db) - No external APIs needed — reads directly from local DB
Other skills for the same job
Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.
- campaign-copywriting by growthenginenowoslawski · 668
- campaign-strategy by growthenginenowoslawski · 668
- smartlead-campaign-upload-public by growthenginenowoslawski · 668
- campaign-postmortem by zapier · 334
- mega-campaign-generator by zapier · 334
- campaign-builder by janskuba · 200
- campaign-sending by extruct-ai · 107
- ad-campaign-management by manojbajaj95 · 95
Need help setting it up?
This page tells you what campaign-dashboard does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.
Book a call →The directory stays free. There is nothing gated behind this.