Skill flagged — suspicious patterns detected
ClawHub Security flagged this skill as suspicious. Review the scan results before using.
Backup of conversations to Obsidian
v1.0.0Automatic conversation backup system for Obsidian with incremental snapshots, hourly breakdowns, and formatted chat-style markdown. Use when setting up conversation archival, preventing data loss from /new resets, or organizing chat history in Obsidian vault with proper formatting (colored callouts, timestamps, multi-paragraph support).
⭐ 4· 2.6k·11 current·13 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
medium confidencePurpose & Capability
Overall the scripts do what the description promises: parse Clawdbot JSONL session files and write Markdown snapshots to an Obsidian vault. However, the code expects files in /root/.clawdbot and /root/clawd by default and references Telegram warning support even though the skill declares no required credentials; this is a mild mismatch in what the skill 'declares' versus what it will try to access at runtime.
Instruction Scope
Scripts read session JSONL files and write snapshots (expected). They also attempt to read /root/.clawdbot/clawdbot.json (to extract .telegram.token) and may use a CHAT_ID variable to send Telegram warnings. The SKILL.md/config.example implies a local config file for BOT_TOKEN/CHAT_ID but the runtime scripts do not read that config; instead they pull BOT_TOKEN from a different file. This is inconsistent and means the skill will silently attempt to read other local configuration files for secrets that were not declared.
Install Mechanism
There is no centralized package install spec (instruction-only), but the bundle includes an install.sh that edits scripts in-place, renames files, and creates directories. Running install.sh will write files and modify the included scripts (sed replacements). This is standard for simple bundles but you should inspect install.sh before executing.
Credentials
The registry metadata lists no required environment variables or credentials, but the code optionally uses a Telegram bot token and chat ID to send warnings. The token is read from /root/.clawdbot/clawdbot.json (jq '.telegram.token'), while CHAT_ID is expected to exist in the environment or a config — this mismatch is not declared. The scripts therefore may access local config files containing secrets without the skill explicitly requesting them.
Persistence & Privilege
The skill does not request always:true, does not alter other skills, and only writes snapshot files and tracking files in user-specified directories. It requires cron to run automatically (user sets crontab). No elevated or persistent platform-wide privileges are requested.
What to consider before installing
This package appears to implement the advertised backup behavior, but it has sloppy configuration handling and will try to read local config files for a Telegram token even though no credentials are declared. Before installing: (1) open and inspect install.sh and the scripts (monitor_and_save.sh, save_full_snapshot.sh) yourself — do not run blindly; (2) verify or change default paths (they default to /root/…); run/install as a non-root user if possible; (3) if you do not want Telegram warnings, remove or disable the curl blocks or ensure BOT_TOKEN/CHAT_ID are empty; (4) confirm where CHAT_ID should be set (scripts do not read the included config.example) and either add explicit config parsing or set environment variables yourself; (5) test the scripts on a small sample session file to confirm they only write local snapshot files and do not transmit conversation contents; (6) consider moving tracking files into a directory you control and audit permissions. If you want, I can point out the exact lines to change to remove Telegram calls and hardcoded root paths.Like a lobster shell, security has layers — review code before you run it.
latestvk979986pbs2crcnd38xekhxmj57znmfk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.