← Back to Skills Marketplace
AI Trend Monitor
by
wuyuyang001-oss
· GitHub ↗
· v1.0.0
646
Downloads
2
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install ai-trend-monitor
Description
监控 GitHub、Reddit、Twitter 等多渠道 AI 趋势与重大新闻,支持实时推送和每日定时汇总飞书卡片。
README (SKILL.md)
AI Trend Monitor
监控 AI 市场趋势和技术前沿,支持实时重大新闻推送 + 定时汇总推送。
功能
- 多渠道监控:GitHub、Reddit、Twitter/X、小红书、新闻
- 智能 URL 提取:自动提取具体帖子/文章 URL(非首页)
- 重大新闻实时推送:检测到重大新闻立即推送
- 定时汇总:每天 9:00、13:00、19:00 定时推送
- 飞书卡片格式:分渠道表格,完整文本,可跳转链接
安装
# 克隆到 skills 目录
git clone \x3Crepo-url> ~/.openclaw/skills/ai_trend_monitor
# 安装依赖
cd ~/.openclaw/skills/ai_trend_monitor
npm install
配置
编辑 config.js:
module.exports = {
// 飞书 Webhook
webhooks: {
market: 'https://open.feishu.cn/open-apis/bot/v2/hook/xxx',
tech: 'https://open.feishu.cn/open-apis/bot/v2/hook/xxx'
},
// 监控渠道
channels: ['GitHub', 'Reddit', 'Twitter', '小红书', '新闻'],
// 推送时间
schedule: {
morning: '0 9 * * *', // 9:00
noon: '0 13 * * *', // 13:00
evening: '0 19 * * *' // 19:00
},
// 重大新闻判定标准
majorNewsCriteria: {
funding: 100000000, // 1亿美元
stockChange: 5, // 股价涨跌5%
keyPeople: ['Sam Altman', 'Elon Musk', 'Andrej Karpathy'],
keyCompanies: ['OpenAI', 'Google', 'Anthropic', 'Meta', 'xAI']
}
};
使用
手动运行
node ai_trend_monitor.js
定时任务
使用 OpenClaw cron:
{
"jobs": [
{
"name": "ai-trend-morning",
"schedule": "0 9 * * *",
"command": "node ~/.openclaw/skills/ai_trend_monitor/ai_trend_monitor.js"
},
{
"name": "ai-trend-noon",
"schedule": "0 13 * * *",
"command": "node ~/.openclaw/skills/ai_trend_monitor/ai_trend_monitor.js"
},
{
"name": "ai-trend-evening",
"schedule": "0 19 * * *",
"command": "node ~/.openclaw/skills/ai_trend_monitor/ai_trend_monitor.js"
}
]
}
消息格式
飞书卡片消息,按渠道分组:
| 渠道 | 标题 | 概述 | 时间 | 影响分析 | 链接 |
|---|---|---|---|---|---|
| GitHub | xxx | xxx | 2026-02-19 08:00 | xxx | [查看] |
| xxx | xxx | 2026-02-19 10:30 | xxx | [查看] |
依赖
- Node.js >= 18
- OpenClaw CLI(用于定时任务)
- kimi_search API(用于实时搜索)
版本
v1.0.0
作者
小赵
License
MIT
Usage Guidance
This skill appears to perform the described monitoring and Feishu webhook pushes, but there are gaps you should resolve before installing: 1) Inspect the upstream repository referenced by SKILL.md (the <repo-url>) and review its package.json and npm dependencies before running npm install. 2) Confirm where the kimi_search API is called and whether it requires an API key—the manifest doesn't declare any required credentials. 3) Decide whether to supply webhook URLs via config.js or environment variables; verify the code will only send to endpoints you control. 4) Because fetch is used to POST cards and the code may call external search endpoints, only run this skill in an environment where network pushes to configured webhooks are acceptable. If you cannot locate a trusted repository or package manifest, treat the package as untrusted and do not run npm install or the script.
Capability Analysis
Type: OpenClaw Skill
Name: ai-trend-monitor
Version: 1.0.0
The OpenClaw skill 'ai-trend-monitor' is designed to monitor AI trends and push notifications to Feishu webhooks. The `ai_trend_monitor.js` script uses mocked data for its search functionality, meaning it does not currently make external API calls for content retrieval. It sends formatted messages to user-configured Feishu webhooks, which aligns with its stated purpose and does not constitute unauthorized data exfiltration. The `SKILL.md` provides standard installation and usage instructions, including setting up cron jobs, without any evidence of prompt injection attempts against the AI agent or instructions for malicious actions. No obfuscation, persistence mechanisms, or other indicators of malicious intent were found in the provided files.
Capability Assessment
Purpose & Capability
The stated purpose (monitor GitHub/Reddit/Twitter/小红书/news and push Feishu cards) is implemented in the JavaScript. However the registry metadata claims no required env/config, while the code expects webhook URLs (via config.js and process.env.WEBHOOK_*) and mentions an external kimi_search API. The presence of network push behavior (Feishu webhooks, external search API) is coherent with the purpose, but the packaging/config declarations are inconsistent.
Instruction Scope
SKILL.md tells the user to clone a repo and run npm install, edit config.js to add Feishu webhooks, and schedule the node script. The code does network I/O (fetch to webhook URLs) and would call an external search API in real deployment. SKILL.md and registry metadata do not declare the environment variables the code reads (e.g., process.env.WEBHOOK_MARKET/WEBHOOK_TECH) nor any API key for kimi_search, which is a scope mismatch: instructions assume external endpoints and credentials but the manifest did not declare them.
Install Mechanism
There is no install spec in the registry (instruction-only), but SKILL.md instructs to run npm install. The provided file list contains no package.json or package-lock, so npm install as documented has no local manifest in this package — this is an inconsistency that could lead users to clone an external repository (SKILL.md uses a placeholder <repo-url>). The code itself is not obfuscated and uses standard Node APIs, but missing package metadata is a red flag requiring the user to inspect the upstream repository before running npm install.
Credentials
Registry metadata lists no required environment variables or primary credential, but the code reads process.env.WEBHOOK_MARKET and process.env.WEBHOOK_TECH (with placeholder defaults) and SKILL.md instructs editing config.js with webhook URLs. The skill also references a third-party 'kimi_search' API (likely requiring credentials) but does not declare or document required API keys. Asking a user to configure webhook URLs is expected, but the lack of declared env/config requirements in the manifest is inconsistent and may lead to silent network calls to endpoints set via env or config.
Persistence & Privilege
The skill does not request always:true, does not attempt to modify other skills, and its recommended installation (clone into ~/.openclaw/skills and cron entries) is standard for a local skill. Autonomous invocation is allowed by platform default — combined with the other concerns this increases blast radius but is not itself unusual.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install ai-trend-monitor - After installation, invoke the skill by name or use
/ai-trend-monitor - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
AI Trend Monitor v1.0.0 initial release
- Monitors AI trends and news across GitHub, Reddit, Twitter/X, 小红书, and news sources.
- Sends real-time push notifications for major news and scheduled digests three times daily (9:00, 13:00, 19:00).
- Automatically extracts detailed URLs (not just homepages) for posts and articles.
- Groups notifications by channel and formats them as Feishu cards with direct links.
- Major news determined by configurable criteria (e.g., funding events, stock changes, key people/companies).
- Supports manual runs and automated scheduling via OpenClaw cron jobs.
Metadata
Frequently Asked Questions
What is AI Trend Monitor?
监控 GitHub、Reddit、Twitter 等多渠道 AI 趋势与重大新闻,支持实时推送和每日定时汇总飞书卡片。 It is an AI Agent Skill for Claude Code / OpenClaw, with 646 downloads so far.
How do I install AI Trend Monitor?
Run "/install ai-trend-monitor" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is AI Trend Monitor free?
Yes, AI Trend Monitor is completely free (open-source). You can download, install and use it at no cost.
Which platforms does AI Trend Monitor support?
AI Trend Monitor is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created AI Trend Monitor?
It is built and maintained by wuyuyang001-oss (@wuyuyang001-oss); the current version is v1.0.0.
More Skills