Tweet Pipeline

Notion-to-Twitter automation — pull approved tweets from a Notion database, schedule one-shot crons for exact post times, and post via X/Twitter OAuth2 API....

This skill is not outright malicious, but it is inconsistent and requires careful review before use. Key concerns: (1) The scripts do not use the declared NOTION_API_KEY env var — they invoke the 1Password CLI (op) and read a local service token file to pull the Notion key from 1Password; (2) Twitter credentials are read from a local file (~/.xurl), not from declared env vars; (3) the scripts call hardcoded user-specific binaries and paths (a specific python in /Users/loki, /opt/homebrew node, ~/.npm-global/bin/openclaw) that may not exist and reveal assumptions about the developer's machine; (4) there is subprocess usage of 'op' and 'openclaw cron add' which will access your password manager and schedule jobs on your system. Recommended actions before installing or running: - Ask the author to explain why NOTION_API_KEY is declared but not used, and to list all required binaries (op, node, openclaw CLI). - Inspect and/or sanitize ~/.xurl and remove sensitive credentials, or modify scripts to accept Twitter creds via environment variables instead of reading a local file. - Replace hardcoded paths with configurable values or relative paths. - Run the scripts in a controlled sandbox or test account first (dry-run mode is provided). - Ensure you are comfortable granting the skill access to your 1Password service account token and to schedule crons on your machine; if not, do not run it. - Because the refresh logic contains buggy/undefined variables, review and fix that function before trusting automatic token refresh or credential writes.

Type: OpenClaw Skill Name: tweet-pipeline Version: 1.0.0 The skill contains hardcoded absolute paths to a specific user's home directory (/Users/loki/) and attempts to read sensitive credentials from the host filesystem, specifically ~/.xurl and ~/.config/openclaw/.op-service-token. It relies on the 1Password CLI (op) to fetch secrets, which is a high-privilege operation. While these behaviors appear intended for a specific personal automation setup, the hardcoded environment dependencies and the practice of accessing sensitive files outside the workspace are risky. Additionally, scripts/tweet_post_one.py contains broken logic with undefined variables (refresh, user, xurl_path) in its token refresh function.