Token导航 LogoToken导航

Agent Skill · 研究检索

rumor-buster(谣言破坏者)

rumor-buster 用于查找、检索和筛选相关信息,适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态,以及是否会触发联网、命令执行或文件读写。

rumor-buster 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为执行命令;许可证为 MIT-0,第三方扫描有提醒项,按安装量在研究检索类的 73,675 个 Skill 里排第 29,492。

总安装 3,045周安装 122GitHub Stars 公开资料未说明下载 986核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:rumor-buster(谣言破坏者)
来源仓库:https://github.com/harry720320/rumor-buster
安装命令:
openclaw skills install rumor-buster
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install rumor-buster

这个 Skill 是做什么的

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

rumor-buster 采用中英文双引擎交叉验证,核查新闻与声明的真实性。适合需要快速溯源、识别虚假信息或比对多方信源的场景。支持声明解析、来源可信度评分与传播路径追踪。安装命令:openclaw skills install rumor-buster;依赖外部事实数据库。

结果受数据覆盖与时延影响,不能保证 100% 准确。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

    它需要执行命令,先在测试目录或测试账号里跑,确认没问题再放到正式项目。

常见问题

6 条

rumor-buster 怎么安装?

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

rumor-buster 支持哪些 AI 工具?

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

rumor-buster 需要什么权限?

权限级别是执行命令。安装流程涉及命令执行,可能通过 openclaw skills install rumor-buster 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

rumor-buster 是免费的吗?

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

rumor-buster 用的人多吗?

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

rumor-buster 安全吗?

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

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

值得选的地方

  • 专注 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调用外部服务未明确有提醒
rumor-buster

谣言破坏者 · 本页

3,045—执行命令MIT-0有提醒

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

SKILL.md 原文

name
rumor-buster
description
Dual-engine fact-checking skill for verifying news, claims, and messages through Chinese + English cross-verification and source tracing. Use when user wants to verify information authenticity, check if a message is true/false, validate news sources, or trace the origin of a claim. Supports /verify and /验证 commands with auto-detection of installed search engines.
version
0.5.0
license
MIT
author
Harry

Rumor Buster - 双引擎谣言终结者

Dual-engine fact-checking with Chinese + English cross-verification and source tracing.

When to Use This Skill

Use Rumor Buster when the user wants to:

  • Verify if a message/news/claim is true or false
  • Check the credibility of information
  • Trace the origin of a rumor
  • Validate sources of news
  • Cross-check claims across languages

Trigger phrases:

  • /verify "claim" or /验证 "消息"
  • "Is this true?" / "这是真的吗?"
  • "Check this" / "验证一下"
  • "Rumor buster" / "谣言终结者"

Quick Start

First-Time Setup

When user first uses /verify, check for config:

CONFIG_FILE = "~/.rumor-buster-config"

if not os.path.exists(CONFIG_FILE):
    # Spawn setup sub-skill
    return sessions_spawn(
        task="Initialize Rumor Buster: detect search engines, configure Tavily API (optional), generate config file",
        agent_id="rumor-buster-setup",
        runtime="subagent",
        mode="session"
    )

Setup sub-skill handles:

  1. Detect native search tools (kimi_search, web_search, web_fetch)
  2. Detect multi-search-engine availability
  3. Configure Tavily API (optional)
  4. Generate ~/.rumor-buster-config

Basic Usage

def handle_verification(user_input):
    """Main entry point for verification requests"""
    # 1. Detect language
    lang = detect_language(user_input)
    
    # 2. Load config
    config = load_config(CONFIG_FILE)
    
    # 3. Extract query
    query = extract_query(user_input)
    
    # 4. Update session state (CRITICAL!)
    update_verification_state(query, lang)
    
    # 5. Perform verification
    results = perform_verification(query, config, lang)
    
    # 6. Generate summary
    return generate_summary(results, lang)

Verification Workflow

Phase 1: Chinese Search

Search Chinese sources for:

  • First appearance of claim
  • Spread path in Chinese media
  • Official responses
def search_chinese(query, config):
    results = []
    
    # kimi_search (if available)
    if config["native"].get("kimi_search", {}).get("available"):
        results.append(kimi_search(query, limit=10, include_content=True))
    
    # multi-search-engine Chinese engines
    if config["multi_search_engine"].get("available"):
        for engine in config["multi_search_engine"].get("chinese", []):
            results.append(search_with_engine(engine, query))
    
    return aggregate_results(results)

Phase 2: English Search

Search English sources for:

  • International perspective
  • Fact-checking reports
  • Official statements
def search_english(query, config):
    results = []
    
    # Tavily (if configured)
    if config["tavily"].get("available"):
        results.append(tavily_search(
            query,
            api_key=config["tavily"]["api_key"],
            max_results=10
        ))
    
    # multi-search-engine English engines
    for engine in config["multi_search_engine"].get("english", []):
        results.append(search_with_engine(engine, query))
    
    return aggregate_results(results)

Phase 3: Cross-Verification

Compare Chinese and English findings:

