vardoger — Analyze History

Use when the user asks to personalize their assistant, to use vardoger, or to analyze their OpenClaw conversation history. Runs the vardoger CLI to read past...

This skill runs a local CLI (vardoger) that will read your conversation history and write a personalization file into your agent/platform directories. That behavior matches the skill's description, but it requires granting read access to session directories and write access to platform rule/skill locations (files under ~/.vardoger, ~/.openclaw, ~/.claude, ~/.codex, etc.). Before installing or approving commands: 1) Confirm you trust the vardoger project (review the GitHub repo and code). 2) Back up any agent/rules files you care about. 3) When asked to allow commands that write outside the workspace, only approve if you expect the skill to modify agent rules; otherwise deny. 4) Consider running vardoger in an isolated environment (container/VM) if you want to avoid giving it direct access to your main agent config. 5) Note that no credentials are requested by the skill, but the CLI will process potentially sensitive conversation text — treat outputs accordingly and inspect the generated personalization file before using it. If you need more assurance, ask for a description of exactly which paths will be read/written on your host and for a dry-run that prints intended write operations without performing them.

Type: OpenClaw Skill Name: vardoger-analyze Version: 0.3.1 The `vardoger-analyze` skill (SKILL.md) requires broad read and write access to sensitive directories outside the standard sandbox, including private conversation histories from platforms like Claude, Cursor, and OpenClaw (e.g., `~/.claude/projects/`, `~/.openclaw/agents/`). It uses an external CLI tool (`vardoger`) to process these logs and generate personalization rules. While the behavior is transparently documented and aligned with the stated purpose of personalizing the assistant, the high-privilege access to private data and the requirement to bypass sandbox protections for global file writes represent significant security and privacy risks.