Tech Morning Briefing

PassAudited by ClawScan on May 11, 2026.

Overview

This is a coherent instruction-only news briefing skill, but it uses scheduled automation, Tavily search access, Feishu posting/document updates, and local state that users should configure deliberately.

This skill appears benign and purpose-aligned. Before installing, make sure you are comfortable giving it Tavily search access and Feishu posting/document permissions, verify the Feishu destination, keep the local data/config files private, and only enable the cron job if you want it to run automatically every day.

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

Once configured, the agent can send generated briefings to Feishu and append them to a Feishu document.

Why it was flagged

The skill tells the agent to use Feishu messaging and document tools to publish and append content. This is central to the stated briefing purpose, but it mutates a third-party workspace.

Skill content
7. 推送到飞书聊天(通过 cron announce)
8. 读取 `data/config.json` 获取 feishuDocToken,追加到飞书文档
Recommendation

Confirm the target chat and document permissions before enabling the workflow, and review the first few generated briefings.

What this means

The briefing can run every morning and post/update content without asking each time.

Why it was flagged

The README documents a recurring cron job. It is user-directed and expected for a daily briefing, but it creates ongoing autonomous execution until disabled.

Skill content
openclaw cron create \
  --label morning-briefing \
  --schedule "30 7 * * *"
Recommendation

Only create the cron job if recurring automation is intended, and keep track of how to pause or delete it.

What this means

Users may need to provide Tavily and Feishu access even though the registry metadata does not clearly advertise those requirements.

Why it was flagged

The skill needs external service access for search and Feishu posting/document sync. This is expected, but the registry metadata declares no required env vars or primary credential.

Skill content
| **Tavily API Key** | 搜索引擎(替代 DuckDuckGo) | 在 `.env` 中设置 `TAVILY_API_KEY` ... |
| **飞书应用** | 推送消息 + 文档同步 | OpenClaw feishu channel 开启 `feishu_doc` 工具即可 |
Recommendation

Use scoped Feishu permissions where possible, avoid sharing broad workspace credentials, and treat the Tavily API key and Feishu configuration as sensitive.

What this means

Local state may influence future briefings, and the Feishu document token should not be exposed casually.

Why it was flagged

The skill persists a Feishu document token and a reusable news pool. This is disclosed and bounded, but stored state can affect later runs.

Skill content
创建后把 `doc_token` 存到 `data/config.json` ... 池文件:`data/news-pool.json`
Recommendation

Keep the skill data directory private, review or reset stored files if outputs look wrong, and avoid committing `data/config.json`.