def cross_verify(cn_results, en_results):
    comparison = {
        "facts_match": compare_facts(cn_results, en_results),
        "timeline_consistent": compare_timeline(cn_results, en_results),
        "authorities_agree": compare_authorities(cn_results, en_results),
        "consistency_score": calculate_consistency(cn_results, en_results)
    }
    return comparison

Phase 4: Source Tracing

Trace claim back to origin:

Original Source → Early Spread → Mainstream Media → Social Media → User

Phase 5: Credibility Scoring

Calculate 0-100% score based on:

  • Source reliability (25%)
  • Cross-confirmation (25%)
  • Evidence quality (20%)
  • Authority acknowledgment (20%)
  • Consistency (10%)

Session State Management (CRITICAL)

Must maintain current verification topic:

verification_state = {
    "current_query": None,
    "current_language": None,
    "chinese_results": None,
    "english_results": None,
    "analysis": None
}

def update_verification_state(query, lang):
    """Update state when new verification starts"""
    verification_state["current_query"] = query
    verification_state["current_language"] = lang
    verification_state["timestamp"] = datetime.now()
    # Reset other fields
    verification_state["chinese_results"] = None
    verification_state["english_results"] = None
    verification_state["analysis"] = None

Why this matters:

User: /verify "Claim A"
System: [Summary for A]
User: /verify "Claim B"  
System: [Summary for B]
User: detailed report  ← MUST return B, not A!

Load references/architecture.md for complete state management details.


Output Format

Summary Report (Default)

# 🔍 Rumor Buster - Verification Summary

**Claim**: "{query}"

## 📊 Credibility Score: {score}% - {verdict}

| Dimension | Result |
|:---|:---|
| **Source** | {source} |
| **Confirmation** | {confirmation} |
| **Evidence** | {evidence} |
| **Consistency** | {consistency} |

## 📝 One-Sentence Conclusion
{conclusion}

## 🔗 Information Source
- **Origin**: {origin}
- **Published**: {time}
- **Spread Path**: {path}

---
💡 Reply "detailed report" to view the complete verification process...

Detailed Report

User replies "detailed report" → Output full analysis including:

  • Complete search results from all engines
  • Source timeline and spread path
  • Cross-verification analysis table
  • Detailed risk assessment

Load references/output-templates.md for complete templates.


Language Support

Auto-Detection

def detect_language(text):
    import re
    chinese_chars = len(re.findall(r'[\一-\鿿]', text))
    total_chars = len(text.strip())
    if total_chars > 0 and chinese_chars / total_chars > 0.3:
        return "zh"
    return "en"

Bilingual Output

All output respects detected language:

  • Summary report language
  • Detailed report language
  • Interactive prompts

Reconfiguration

User can trigger reconfiguration:

  • setup / 设置
  • reset / 重新设置
  • /rumor-buster setup

Handler:

def handle_reconfig(user_input):
    lang = detect_language(user_input)
    return sessions_spawn(
        task=f"Reconfigure Rumor Buster (language: {lang})",
        agent_id="rumor-buster-setup",
        runtime="subagent",
        mode="session"
    )

Reference Files

Load these files when implementing specific features:

FileContentWhen to Load
references/verification-guide.mdComplete verification workflowImplementing verification logic
references/output-templates.mdOutput format templatesFormatting results
references/architecture.mdSystem architecture & sub-skill integrationModifying architecture

Configuration Schema

{
  "setup_completed": true,
  "version": "0.5.0",
  "search_engines": {
    "native": {
      "kimi_search": {"available": false},
      "web_search": {"available": true, "provider": "brave"},
      "web_fetch": {"available": true}
    },
    "multi_search_engine": {
      "available": true,
      "chinese": ["sogou", "toutiao"],
      "english": ["duckduckgo", "startpage"]
    },
    "tavily": {
      "available": true,
      "api_key": "tvly-xxxxx",
      "quota": 1000
    }
  }
}

File Structure

rumor-buster/
├── SKILL.md                      # This file - core workflow
├── LICENSE                       # MIT license
├── scripts/
│   └── tavily_search.py         # Tavily search script
├── sub-skills/
│   └── setup/
│       ├── SKILL.md             # Setup sub-skill documentation
│       └── setup.py             # Setup implementation
└── references/                   # Detailed documentation
    ├── verification-guide.md    # Complete workflow
    ├── output-templates.md      # Output formats
    └── architecture.md          # System architecture

Best Practices

  1. Always update session state when starting new verification
  2. Cross-verify - never rely on single source
  3. Check dates - old news often resurfaces
  4. Trace to origin - don't stop at aggregators
  5. Handle errors gracefully - continue if one engine fails
  6. Respect rate limits - especially Tavily (1000/month free)

*Rumor Buster - Cross-verify, trace sources, seek truth.*

平台分布

OpenClaw

95.77%
按下载量换算944

安全审计

VirusTotal

可疑

ClawScan

可疑

Static analysis

通过

权限和风险

执行命令

安装流程涉及命令执行,可能通过 openclaw skills install rumor-buster 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

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

继续浏览同类 Skills