Verified Research

执行多源核实的深入研究，拆解复杂问题，优先采集高可信度来源，核实信息时效性并生成结构化报告，支持三天缓存。

This skill is broadly coherent with its stated purpose (multi-source research), but it has a few important discrepancies you should consider before installing: - The scripts write summaries into /root/.openclaw/workspace/MEMORY.md automatically during cleanup. That means research summaries will be appended to the agent's global memory without an extra consent step; if you do not want your research summaries persisted globally, do not install or edit the scripts to disable that behavior. - The metadata declares no required binaries or config paths, but the scripts require Python 3 and common CLI tools (md5sum, stat, sed, xxd, tail, etc.) and expect the workspace path /root/.openclaw/workspace to exist. Consider adding these as declared requirements or run in an environment where these are available. - cleanup.sh deletes cached research directories after archiving the summary. If you want to keep full reports, explicitly copy them to your workspace before the 3-day window expires. - If you plan to use this skill in a multi-tenant or sensitive environment, review/modify the scripts to: (a) prompt before writing to global MEMORY.md, (b) avoid hard-coded /root paths, and (c) explicitly declare runtime dependencies in the skill metadata. - Suggested mitigations: run the skill in a sandboxed agent instance first, inspect/modify the code to change the MEMORY.md write behavior or target a user-controlled path, and confirm Python 3 is available. If these points are acceptable or are intentionally intended behavior, the skill appears functionally coherent; otherwise treat it as suspicious and proceed with caution.

Type: OpenClaw Skill Name: verified-research Version: 1.2.1 The skill implements a structured multi-source research methodology with a local caching and automated cleanup system. It uses a series of shell and Python scripts (research.sh, manifest.sh, finalize.sh, cleanup.sh) to manage research 'evidence cards' in /tmp/deep-research-cache/ and archive summaries to the workspace's MEMORY.md file. The logic is transparent, well-documented, and lacks any indicators of data exfiltration, unauthorized persistence, or malicious prompt injection.