QQBot Send Local Media

AdvisoryAudited by Static analysis on May 10, 2026.

Overview

No suspicious patterns detected.

Findings (0)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

If the user selects a sensitive file, it may be delivered through QQBot to the active QQ destination.

Why it was flagged

The skill intentionally passes local file media to QQBot using the qqmedia relay mechanism. This is purpose-aligned, but users should understand that selected local file contents may be sent outside the local machine.

Skill content
Send the staged path with:
   - `<qqmedia>staged-absolute-path</qqmedia>`
Recommendation

Use only with files the user explicitly wants to send, and verify the QQ recipient or chat context before sending sensitive media.

What this means

The agent may run a local Python script to copy the requested file into the QQ media relay directory and later remove the staged copy.

Why it was flagged

The workflow requires executing a bundled Python helper. This is expected for staging and cleanup, and the provided source shows bounded local file copy/delete behavior without networking or obfuscation.

Skill content
Run:
   - `python scripts/stage_media.py <source_path>`
Recommendation

Keep the bundled helper unchanged and avoid running modified or unreviewed replacement scripts.

What this means

A staged copy in the QQ media relay directory can be removed after sending; the original source file should not be touched.

Why it was flagged

The cleanup helper can delete files, but it confines deletion to paths resolving under ~/.openclaw/media/qqbot. The SKILL.md further instructs cleanup only for the exact staged path returned during the current send flow.

Skill content
staged.relative_to(dest_dir)
...
staged.unlink()
Recommendation

Only run cleanup on the exact path printed by the staging command, as the skill instructs.

What this means

Users have less external provenance information about who maintains the skill or where to verify it.

Why it was flagged

The package provenance is limited in the registry metadata. This is not a concern by itself because the artifact contains the helper source and no remote install mechanism or external dependencies are shown.

Skill content
Source: unknown
Homepage: none
Recommendation

Review the included SKILL.md and script before installing, and prefer updates from a known trusted source when available.