Token导航 LogoToken导航

Agent Skill · 研究检索

keyapi-twitter-content-analytics(keyapi Twitter 内容分析)

用于辅助数据整理、表格处理、CSV/Excel 分析、指标计算和图表准备。它适合让 Agent 清洗字段、汇总数据、发现异常、生成统计口径或把分析结果转成可读说明。使用时需要确认数据来源、字段含义和时间范围,避免把样本数据当全量事实;涉及敏感数据、导出文件或批量写回时,应先确认权限和脱敏边界。

keyapi-twitter-content-analytics 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为接触敏感数据;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 35,589。

总安装 2,060周安装 85GitHub Stars 公开资料未说明下载 673核验 2026-05-01

安装说明

本站只整理中文说明,不托管安装包,也不代用户安装。
GitHub
许可证
MIT-0
版本
1.0.0

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:keyapi-twitter-content-analytics(keyapi Twitter 内容分析)
来源仓库:https://github.com/lycici/keyapi-twitter-content-analytics
安装命令:
openclaw skills install keyapi-twitter-content-analytics
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install keyapi-twitter-content-analytics

这个 Skill 是做什么的

研究检索类 Skill 主要解决「找资料、核对事实、把来源整理清楚」的问题,通常会让助手先检索再总结。

用于大规模检索 Twitter/X 用户推文、评论、回复及媒体内容,监控热门话题。适合在 OpenClaw 中分析舆论走向、追踪品牌声量或挖掘传播节点时使用。支持跨内容类型搜索与实时流数据整理,输出结构化日志与统计报表。

安装命令:openclaw skills install keyapi-twitter-content-analytics。需注意平台 API 调用频次限制,避免服务中断或数据丢失。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

    公开资料标注支持 OpenClaw;先确认自己用的是其中之一,再按对应工具的 Skills 目录放置。

  2. 2

    拿到安装命令

    可以直接复制的命令是 openclaw skills install keyapi-twitter-content-analytics;命令里的占位符换成自己的路径或密钥再执行。

  3. 3

    安装后重启宿主

    命令执行完要完全退出宿主工具再打开,让新装的 Skill 被重新扫描到,否则列表里可能看不到。

  4. 4

    按最小权限试用

    它需要接触敏感数据,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

keyapi-twitter-content-analytics 怎么安装?

在终端执行 openclaw skills install keyapi-twitter-content-analytics。装完完全退出宿主工具再打开,让它重新扫描本地 Skill。

keyapi-twitter-content-analytics 支持哪些 AI 工具?

公开资料标注支持 OpenClaw。其他工具只要能读取本地 Skill 目录,一般也能手动放进去,但要自己确认触发方式是否一致。

keyapi-twitter-content-analytics 需要什么权限?

权限级别是接触敏感数据。该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

keyapi-twitter-content-analytics 是免费的吗?

来源标注的许可证是 MIT-0。本站不代收任何费用,也不托管安装包;能否商用、要不要署名,以许可证原文为准。

keyapi-twitter-content-analytics 用的人多吗?

公开数据是累计安装 2,060 次,近一周安装 85 次,下载 673 次。这些数字来自第三方目录统计,只能当作热度参考,不代表质量或安全性。

keyapi-twitter-content-analytics 安全吗?

第三方扫描有提醒项,说明存在需要人工确认的行为。安装前请打开源码看清它读了什么、联网到哪里。

值得选的地方和要先想清楚的地方

值得选的地方

  • 专注 OpenClaw 一种宿主,触发方式和使用习惯不用来回切换。
  • 许可证明确为 MIT-0,商用和分发边界好判断。

先想清楚的地方

  • 需要接触敏感数据,装到常用环境前要先评估影响面。
  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

  • 已经在用 OpenClaw,想直接扩展它能力的人。
  • 需要处理研究检索类任务、又不想每次都手写提示词的人。

不太适合

  • 环境里有大量密钥、凭证,不方便给第三方 Skill 读取的人。
  • 需要厂商级技术支持和 SLA 的生产系统。

研究检索类 Skill 对比

6 个同类
Skill总安装GitHub 星权限许可证扫描
find-skills

寻找技能 · Codex、Claude

31,199,81316,486操作浏览器MIT有提醒
self-improving-agent

