Token导航 LogoToken导航TokenDH.com
开发只读github未标认证来源可访问许可证需确认审计通过

algo-social-engagement算法社交参与

Agent Skill

algo-social-engagement 用于处理 GitHub 仓库、Issue、Pull Request 和代码协作信息,适合在 Codex、Claude、Cursor、Gemini CLI 中需要围绕仓库状态、代码变更或协作事项进行整理时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

总安装

356

周安装

15

GitHub Stars

125

下载量

125
CodexClaudeCursorGemini CLI

安装说明

本站只整理中文说明和来源信息,不托管安装包,也不代用户安装。

GitHub

来源数

2

许可证

unknown

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手,先确认命令和权限,再让它执行。

请帮我安装这个 Agent Skill:algo-social-engagement(算法社交参与)
来源仓库:https://github.com/asgard-ai-platform/skills
仓库路径:skills/algo-social-engagement
安装命令:
npx skills add https://github.com/asgard-ai-platform/skills --skill algo-social-engagement
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 npx skills 从第三方来源获取 Skill;本站只展示命令,不托管安装包,也不自动执行。

skills.shnpx skills
npx skills add https://github.com/asgard-ai-platform/skills --skill algo-social-engagement

简介

algo-social-engagement 计算社交媒体互动率,衡量内容与受众的连接强度。

  • 适用于账号绩效对比、行业基准测试或单篇内容影响力评估场景。
  • 公式为(点赞+评论+转发)/分母×100%,分母选择影响结果解读方向。
  • 安装依赖 GitHub 仓库,使用前需确认是否具备社交平台数据接口访问权限。
  • 不涵盖品牌认知或长期影响评估,仅反映短期互动水平。

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

适合场景

01

用户想查找某类 Agent Skill 时

02

需要根据任务场景推荐可安装能力包时

03

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明,方便继续核验

能力 4

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用;具体调用方式请以来源页面和 README 为准。

平台分布

Codex

35%
按下载量换算44

Claude

30.17%
按下载量换算38

Cursor

19.29%
按下载量换算24

Gemini CLI

10.57%
按下载量换算13

安全审计

Gen Agent Trust Hub

通过

Socket

通过

Snyk

通过

权限和风险

只读

该 Skill 主要提供规则、说明或参考内容,本身偏只读;真正读写文件、联网或执行命令仍取决于宿主 Agent 的任务。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源,正式发布前建议补源仓库或其他目录站核验。

来源信息

继续浏览同类 Skills