Chat to Podcast

ReviewAudited by ClawScan on May 10, 2026.

Overview

Review recommended: this skill can scan historical OpenClaw chat logs and publish the resulting content publicly through your Halo account.

Only install or use this if you are comfortable letting it inspect selected OpenClaw conversation history and publish to Halo. Before publishing, approve the exact source conversations, review the full draft for secrets or unrelated content, verify the Halo profile/domain and slug, and consider pinning the npm/CLI dependencies.

Findings (4)

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

Private or unrelated chat history could be pulled into the generated podcast draft or influence the agent; if missed during review, it could be published publicly.

Why it was flagged

The workflow searches historical OpenClaw session logs and then instructs extracting the entire matched session with no count limit, which can include unrelated private messages, tool outputs, secrets, or prior instructions.

Skill content
for f in ~/.openclaw/agents/main/sessions/*.jsonl ... grep -qi "Halo" ... 找到目标 session 后,提取完整对话记录(不做条数限制)。
Recommendation

Require the user to approve exact source sessions and turn ranges before reading them, minimize to relevant excerpts, treat historical logs as untrusted content, and add explicit redaction and exclusion rules.

What this means

A mistaken slug, wrong profile, or insufficient review could modify or publish blog content publicly.

Why it was flagged

The helper can force-import content and make a Halo post public. This matches the stated publishing purpose and the SKILL asks for user confirmation, but it is still a high-impact mutation.

Skill content
halo post import-markdown --profile "$PROFILE" --file "$MD_FILE" --force ... halo post update "$POST_NAME" --visible PUBLIC ... halo post update "$POST_NAME" --publish true
Recommendation

Confirm the target Halo profile, slug, and full rendered draft before running the publishing step; avoid using --force where an existing post might be overwritten.

What this means

The skill can publish or update posts as the Halo account associated with the selected profile.

Why it was flagged

The skill relies on a logged-in Halo CLI profile to act on the user’s blog account. That is expected for publishing, but users should recognize that the skill can use that account authority.

Skill content
已配置 Halo profile(如 `blog-danke`)并完成登录 ... halo post create --profile blog-danke ... --publish true
Recommendation

Use a dedicated or least-privilege Halo profile/token if possible, verify the active profile and blog domain before publishing, and revoke credentials when no longer needed.

What this means

Future package changes or a compromised dependency could affect the publishing process.

Why it was flagged

The instructions use unpinned npm/CLI dependencies and a runtime npx conversion step. This is normal for the publishing workflow but leaves behavior dependent on external package versions.

Skill content
npm install -g @halo-dev/cli ... 正文用 `npx marked` 转成 HTML
Recommendation

Pin dependency versions, document required binaries such as npx/node/python3, and install from trusted registries only.