openclaw-ledger

What This Skill Does

The openclaw-ledger skill provides a robust, tamper-evident audit trail for your OpenClaw agent workspace. In an environment where agents perform autonomous file modifications, command executions, and configuration changes, keeping track of exactly what was altered is critical for debugging and security. This skill functions by maintaining a hash-chained log of your workspace state. Every time you snapshot or record changes, the ledger calculates a SHA-256 hash that links to the previous state. If an entry is maliciously modified, deleted, or inserted after the fact, the mathematical chain breaks, and the built-in verification tool will immediately flag the corruption. By relying exclusively on the Python standard library, the ledger ensures that security monitoring doesn't introduce external vulnerabilities or require additional pip dependencies.

Installation

To install this skill, use the ClawHub interface from your agent's command line environment:

clawhub install openclaw/skills/skills/atlaspa/openclaw-ledger

Once installed, initialize your workspace ledger before starting your task:

python3 {baseDir}/scripts/ledger.py init --workspace /your/project/path

Use Cases

• Forensic Auditing: Review exactly what an agent changed during a complex refactor or debugging session when things don't go as expected.
• Security Enforcement: Detect unauthorized modifications to agent-controlled files by verifying the integrity of the ledger chain.
• Change Tracking: Maintain a persistent, verifiable timeline of an agent's progress throughout long-running automation tasks.
• State Recovery: Use the history snapshots to better understand the delta between a known-good configuration and the current (potentially broken) state.

Example Prompts

1. "OpenClaw, please initialize a ledger in the current directory and record a snapshot of the workspace before you start refactoring the auth modules."
2. "I suspect the last run was corrupted. Can you run the ledger verification command to check if any files were tampered with since the last successful session?"
3. "Show me the last 10 entries in the workspace ledger so I can review the sequence of commands executed during the file cleanup process."

Tips & Limitations

• Manual Triggering: Remember that the ledger is currently invoked via commands. Ensure your agent is instructed to run the 'record' command periodically to maintain a granular history.
• Performance: While SHA-256 hashing is fast, performing frequent ledger updates in massive repositories with millions of files may introduce minor latency.
• Local Storage: The ledger stores data locally. Ensure your workspace remains persistent; if the ledger files are deleted, the history is permanently lost.
• No External Dependency: This tool is purely local and requires no network connections, making it an ideal choice for high-security environments where outbound traffic is restricted.