Article Publisher

SuspiciousAudited by ClawScan on May 10, 2026.

Overview

The skill matches its stated publishing purpose, but it can post publicly to multiple logged-in accounts and persist login cookies, so it needs careful review before use.

Install only if you are comfortable letting the skill automate logged-in browser sessions and publish publicly on your behalf. Start in testMode, review the browser draft before publishing, avoid the all-platform command until you have checked the content, and protect or periodically clear the saved cookie/session files.

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

A mistaken or overly broad agent invocation could publish content publicly under the user's account.

Why it was flagged

The publishing adapters default to non-test mode and proceed to click the platform publish button. This is expected for a publisher, but it is a high-impact public account action without an explicit confirmation gate shown in the artifacts.

Skill content
async publish(article: ArticleContent, testMode: boolean = false) ... console.log('📤 点击发布按钮...'); await this.clickPublish();
Recommendation

Use testMode or manually review drafts first, and only invoke publishing after explicitly confirming the platform, title, content, cover, and tags.

ConcernHigh Confidence
ASI08: Cascading Failures
What this means

One error could be replicated across Zhihu, Bilibili, Baijiahao, Toutiao, Xiaohongshu, and any other logged-in supported platforms.

Why it was flagged

The all-platform workflow sends the same article to every logged-in supported platform. A bad title/content/tag set or accidental invocation can propagate across multiple public accounts.

Skill content
publish_to_all ... const adapters = getAllAdapters(); ... if (isLoggedIn) { const result = await adapter.publish(article, testMode); }
Recommendation

Prefer publishing to one selected platform first, require per-platform confirmation, and use the all-platform workflow only after review.

What this means

Anyone or anything that can access the saved cookie files may be able to reuse logged-in publishing sessions.

Why it was flagged

Persisted cookies are session credentials for third-party publishing accounts. The behavior is disclosed and purpose-aligned, but the artifacts do not clearly bound where cookies are stored, how they are protected, or how long they remain usable.

Skill content
Cookie持久化 - 登录状态自动保存,免重复登录 ... Cookie 自动保存在本地 ... Cookie 保存在本地,注意保密
Recommendation

Store the skill in a trusted local environment, restrict file permissions, avoid sharing the configuration/cookie files, and provide a clear logout/cleanup process before relying on it.

What this means

Installation may download and run third-party package/browser components needed for automation.

Why it was flagged

The npm/Playwright dependency installation is expected for browser automation, but caret-ranged external dependencies and browser downloads mean users must trust the package sources and installation environment.

Skill content
"dependencies": { "playwright": "^1.40.0" }, "devDependencies": { "cross-env": "^7.0.3" }
Recommendation

Install only from trusted registries, consider pinning dependency versions, and review package integrity before use.