smithery/gtmagents

performance-metrics

Use to define KPIs, alert thresholds, and reporting cadences for social calendars.

Installation

$ npx skills add smithery/gtmagents --skill performance-metrics

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/gtmagents · top by installs.

npx skills add smithery/gtmagents

Browse all from smithery/gtmagents

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,455 B
  • docs SUMMARY.md 109 B

History

  1. First recorded snapshot · 0 installs

SKILL.md

Social Performance Metrics Skill

When to Use

  • Setting KPI targets for new campaigns or evergreen programs.
  • Building dashboards or scorecards for exec/stakeholder updates.
  • Diagnosing pacing, reach, or conversion issues mid-flight.

Framework

  1. Metric Stack – map awareness (reach, impressions), engagement (ER, saves, shares), conversion (traffic, pipeline), and community health (sentiment, response time).
  2. Attribution & Tagging – enforce UTM structure, post IDs, and partner tags for downstream analysis.
  3. Alerting Rules – define thresholds (± variance vs goal), alert channels, and severity tiers.
  4. Reporting Cadence – daily pacing snapshots, weekly recaps, campaign retros, quarterly trendlines.
  5. Experiment Measurement – document test KPIs, guardrails, and success decision trees.

Templates

  • KPI scorecard (metric → target → actual → variance → owner → notes).
  • Alert playbook (trigger condition → notification → response steps).
  • Retro template summarizing learnings, insights, and backlog actions.

Tips

  • Normalize metrics per channel and audience to avoid false comparisons.
  • Pair with analytics warehouse data for revenue-attribution context.
  • Keep metadata consistent (pillar, campaign, creative ID) so insights are reusable.