Topic to Article Kit

Turn a chosen AI topic into a public-account writing package: collect evidence from X/Twitter and other sources, extract high-value comments, and produce title options + structured outline written into Obsidian. Use when user asks for topic-based research and article prep.

This skill appears to do what it says (collect web evidence and write Obsidian notes) but its instructions require direct writes to your real Obsidian vault and browser control while the metadata declares no filesystem/config permissions. Before installing or invoking it, consider: 1) Ask the skill author (or require the agent) to prompt you for the exact absolute vault path on every run rather than using a default. 2) Require an explicit user confirmation before any file write, and request a preview of proposed file names/contents. 3) Run it first in a sandbox or against a workspace mirror copy of your vault to confirm behavior and avoid accidental overwrites. 4) Back up your Obsidian vault before use. 5) If you don't want the agent to control your real browser, restrict it to a browser automation environment or disable autonomous invocation. 6) If possible, require the skill to declare any config paths or tools it needs (e.g., browser automation hooks) so you can reason about permissions. These steps reduce the risk of accidental data writes or unintended data exposure.

Type: OpenClaw Skill Name: topic-to-article-kit Version: 1.0.5 The skill bundle instructs the AI agent to perform web scraping and write files directly to the user's local Obsidian vault using an "absolute path under user's real vault," as specified in `SKILL.md`. While the stated purpose of creating research notes and outlines is benign, the instruction to bypass potential workspace sandboxing and write to an absolute path on the user's file system represents a high-risk capability. This could be exploited as an arbitrary file write vulnerability if the agent's path resolution or file system access controls are flawed, even though the skill itself does not demonstrate explicit malicious intent like data exfiltration or backdoor installation.