Install
$ agentstack add skill-gokulb20-crewm8-social-media-manager-skill-graph-metrics-track ✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.
Security review
✓ PassedNo issues found. Passed automated security review. · v0.1.0 How review works →
- ✓ Prompt-injection patterns
- ✓ Secret / credential exfiltration
- ✓ Dangerous shell & filesystem operations
- ✓ Untrusted network calls
- ✓ Known-malicious package signatures
What it can access
- ✓ Network access No
- ✓ Filesystem access No
- ✓ Shell / process execution No
- ✓ Environment & secrets No
- ✓ Dynamic code execution No
From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.
Verified badge
Passed review? Show it. Paste this badge into your README, it links to the public security report.
Reliability & compatibility
Declared compatibility
Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.
We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.
How agent discovery & health will work →About
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-reportgeneration - 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
| Metric | What It Measures | Why It Matters | |--------|-----------------|---------------| | Impressions | How many times content was shown | Top of funnel — are we being seen? | | Engagement rate | (Likes+comments+shares+saves) / impressions | Content quality — are people responding? | | Profile visits | Clicks to profile from content | Brand interest — are people exploring? | | Follows / growth | New followers (net) | Is the audience expanding? | | Link clicks | Clicks on links | Is content driving action? | | Saves / bookmarks | Posts saved for later | Value density — worth keeping? | | Shares / reposts | Content shared by others | Virality potential | | Video retention | % of video watched | Video quality |
Procedure
- Pull metrics per post: impressions, likes, comments, shares, saves, link clicks, profile visits, follows.
- Calculate derived metrics:
- ER% = (likes + comments + shares + saves) / impressions * 100
- Follower growth rate = net new / total followers * 100
- CTR = link clicks / impressions * 100
- Build running database: Track every post with metrics for 90+ days. Store: post ID, platform, date, format, pillar, hook type, metrics.
- Establish baselines:
- Average ER per platform (trailing 30 days)
- Average impressions per post type
- Average weekly follower growth
- "Normal" range for anomaly detection
- 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:
- Metrics are pulled for all posts in the tracking period
- ER%, growth rate, and CTR are calculated
- Anomalies are flagged (overperformers and underperformers)
- Running benchmarks are updated
- 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.
Source & license
This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.
- Author: gokulb20
- Source: gokulb20/Crewm8-Social-Media-Manager-Skill-Graph
- License: MIT
- Homepage: https://crewm8.ai
Install and usage instructions live in the source repository linked above.
Reviews
No reviews yet, be the first.
Write a review
Versions
- v0.1.0 Imported from the upstream source.