smithery.ai

performance-tracking

Use when establishing measurement frameworks, dashboards, and optimization rhythms for live campaigns.

First seen Apr 2, 2026

Installation

$ npx skills add https://smithery.ai

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from smithery.ai · top by installs.

npx skills add https://smithery.ai

Browse all from smithery.ai

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 1,450 B
  • docs SUMMARY.md 130 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Performance Tracking Skill

When to Use

  • Before launch to define metrics, data sources, and reporting cadence.
  • During active campaigns to monitor pacing vs goals and trigger optimizations.
  • Post-campaign retros to capture learnings and benchmarks.

Framework

  1. Metric Hierarchy – define business (pipeline, revenue), leading (MQL, CTR), and diagnostic metrics (CPC, landing page CVR).
  2. Data Plumbing – map sources (ad platforms, MA, CRM, BI) and ensure consistent IDs/UTMs.
  3. Dashboard Build – create executive + operator views with automated refresh.
  4. Alerting – set thresholds for spend pacing, CPA, conversion drops, SLAs.
  5. Insight Cadence – daily standups, weekly deep dives, end-of-campaign retros.
  6. Documentation – record hypotheses, experiments, and outcomes.

Templates

  • KPI tree worksheet.
  • Dashboard spec (dataset, visualization, owner, refresh schedule).
  • Optimization log (date, insight, action, result).

Tips

  • Automate alert routing (Slack, email) so anomalies are actioned quickly.
  • Pair dashboards with narrative summaries to help execs interpret shifts.
  • Capture experiment context in the optimization log to prevent repeating failed tests.
  • Align BI/RevOps early so new metrics get logged before launch.