自我改进 Agent · OpenClaw

16,464,0023,396接触敏感数据MIT-0通过
soultrace

灵魂追踪 · Codex、Claude

7,588,94412需要联网未明确有提醒
self-improving

自我完善 · OpenClaw

6,829,2841,046需要联网MIT-0通过
microsoft-foundry

微软代工厂 · Codex、Claude

6,614,144764调用外部服务未明确有提醒
keyapi-twitter-content-analytics

keyapi Twitter 内容分析 · 本页

2,060—接触敏感数据MIT-0有提醒

按安装量取同分类前几名;数字来自第三方目录统计,只作热度参考,不代表质量结论。

SKILL.md 原文

name
keyapi-twitter-content-analytics
description
Explore and analyze Twitter/X content at scale — retrieve user profiles, tweets, comments, replies, media, search across content types, monitor trending topics, and analyze follower/following networks.
metadata
{"openclaw":{"requires":{"env":["KEYAPI_TOKEN"],"bins":["node"]},"primaryEnv":"KEYAPI_TOKEN","emoji":"🐦"}}
author
KeyAPI
license
MIT
repository
https://github.com/EchoSell/keyapi-skills

keyapi-twitter-content-analytics

Explore and analyze Twitter/X content at scale — from user profiles and tweet threads to search, trending topics, and social graph analysis.

This skill provides comprehensive Twitter/X intelligence using the KeyAPI MCP service. It enables detailed tweet inspection, user profile retrieval, comment and reply thread analysis, media library enumeration, multi-type search (Top, Latest, Media, People, Lists), trending topic monitoring across countries, and follower/following network exploration — all through a cache-first workflow.

Use this skill when you need to:

  • Retrieve full tweet details including engagement metrics, media, and quoted content
  • Fetch user profiles with follower counts, bio, verification status, and account metadata
  • Analyze a user's tweet timeline, replies, and media library
  • Read comment threads under any tweet with pagination support
  • Search Twitter by keyword across multiple result types (Top, Latest, Media, People, Lists)
  • Monitor trending topics and hashtags by country or globally
  • Explore social graphs — analyze who a user follows and who follows them
  • Identify users who retweeted a specific tweet

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Prerequisites

RequirementDetails
KEYAPI_TOKENA valid API token from keyapi.ai. If you don't have one, register at the site to obtain your free token. Set it as an environment variable: export KEYAPI_TOKEN=your_token_here
Node.jsv18 or higher
DependenciesRun npm install in the skill directory to install @modelcontextprotocol/sdk

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


MCP Server Configuration

All tool calls in this skill target the KeyAPI Twitter MCP server:

Server URL : https://mcp.keyapi.ai/twitter/mcp
Auth Header: Authorization: Bearer $KEYAPI_TOKEN

Setup (one-time):

# 1. Install dependencies
npm install

# 2. Set your API token (get one free at https://keyapi.ai/)
export KEYAPI_TOKEN=your_token_here

# 3. List all available tools to verify the connection
node scripts/run.js --platform twitter --list-tools

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Analysis Scenarios

Tweet & User Nodes

User NeedNode(s)Best For
Full tweet details (metrics, media, quoted content)get_single_tweet_dataTweet audit, engagement snapshot — requires tweet_id from URL
User profile with bio, follower counts, verificationget_user_profileProfile overview — accepts screen_name or rest_id
User's tweet timelineget_user_postContent inventory, posting cadence analysis — accepts screen_name or rest_id
User's tweet repliesget_user_tweet_repliesReply activity, conversation participation — requires screen_name only
User's media library (photos/videos)get_user_mediaVisual content audit — requires screen_name only

Comment & Engagement Nodes

User NeedNode(s)Best For
Comments under a tweetget_commentsAudience sentiment, comment volume analysis
Users who retweeted a tweetretweet_user_listAmplification analysis, retweet network mapping

Search & Discovery Nodes

User NeedNode(s)Best For
Search by keyword (multi-type)searchBroad discovery — filter by Top, Latest, Media, People, Lists
Trending topics by countrytrendingReal-time trend monitoring — supports 50+ countries

Social Graph Nodes

User NeedNode(s)Best For
Users a profile is followinguser_followingsNetwork affinity, brand partnership signals — requires screen_name only
Users following a profileuser_followersAudience sampling, follower demographics — requires screen_name only

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Workflow

