Plakar backup

Teaches the agent how to list, inspect, diff, and restore Plakar snapshots. Invoke when the user says "undo", "rollback", "restore", or "revert".

Security Scan

The skill's instructions match a Plakar restore workflow, but its metadata omits required binaries/config and the skill can perform destructive filesystem restores — verify provenance and declared requirements before installing.

Purpose & Capability

The name/description (Plakar restore) aligns with the SKILL.md (listing, diffing, restoring snapshots). However the registry metadata declares no required binaries or config paths while the SKILL.md explicitly requires the 'plakar' binary in $PATH and a plugin config value 'plakar.store' — an incoherence between claimed requirements and the runtime instructions.

Instruction Scope

Instructions are narrowly scoped to listing, inspecting, diffing, and restoring Plakar snapshots and explicitly tell the agent to confirm with the user before restoring. They do direct the agent to run commands that can overwrite live files (restore operations) which is expected for this purpose and appropriately flagged in the doc.

Install Mechanism

This is an instruction-only skill with no install spec and no code files, so there is nothing written to disk by the skill itself. That is the lowest-risk install mechanism.

Credentials

The SKILL.md depends on the 'plakar' binary and on a plugin configuration value 'plakar.store', but the skill's declared requirements list no required binaries or config paths. While no secrets or environment variables are requested, the omission means an agent or administrator might not realize the skill will attempt to run a local tool and access a store path.

Persistence & Privilege

The skill does not request always:true and is user-invocable only; it does not ask to modify other skills or system-wide settings. Autonomous invocation is allowed (default) but is not combined with other high-risk flags here.

What to consider before installing

This skill appears to implement legitimate Plakar restore steps, but its metadata omits runtime requirements and the source is unknown. Before installing: 1) Verify the skill's provenance/author (no homepage, unknown source). 2) Confirm you have the 'plakar' binary and the plugin configuration key 'plakar.store' documented and correct. 3) Ensure the agent is configured to always prompt you before any restore (restores overwrite live files). 4) Test restores in a safe environment (non-production) to confirm behavior. If you require strict visibility, ask the publisher to update the metadata to declare the required binary and config path.

Plakar Restore Workflows

This skill covers restore operations only. Triggering snapshots is handled automatically by the openclaw-plugin-plakar plugin — you do not need to run plakar backup manually.

When to offer restore

Offer to restore from a Plakar snapshot when the user says anything like:

• "undo that", "roll back", "revert to before", "restore my files"
• "something went wrong, can we go back"
• "the last tool call broke things"

Prerequisites

• plakar must be in $PATH
• The store path is available in plugin config as plakar.store
• Always pass -no-agent to avoid requiring a running plakar agent daemon

CLI syntax (v1.0.6+)

All commands use the form:

plakar -no-agent at <store> <command> [options]

List all snapshots

plakar -no-agent at <store> ls

Output: snapshot ID, timestamp, size, path. Present the list to the user and ask which snapshot to restore from.

Inspect a snapshot's contents

plakar -no-agent at <store> ls <snapshotID>
plakar -no-agent at <store> ls -recursive <snapshotID>:/path

Use this to confirm the snapshot contains the expected state before restoring.

Diff two snapshots

plakar -no-agent at <store> diff <snapshotID1> <snapshotID2>
plakar -no-agent at <store> diff -highlight <snapshotID1>:/file <snapshotID2>:/file

Use this to show the user what changed between two points in time.

Restore a snapshot

Restore all files to the original paths:

plakar -no-agent at <store> restore <snapshotID>

Restore to a specific directory:

plakar -no-agent at <store> restore -to /tmp/restore-here <snapshotID>

Restore a specific path within a snapshot:

plakar -no-agent at <store> restore -to /tmp/restore-here <snapshotID>:/path/to/file

Always confirm with the user before running a restore — it overwrites live files.

Example agent interaction

User: "The last edit broke my config file, can you undo it?"

1. Run plakar -no-agent at <store> ls and show the most recent snapshots
2. Ask: "Should I restore from snapshot <id> taken at <timestamp>?"
3. On confirmation: plakar -no-agent at <store> restore -to <original-path> <id>
4. Confirm the restore completed and invite the user to verify the file