agentleFS
asgard-ai-platformasgard-ai-platform/skills/algo-social-engagement/SKILL.md

algo-social-engagement

Skill238 starsChanged 6 months agoMITView on GitHub

Calculate and benchmark social media engagement rates across platforms and variants. Use this skill when the user needs to compute engagement metrics, compare performance across accounts or posts, or set engagement benchmarks — even if they say 'what is my engagement rate', 'benchmark engagement', or 'social media KPIs'.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    When evaluating influence holistically (use influence measurement)

    line 23
  2. Distinctive:

    When modeling content spread dynamics (use virality models)

    line 24
  3. Distinctive:

    Follower-based ER is noisy: Not all followers see each post (reach < followers).

    line 82

≈ “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

Engagement Rate Calculation

Overview

Engagement rate measures audience interaction relative to reach or audience size. Formula: (reactions + comments + shares) / denominator × 100%. The denominator choice (reach, impressions, followers) significantly affects the result. Computes in O(n) per post set.

When to Use

Trigger conditions:

  • Computing engagement metrics for social media reporting
  • Benchmarking account or post performance against industry averages
  • Comparing content performance across posts or accounts

When NOT to use:

  • When evaluating influence holistically (use influence measurement)
  • When modeling content spread dynamics (use virality models)

Algorithm

IRON LAW: Engagement Rate Denominator MATTERS
By reach, by impressions, and by followers produce DIFFERENT numbers:
- ER by Reach = engagements / reach × 100% (most accurate, requires analytics access)
- ER by Impressions = engagements / impressions × 100% (always lower than by reach)
- ER by Followers = engagements / followers × 100% (public data, but inflated by non-reaching followers)
ALWAYS specify which variant when reporting or comparing.

Phase 1: Input Validation

Collect per post: likes, comments, shares/retweets, saves (platform-specific), reach or impressions or follower count. Gate: Consistent denominator across all posts being compared.

Phase 2: Core Algorithm

  1. Sum engagements per post: likes + comments + shares (+ saves, clicks if available)
  2. Weight engagements if desired: share=3×, comment=2×, like=1× (shares indicate higher commitment)
  3. Divide by chosen denominator (reach preferred, followers as fallback)
  4. Compute: per-post ER, average ER across posts, median ER, ER trend over time

Phase 3: Verification

Compare against platform benchmarks. Flag anomalies (ER > 20% likely data error or viral outlier). Gate: Results within plausible range for platform.

Phase 4: Output

Return engagement metrics with benchmarking context.

Output Format

{
  "metrics": {"avg_er_by_reach": 3.2, "avg_er_by_followers": 1.8, "median_er": 2.9, "top_post_er": 8.5},
  "benchmark": {"platform": "instagram", "industry": "fashion", "benchmark_er": 2.5, "percentile": 72},
  "metadata": {"posts_analyzed": 30, "period": "2025-Q1", "denominator": "reach"}
}

Examples

Sample I/O

Input: Post: 150 likes, 20 comments, 5 shares, reach=5000 Expected: ER by reach = (150+20+5)/5000 × 100% = 3.5%

Edge Cases

InputExpectedWhy
Reach = 0Undefined, skip postCan't divide by zero
Boosted/paid postSeparate from organicPaid reach inflates denominator, deflates ER
Viral outlier (10x avg)Flag, analyze separatelySkews averages

Gotchas

  • Platform algorithm changes: Instagram's algorithm shifts regularly. Historical ER benchmarks become outdated. Use rolling 90-day benchmarks.
  • Vanity metric trap: High ER doesn't mean business impact. 1000 likes on a meme ≠ 10 link clicks on a product post. Track meaningful engagements.
  • Story/Reel metrics differ: Story engagement (taps, replies) and Reel engagement (plays, shares) need different formulas than feed posts. Don't mix.
  • Follower-based ER is noisy: Not all followers see each post (reach < followers). ER by followers underestimates true engagement among those who saw the post.
  • Comparing across account sizes: Smaller accounts naturally have higher ER by followers. Normalize or segment by account size for fair comparison.

References

  • For platform-specific benchmark data, see references/platform-benchmarks.md
  • For weighted engagement scoring models, see references/weighted-engagement.md

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.