Step 1 — Identify the Analysis Objective and Select Nodes

Clarify the research goal and map it to one or more nodes. Common patterns:

  • Tweet analysis: Extract tweet_id from URL → get_single_tweet_data → deepen with get_comments + retweet_user_list.
  • User profile audit: Use get_user_profile with screen_name → layer get_user_post + get_user_tweet_replies + get_user_media.
  • Search research: Use search with keyword and search_type filter → paginate with cursor for more results.
  • Trend monitoring: Use trending with country parameter → cross-reference with search for content depth.
  • Social graph analysis: Use user_followings + user_followers with screen_name → paginate with cursor.
User identification Most endpoints accept either screen_name (e.g., elonmusk) or rest_id (numeric user ID, e.g., 44196397) — pass one, not both. - get_user_profile and get_user_post accept both screen_name and rest_id. - get_user_tweet_replies, get_user_media, user_followings, and user_followers require screen_name only — no rest_id option.
Tweet ID extraction Extract the tweet ID from the URL: - https://x.com/elonmusk/status/1808168603721650364 → 1808168603721650364

Step 2 — Retrieve API Schema

Before calling any node, inspect its input schema to confirm required parameters and available options:

node scripts/run.js --platform twitter --schema <tool_name>

# Examples
node scripts/run.js --platform twitter --schema get_single_tweet_data
node scripts/run.js --platform twitter --schema search

Step 3 — Call APIs and Cache Results Locally

Execute tool calls and persist responses to the local cache.

Calling a tool:

node scripts/run.js --platform twitter --tool <tool_name> \
  --params '<json_args>' --pretty

# Skip cache for fresh results
node scripts/run.js --platform twitter --tool <tool_name> \
  --params '<json_args>' --no-cache --pretty

Example — get tweet details:

node scripts/run.js --platform twitter --tool get_single_tweet_data \
  --params '{"tweet_id":"1808168603721650364"}' --pretty

Example — get user profile:

node scripts/run.js --platform twitter --tool get_user_profile \
  --params '{"screen_name":"elonmusk"}' --pretty

Example — get user tweets (first page):

node scripts/run.js --platform twitter --tool get_user_post \
  --params '{"screen_name":"elonmusk"}' --pretty

Example — paginate to next page:

node scripts/run.js --platform twitter --tool get_user_post \
  --params '{"screen_name":"elonmusk","cursor":"<next_cursor_from_previous_response>"}' --pretty

Example — get comments under a tweet:

node scripts/run.js --platform twitter --tool get_comments \
  --params '{"tweet_id":"1808168603721650364"}' --pretty

Example — search by keyword (Top results):

node scripts/run.js --platform twitter --tool search \
  --params '{"keyword":"AI","search_type":"Top"}' --pretty

Example — search for latest tweets:

node scripts/run.js --platform twitter --tool search \
  --params '{"keyword":"ChatGPT","search_type":"Latest"}' --pretty

Example — get trending topics (United States):

node scripts/run.js --platform twitter --tool trending \
  --params '{"country":"UnitedStates"}' --pretty

Example — get trending topics (Japan):

node scripts/run.js --platform twitter --tool trending \
  --params '{"country":"Japan"}' --pretty

Example — get user's followings:

node scripts/run.js --platform twitter --tool user_followings \
  --params '{"screen_name":"elonmusk"}' --pretty

Example — get user's followers:

node scripts/run.js --platform twitter --tool user_followers \
  --params '{"screen_name":"elonmusk"}' --pretty

Example — get retweet user list:

node scripts/run.js --platform twitter --tool retweet_user_list \
  --params '{"tweet_id":"1835124037934367098"}' --pretty

Pagination:

All paginated endpoints use cursor from the next_cursor field in the previous response.

EndpointPagination parameterNotes
get_user_post, search, get_comments, get_user_tweet_replies, get_user_media, retweet_user_list, user_followings, user_followerscursorPass next_cursor value from previous response
get_single_tweet_data, get_user_profile, trending—Single-call; no pagination

Cache directory structure:

