Token导航 LogoToken导航

Agent Skill · 研究检索

content-research-mcbai(内容研究麦克拜)

用于辅助文档、README、Markdown、说明文和内容稿件的整理与改写。它适合让 Agent 提炼结构、补齐章节、统一术语、检查链接或把零散材料整理成可读文档。使用时应保留项目已有事实、命令和路径,不要把未确认的信息写成确定结论;涉及对外文案时,还需要控制语气,避免过度营销或夸大能力。

content-research-mcbai 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为调用外部服务;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 30,911。

总安装 2,796周安装 112GitHub Stars 公开资料未说明下载 905核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

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

命令行安装

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

ClawHubOpenClaw
openclaw skills install content-research-mcbai

这个 Skill 是做什么的

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

通过网络搜索发现任意主题的热门内容与趋势来源。支持查找文章、新闻与博客等多样化信息源。适用于选题调研、竞品分析与背景资料收集。帮助用户快速定位高质量内容,避免无效检索。输出包含来源链接与摘要的结构化报告。content-research-mcbai 属于研究检索类 Skill,可作为该场景下的辅助能力补充。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要调用外部服务,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

content-research-mcbai 怎么安装?

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

content-research-mcbai 支持哪些 AI 工具?

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

content-research-mcbai 需要什么权限?

权限级别是调用外部服务。该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

content-research-mcbai 是免费的吗?

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

content-research-mcbai 用的人多吗?

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

content-research-mcbai 安全吗?

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

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

值得选的地方

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

先想清楚的地方

  • 第三方扫描存在提醒项或未通过项,需要人工逐条确认。
  • 第三方目录整理,版本更新和行为细节以来源仓库为准。

适不适合你

更适合

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

不太适合

  • 需要厂商级技术支持和 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调用外部服务未明确有提醒
content-research-mcbai

内容研究麦克拜 · 本页

2,796—调用外部服务MIT-0有提醒

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

SKILL.md 原文

name
content-research
description
Research and discover trending content sources for any topic using web search. Use this skill whenever the user wants to find articles, news, blog posts, or trending content about a specific topic for content creation, LinkedIn posts, social media writing, or content curation. Also trigger when the user mentions "research topic", "find articles about", "trending news", "content sources", "search for content", or wants to gather data/sources before writing posts.

Content Research Skill

Installation

npx clawhub@latest install content-research-mcbai

Search the web for trending articles, news, and content sources on any topic. This skill powers the MCB AI content research pipeline — finding, filtering, scoring, and organizing source material for content creation.

Search Strategy: Brave + Tavily Dual-Engine

This skill uses TWO search providers in parallel for maximum coverage:

  • Brave Search — via web_search tool (built-in OpenClaw tool)
  • Tavily — via direct API call using TAVILY_API_KEY from ~/.openclaw/.env

Tavily API Call

POST https://api.tavily.com/search
Headers: Content-Type: application/json
Body:
{
  "api_key": "<TAVILY_API_KEY>",
  "query": "<query>",
  "search_depth": "advanced",
  "include_answer": false,
  "include_raw_content": false,
  "max_results": 10,
  "topic": "news"   // use "general" for non-news searches
}

Run Tavily via exec with PowerShell:

$body = @{
  api_key = $env:TAVILY_API_KEY
  query = "<query>"
  search_depth = "advanced"
  include_answer = $false
  include_raw_content = $false
  max_results = 10
  topic = "news"
} | ConvertTo-Json

Invoke-RestMethod -Uri "https://api.tavily.com/search" -Method Post -ContentType "application/json" -Body $body

Fallback Logic

  • Run Brave (web_search) and Tavily in parallel
  • If Brave fails → use Tavily results only
  • If Tavily fails → use Brave results only
  • If both succeed → merge and deduplicate by URL

When to Use

  • User wants to research a topic before writing content
  • User needs to find recent articles, news, or data about a subject
  • User wants to discover trending content sources for LinkedIn/social media
  • User needs to curate sources for a toplist, POV, case study, or how-to post

Core Workflow

Step 1: Understand the Research Request

Extract from the user's message:

  1. Topic — the subject to research (required)
  2. Source filter — where to search (default: all sources)

- all — All web sources - news — News publications only - linkedin — LinkedIn posts/articles (append site:linkedin.com) - youtube — YouTube videos (append site:youtube.com) - blogs — Blog posts and articles (append blog OR article OR guide)

  1. Freshness — how recent (default: past month for web, past week for news)
  2. Count — how many results to return (default: 10-15)

If the user doesn't specify these, use sensible defaults and mention what you chose.

Step 2: Execute Dual Search (Brave + Tavily)

Run BOTH providers. Each provider runs TWO queries when possible.

Brave Search (web_search tool)

