Token导航 LogoToken导航

Agent Skill · 研究检索

data-source-verification(数据来源验证)

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

data-source-verification 是研究检索类 Agent Skill,可用宿主为 OpenClaw,通过ClawHub获取,权限为需要联网;许可证为 MIT-0,第三方扫描已通过,按安装量在研究检索类的 73,675 个 Skill 里排第 13,492。

总安装 9,335周安装 401GitHub Stars 公开资料未说明下载 3,272核验 2026-05-01

安装说明

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

安装方式

通过对话安装

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

请帮我安装这个 Agent Skill:data-source-verification(数据来源验证)
来源仓库:https://github.com/larry-of-cosmotim/data-source-verification
安装命令:
openclaw skills install data-source-verification
安装前请先检查当前环境是否支持对应 CLI,并向我确认将要执行的命令、安装目录、联网范围和文件读写权限;确认后再执行。

命令行安装

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

ClawHubOpenClaw
openclaw skills install data-source-verification

这个 Skill 是做什么的

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

依据原始论文核验数值数据的真实性与来源可靠性。建立数据集每个值的完整可追溯引用链条。data-source-verification 属于研究检索类 Skill,可作为该场景下的辅助能力补充。支持图表与表格内容的交叉验证与溯源标注。适用于科研或高可信度报告场景增强论证基础。需用户提供权威参考文献列表作为验证基准。

上手步骤

4 步
  1. 1

    确认自己的宿主工具

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

  2. 2

    拿到安装命令

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

  3. 3

    安装后重启宿主

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

  4. 4

    按最小权限试用

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

常见问题

6 条

data-source-verification 怎么安装?

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

data-source-verification 支持哪些 AI 工具?

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

data-source-verification 需要什么权限?

权限级别是需要联网。该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

data-source-verification 是免费的吗?

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

data-source-verification 用的人多吗?

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

data-source-verification 安全吗?

第三方扫描结果为通过,但这只覆盖已知的静态检查项,不能替代自己读一遍源码和安装命令。

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

值得选的地方

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

数据来源验证 · 本页

9,335—需要联网MIT-0通过

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

SKILL.md 原文

name
data-source-verification
description
Verify numerical data against original papers and maintain traceable provenance for every value in datasets, tables, and plots. Includes citation source management, PDF-based verification, and audit reporting.
version
2.0.0
homepage
https://github.com/Larry-of-cosmotim/data-source-verification
metadata
openclaw
emoji
🔍

Data Source Verification

A systematic workflow for verifying that every data point in a research dataset can be traced back to its original source paper, figure, table, or text passage.

When to Use

  • Building datasets from literature (CSV, JSON, tables)
  • Populating tables or plots with values from multiple papers
  • Reviewing existing datasets for data integrity
  • Before submitting any paper that includes compiled data

Core Rule

Every numerical value must be traceable to a specific location in the original paper. If you cannot find the value in the cited source, it is unverified and must be flagged — never included as confirmed data.

Data Provenance Chain

Source PDF → CITATION.md (extracted values) → CSV/data table → LaTeX manuscript

Every link in this chain must be auditable. If someone asks "where did this number come from?", the answer should be: paper X, Table Y, column Z — and we have the PDF to prove it.


Citation Source Management

Project Setup (init)

Create a Citation_Sources/ directory for the project:

Citation_Sources/
  AuthorLastName_Year_Journal_ShortTitle/
    Author_Year_Topic.pdf          ← original paper
    Author_Year_Topic_SI.pdf       ← supplementary info (if any)
    CITATION.md                    ← structured metadata + data provenance

CITATION.md Template

Every cited paper gets a CITATION.md file:

# Author et al. Year — Short Description
**Title**: Full title
**Authors**: Author list
**Journal**: Journal Vol, Pages (Year)
**DOI**: 10.xxxx/xxxxx
**Data used**: [exact values extracted, with table/figure reference]
**PDF**: ✅ Confirmed | ❌ NOT DOWNLOADED — [reason]
**Status**: CONFIRMED | ⚠️ NEEDS CONFIRM — [reason]
**Notes**: [any caveats, discrepancies, proxy assumptions]

Adding a Source (add)

When adding a new citation:

  1. Create the folder: Citation_Sources/AuthorLastName_Year_Journal_ShortTitle/
  2. Download the original PDF — always try to get the actual paper, not just the abstract
  3. Download supplementary information if it contains data
  4. Create CITATION.md from the template
  5. Extract the specific values you need, recording exact table/figure/page locations
  6. Mark the PDF status and verification status

Verification Workflow

Step 1: Collect with Provenance

When extracting data from a paper, record ALL of the following for each value:

Value: 0.65 W/m·K
Paper: Cheng et al. 2021
DOI: 10.1002/smll.202101693
Location: Table 2, row 3
Method: TDTR (time-domain thermoreflectance)
Data type: Experimental
Verified: YES — value confirmed in Table 2

Never record a value without filling in the Location, Data type, and Verified fields.

Step 2: Verify Against Original

For each data point:

  1. Always download the original PDF — don't trust web scraping, abstracts, or secondary sources
  2. Find the exact value in a table, figure, or text passage
  3. Record where you found it — table number, figure number, page, equation
  4. Note the measurement method — experimental technique, simulation, estimate
  5. Check units — convert if needed, note the original units
  6. Track the data type: DFT-calculated, experimentally measured, or derived (note assumptions)

If the paper is behind a paywall and you cannot verify:

  • Mark as ⚠️ NEEDS CONFIRM — paywall
  • Note this limitation in CITATION.md