.keyapi-cache/
└── YYYY-MM-DD/
    ├── get_single_tweet_data/
    │   └── {params_hash}.json
    ├── get_user_profile/
    │   └── {params_hash}.json
    ├── get_user_post/
    │   └── {params_hash}.json
    ├── search/
    │   └── {params_hash}.json
    ├── get_comments/
    │   └── {params_hash}.json
    ├── get_user_tweet_replies/
    │   └── {params_hash}.json
    ├── get_user_media/
    │   └── {params_hash}.json
    ├── retweet_user_list/
    │   └── {params_hash}.json
    ├── trending/
    │   └── {params_hash}.json
    ├── user_followings/
    │   └── {params_hash}.json
    └── user_followers/
        └── {params_hash}.json

Cache-first policy:

Before every API call, check whether a cached result already exists. If valid, load from disk and skip the API call.

Step 4 — Synthesize and Report Findings

For tweet analysis:

  1. Tweet Overview — Text content, author, publish date, view count, like count, retweet count, reply count, quote count.
  2. Engagement Analysis — Like-to-view ratio, retweet amplification, comment depth.
  3. Media & Links — Attached images/videos, external links, quoted tweets.
  4. Comment Insights — Top comment themes, sentiment signals, key discussion points.
  5. Retweet Network — Who amplified the tweet, account types, reach estimation.

For user analysis:

  1. Profile Overview — Screen name, display name, bio, follower count, following count, tweet count, verification status, account creation date.
  2. Content Patterns — Posting frequency, media usage, reply activity, content themes.
  3. Social Graph — Follower-to-following ratio, notable followings/followers where available.
  4. Engagement Quality — Average engagement per tweet, reply rate, retweet rate.

For search / discovery:

  1. Search Results Overview — Result count, top tweets/users, engagement distribution.
  2. Trending Topics — Current trending hashtags and topics by country, volume indicators.
  3. Content Themes — Common topics, hashtags, and discussion patterns.

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Common Rules

RuleDetail
User identificationget_user_profile and get_user_post accept screen_name or rest_id. get_user_tweet_replies, get_user_media, user_followings, and user_followers require screen_name only.
Tweet ID extractionExtract from URL: x.com/user/status/TWEET_ID or twitter.com/user/status/TWEET_ID.
Search typessearch supports: Top (default), Latest, Media, People, Lists.
Trending countriestrending supports 50+ countries including: UnitedStates, China, India, Japan, Russia, Germany, UnitedKingdom, France, Brazil, Canada, Australia, SouthKorea, Mexico, Spain, Italy, Turkey, Indonesia, SaudiArabia, Egypt, Argentina, Philippines, Singapore, and more. See schema for full list.
PaginationAll paginated endpoints use cursor from the next_cursor field in the previous response.
Success checkcode = 0 → success. Any other value → failure. Always check the response code before processing data.
Retry on 500If code = 500, retry the identical request up to 3 times with a 2–3 second pause between attempts before reporting the error.
Cache firstAlways check the local .keyapi-cache/ directory before issuing a live API call.

author: KeyAPI license: MIT repository: https://github.com/EchoSell/keyapi-skills


Error Handling

CodeMeaningAction
0SuccessContinue workflow normally
400Bad request — invalid or missing parametersValidate input against the tool schema; check tweet_id format, screen_name vs rest_id requirements, and search type values
401Unauthorized — token missing or expiredConfirm KEYAPI_TOKEN is set correctly; visit keyapi.ai to renew
403Forbidden — plan quota exceeded or feature restrictedReview plan limits at keyapi.ai
404Resource not found — tweet or user may be deleted, suspended, or privateVerify the tweet ID or screen name; the content may no longer be available
429Rate limit exceededWait 60 seconds, then retry
500Internal server errorRetry up to 3 times with a 2–3 second pause; if it persists, log the full request and response and skip this node
Other non-0Unexpected errorLog the full response body and surface the error message to the user

平台分布

OpenClaw

74.74%
按下载量换算503

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

可疑

权限和风险

接触敏感数据

该 Skill 可能接触密钥、Token、环境变量或敏感配置,应进入高风险复核队列,默认不自动发布。

安装前确认

本站仅展示第三方公开信息,不托管安装包,不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。来源安全扫描存在提醒或未通过项,安装前请自行复核。目前只有一个公开来源,建议同时核对源仓库。

继续浏览同类 Skills