Query 1 — Web:

Query: {topic} {source_filter_query}
count: 10
freshness: month

Query 2 — News:

Query: {topic} news
count: 10
freshness: week
Tavily Search (exec PowerShell)

Query 1 — General:

$env:TAVILY_API_KEY = (Get-Content "$env:USERPROFILE\.openclaw\.env" | Select-String "TAVILY_API_KEY" | ForEach-Object { $_ -replace "TAVILY_API_KEY=", "" })

$body = @{
  api_key = $env:TAVILY_API_KEY.Trim()
  query = "{topic}"
  search_depth = "advanced"
  include_answer = $false
  include_raw_content = $false
  max_results = 10
  topic = "general"
} | ConvertTo-Json

Invoke-RestMethod -Uri "https://api.tavily.com/search" -Method Post -ContentType "application/json" -Body $body

Query 2 — News:

# Same as above but topic = "news"

Step 3: Merge and Deduplicate

  1. Collect all results from Brave (web + news) and Tavily (general + news)
  2. Deduplicate by URL — keep one copy per URL, prefer Tavily version (richer content)
  3. Sort by relevance:

- News articles first (most time-sensitive) - Then by freshness (most recent first)

  1. Limit to requested count (default 15)
  2. Label source engine in metadata: [Brave] or [Tavily]

Step 4: Process and Organize Results

For each result, extract and structure:

Article:
  - Title: [article title]
  - Source: [publication/website name]
  - URL: [full URL]
  - Date: [relative date, e.g. "2 hours ago", "3 days ago"]
  - Summary: [description/snippet from search]
  - Type: [News / Blog / Report / Video / LinkedIn]
  - Tag: [auto-detected tag, see Tag Rules below]
  - Engine: [Brave / Tavily / Both]
Source Name Extraction

Clean the hostname to a readable name:

  • Remove www. prefix
  • Remove .com, .org, .net, .io, .co suffixes
  • Map known domains: techcrunch → TechCrunch, crunchbase → Crunchbase, forbes → Forbes, bloomberg → Bloomberg, reuters → Reuters, etc.
Auto-Tag Rules

Scan title + summary and apply the FIRST matching tag:

TagPattern Keywords
Fundingfund, raise, round, series A-C, seed, valuation, invest, VC, venture
AIai, artificial intelligence, machine learning, LLM, GPT, Claude, OpenAI
SaaSsaas, software as a service, subscription, ARR, MRR
Toolstool, platform, app, software, stack, framework
Trendstrend, report, survey, data, statistic, forecast, prediction
Startupstartup, founder, launch, accelerator, incubator, YC
Growthgrowth, marketing, GTM, acquisition, retention, conversion

Step 5: Present Results

Present the organized results in a clear, scannable format:

## Research Results: "{topic}"
Found {N} articles from {sources_count} sources
Sources: Brave ({brave_count}) + Tavily ({tavily_count}) → merged {total} unique

### 📰 News
1. **{title}** — {source} ({date}) [{engine}]
   {summary}
   🏷️ {tag} | 🔗 {url}

### 📝 Articles & Blogs
2. **{title}** — {source} ({date}) [{engine}]
   {summary}
   🏷️ {tag} | 🔗 {url}

...

Then ask the user which articles they want to use for content creation. If the user wants to proceed to writing, hand off to the content-writer skill with the selected articles.

Output Format

Always provide results as a numbered list with:

  • Clear title
  • Source name and date
  • Engine label [Brave] or [Tavily]
  • Brief summary (1-2 lines)
  • Auto-detected tag
  • Source URL

Tips for Better Research

  • For funding/startup topics: search for specific company names + "funding" or "series"
  • For trend pieces: include year/quarter in the search (e.g., "AI trends Q1 2026")
  • For competitive analysis: search for specific company + "vs" or "alternative"
  • For LinkedIn content: recent news performs best (past 1-2 weeks)
  • Combine multiple source types for richer content
  • Tavily search_depth: "advanced" digs deeper — use for complex topics
  • If one engine returns fewer results than expected, note it in the summary

Integration with Content Writer

After research, the user typically selects articles and moves to writing. Pass the selected articles to the content-writer skill in this format:

{
  "articles": [
    {
      "title": "Article title",
      "source": "Publication name",
      "url": "https://...",
      "date": "2 days ago",
      "summary": "Brief description",
      "tag": "AI",
      "engine": "Tavily"
    }
  ]
}

See references/source-filters.md for detailed source filter configurations.

平台分布

OpenClaw

72.03%
按下载量换算652

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

通过

权限和风险

调用外部服务

该 Skill 可能调用第三方服务、云服务或外部模型 API,使用前需要确认账号、额度、数据发送范围和服务条款。

安装前确认

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

继续浏览同类 Skills