agentleFS
gokulsvisiongokulsvision/Crewm8-Social-Media-Manager-Skill-Graph/skills/analytics/metrics-track/SKILL.md

metrics-track

Skill17 starsChanged 7 months agoMITView on GitHub

Track post-level metrics across all platforms — impressions, engagement rate, profile clicks, follows, link clicks — with weekly aggregation and trend detection for performance analysis.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After a campaign or launch

    line 32
  2. Distinctive:

    Not tracking saves/bookmarks (strongest signal of value density)

    line 113

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Metrics Track

Pull and track post-level metrics across every platform. Data without tracking is just guessing. This skill defines what to measure, how to pull it, and how to interpret it so the brand knows what's actually working.

Purpose

Most social media managers track everything and understand nothing. This skill focuses on the metrics that matter — engagement rate (quality), follower growth (reach), link clicks (conversion) — and flags anomalies worth investigating.

When to Use

  • Daily pull for recently published posts
  • Weekly aggregation for performance reporting
  • Before performance-report generation
  • After a campaign or launch

Inputs Required

  • Platform analytics access (native or third-party)
  • List of posts for the tracking period
  • Historical baselines (for anomaly detection)

Quick Reference

MetricWhat It MeasuresWhy It Matters
ImpressionsHow many times content was shownTop of funnel — are we being seen?
Engagement rate(Likes+comments+shares+saves) / impressionsContent quality — are people responding?
Profile visitsClicks to profile from contentBrand interest — are people exploring?
Follows / growthNew followers (net)Is the audience expanding?
Link clicksClicks on linksIs content driving action?
Saves / bookmarksPosts saved for laterValue density — worth keeping?
Shares / repostsContent shared by othersVirality potential
Video retention% of video watchedVideo quality

Procedure

  1. Pull metrics per post: impressions, likes, comments, shares, saves, link clicks, profile visits, follows.
  2. Calculate derived metrics:
    • ER% = (likes + comments + shares + saves) / impressions * 100
    • Follower growth rate = net new / total followers * 100
    • CTR = link clicks / impressions * 100
  3. Build running database: Track every post with metrics for 90+ days. Store: post ID, platform, date, format, pillar, hook type, metrics.
  4. Establish baselines:
    • Average ER per platform (trailing 30 days)
    • Average impressions per post type
    • Average weekly follower growth
    • "Normal" range for anomaly detection
  5. Flag anomalies:
    • 2x above baseline (investigate what worked)
    • Below 50% of baseline (investigate what broke)
    • Sudden follower spike or drop

Output Format

# Metrics Track: [Week]

## Weekly Snapshot
| Platform | Avg Impressions | Avg ER% | Best Post | Worst Post | Follower Change |
|----------|----------------|---------|-----------|------------|----------------|
| X | [N] | [N]% | [Title] | [Title] | [+N] |
| LinkedIn | [N] | [N]% | [Title] | [Title] | [+N] |
| IG | [N] | [N]% | [Title] | [Title] | [+N] |
| TikTok | [N] | [N]% | [Title] | [Title] | [+N] |

## Anomaly Flags
- **Overperformer:** [Post] — [ER% vs baseline]. Why? [Hypothesis]
- **Underperformer:** [Post] — [ER% vs baseline]. Why? [Hypothesis]

## Running Benchmarks (30 Days)
| Platform | Avg ER% | Best Format | Best Day/Time |
|----------|---------|-------------|---------------|
| X | [N]% | [Format] | [Day/Time] |
...

Done Criteria

The skill is complete when:

  1. Metrics are pulled for all posts in the tracking period
  2. ER%, growth rate, and CTR are calculated
  3. Anomalies are flagged (overperformers and underperformers)
  4. Running benchmarks are updated
  5. Data is ready for performance-report

Pitfalls

  • Tracking vanity metrics (impressions without engagement)
  • Comparing ER across platforms directly (X ER != LinkedIn ER != IG ER)
  • Pulling metrics too early (post under 6 hours old isn't reliable)
  • Not tracking saves/bookmarks (strongest signal of value density)
  • Ignoring video retention

Verification

Can you answer "what was our best post this week and why?" from this data? Can you answer "are we growing faster or slower than last month?" If not, the tracking is incomplete.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.