Social Push Semi
Analysis
This skill mostly matches a semi-automatic Xiaohongshu publishing workflow, but it bundles logged-in browser automation and broader publish/comment/account-data capabilities that should be reviewed before installation.
Findings (5)
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.
Checks for instructions or behavior that redirect the agent, misuse tools, execute unexpected code, cascade across systems, exploit user trust, or continue outside the intended task.
python cdp_publish.py ... publish --title "标题" ... python cdp_publish.py ... click-publish ... python cdp_publish.py ... post-comment-to-feed --feed-id FEED_ID ...
The stated skill workflow is semi-automatic, but the included CDP publisher documents direct publish, final-click, and comment-posting commands that could bypass the manual-publish guardrail if invoked.
requests>=2.28.0 websockets>=12.0
The setup installs dependencies with lower-bound version ranges rather than pinned versions or hashes, allowing future package changes.
Checks whether tool use, credentials, dependencies, identity, account access, or inter-agent boundaries are broader than the stated purpose.
Manages multiple Xiaohongshu accounts with separate Chrome profiles: - Each account has its own user-data-dir for cookie isolation - Accounts are stored in a JSON config file
The package persists and reuses authenticated browser profiles for Xiaohongshu accounts, which is high-impact account/session authority.
python cdp_publish.py ... get-notification-mentions [--wait-seconds 18] python cdp_publish.py ... content-data [--page-num 1] [--page-size 10] [--type 0]
The bundled tool documents reading logged-in account notifications and creator/content analytics, which goes beyond preparing and preview-filling a publish package.
BASE_URL="https://ark.cn-beijing.volces.com/api/v3" MODEL="doubao-seedream-5-0-260128" API_KEY_ENV="DOUBAO_API_KEY"
The topic-to-image workflow uses an external Doubao-compatible API and an API key environment variable, which is expected for this feature but not declared in the registry requirements.