Step 3: Cross-Check the Full Chain

Verify consistency at every step:

Value in PDF → Value in CITATION.md → Value in data table/CSV → Value in manuscript

Any mismatch at any step is a flag.

Step 4: Flag Problems

Mark any value with one of these status levels:

StatusMeaningAction
VERIFIEDFound exact value in cited paper at stated locationInclude in dataset
APPROXIMATEValue is close but not exact (e.g., read from figure)Include with note
UNVERIFIEDCannot find value in cited paperFlag — do not use without user approval
MISATTRIBUTEDCited paper does not contain this data at allRemove from dataset, alert user immediately
ESTIMATEDValue was calculated or estimated, not directly measuredInclude with clear label
⚠️ NEEDS CONFIRMPDF not available (paywall) or value needs double-checkFlag for manual verification

Step 5: Flag Discrepancies

When multiple sources report different values for the same quantity:

  • Record both values with their sources
  • Note the discrepancy explicitly (e.g., "B = 45 GPa (Author A, Table 2) vs B = 86 GPa (Author B, Fig. 3)")
  • Check if the difference is due to measurement method, sample preparation, or temperature
  • Let the user decide which value to use — do not silently pick one

Dataset Format

When building compiled datasets, always include provenance columns:

CSV format:

Material,Property,Value,Unit,Source_Paper,DOI,Source_Location,Method,Data_Type,Verified,Notes
Li6PS5Cl,kappa,0.69,W/m·K,Cheng 2021,10.1002/smll.202101693,Table 2,TDTR,experimental,YES,
Li3InCl6,v_longitudinal,2800,m/s,Asano 2018,10.1002/adma.201803075,NOT FOUND,Unknown,unknown,MISATTRIBUTED,Paper contains no Li3InCl6 sound velocity data

JSON format:

{
  "material": "Li6PS5Cl",
  "property": "thermal_conductivity",
  "value": 0.69,
  "unit": "W/m·K",
  "source": {
    "paper": "Cheng et al. 2021",
    "doi": "10.1002/smll.202101693",
    "location": "Table 2, row 5",
    "method": "TDTR",
    "dataType": "experimental",
    "verified": true
  }
}

Audit Workflow (audit)

Scan all CITATION.md files and generate a report:

  1. List all unique sources in Citation_Sources/
  2. For each source, check:

- PDF downloaded? (✅ or ❌) - CITATION.md complete? (all fields filled) - Values confirmed against PDF?

  1. Generate audit summary:
## Audit Report — [Project Name]
Date: [timestamp]

### Summary
- Total sources: [N]
- PDFs confirmed: [N] / [N]
- Values verified: [N] / [N]
- Needs confirmation: [N]
- Missing PDFs: [N]

### Source Details

| Paper | PDF | Values | Verified | Status |
|---|---|---|---|---|
| Cheng 2021 | ✅ | 3 | 3/3 | CONFIRMED |
| Asano 2018 | ✅ | 2 | 1/2 | ⚠️ 1 MISATTRIBUTED |
| Wang 2014 | ❌ | 4 | 0/4 | ⚠️ NEEDS CONFIRM |

### Flagged Values
- Li3InCl6 v_longitudinal: MISATTRIBUTED to Asano 2018 — paper contains no LIC data
- LGPS density: conflicting values (2.0 vs 1.9 g/cm³) between Wang 2014 and Kamaya 2011
  1. Report findings — list verified, flagged, and misattributed values
  2. Recommend action for each flagged value

Export (export)

Generate a summary table of all data values and their provenance:

## Data Provenance Summary — [Project Name]

| Material | Property | Value | Unit | Source | Location | Data Type | Status |
|---|---|---|---|---|---|---|---|
| LLZTO | κ | 0.42 | W/m·K | Muy 2019 | Table 1 | experimental | VERIFIED |
| LAGP | v_avg | 4700 | m/s | Rohde 2021 | Table S2 | experimental | VERIFIED |
| Li3InCl6 | v_avg | 1849 | m/s | Qiu 2025 | Table 1 | DFT | VERIFIED |

Red Flags

Watch for these indicators of unreliable data:

  • Value attributed to a paper but no specific table/figure cited
  • "Estimated from family properties" without a clear methodology
  • Values that appear in reviews but cannot be traced to original measurements
  • Round numbers that suggest estimation rather than measurement (e.g., 2800 m/s vs 2837 m/s)
  • Same value appearing in multiple papers without independent measurement
  • DFT values presented as experimental without noting the distinction
  • Discrepancies between different sources for the same quantity left unaddressed

Rules

  1. Never assume a citation is correct — always verify against the original paper
  2. Always download the PDF — don't trust abstracts, web scraping, or secondary sources
  3. Secondary sources are not verification — a review paper citing a value does not confirm it
  4. Flag immediately when a value cannot be found in its cited source
  5. Track data type — distinguish DFT-calculated, experimentally measured, and derived values
  6. Flag discrepancies — when two sources disagree, note both values and let the user decide
  7. Prefer measured over estimated — clearly label the difference
  8. Document everything — future researchers need the audit trail
  9. When in doubt, exclude — a smaller verified dataset beats a larger unverified one

平台分布

OpenClaw

87.49%
按下载量换算2,863

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

需要联网

该 Skill 可能需要联网访问来源站点、仓库或外部 API;具体网络访问范围需要结合源码和 README 复核。

安装前确认

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

继续浏览同类 Skills