Trash Cli

PassAudited by ClawScan on May 1, 2026.

Overview

Trash Cli is a coherent trash-cli helper; it is not suspicious, but it can delete or permanently empty local trash and includes optional sudo and shell-alias setup steps.

Install this only if you want the agent to manage local files through trash-cli. Confirm any file paths, patterns, `trash-empty`, `trash-rm`, sudo setup, or shell startup-file edits before allowing them, because those actions can permanently remove data or change future shell behavior.

Findings (3)

Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.

What this means

Using the wrong command, path, or pattern could permanently remove files from the trash rather than keeping them recoverable.

Why it was flagged

The skill documents commands that can permanently delete all items already in the trash. This is disclosed and fits trash-cli, but it is a high-impact local file operation.

Skill content
`trash-empty` | Permanently delete trashed files ... `trash-empty                 # Remove ALL trashed files`
Recommendation

Confirm file paths and patterns before trashing or emptying; list trash contents first and avoid `trash-empty` or `trash-rm` unless the user explicitly wants permanent removal.

What this means

Running these commands changes a root-level directory and its permissions, which could affect how trash works on that system or partition.

Why it was flagged

The FAQ includes optional elevated commands to create and permission a top-level trash directory. This is purpose-related setup, but it crosses a local privilege boundary.

Skill content
`sudo mkdir --parent /.Trash` ... `sudo chmod a+rw /.Trash` ... `sudo chmod +t /.Trash`
Recommendation

Only run the sudo setup when needed for a specific partition and after confirming the exact path and permission changes.

NoteHigh Confidence
ASI10: Rogue Agents
What this means

Future shell sessions may handle `rm` differently, which can surprise users or scripts if added without clear approval.

Why it was flagged

The skill suggests optional persistent shell aliases that change future `rm` behavior. This is disclosed and even cautioned against later, but it persists beyond a single command.

Skill content
Add to `.bashrc` or `.zshrc`: ... `alias rm='trash-put'`
Recommendation

Do not let the agent edit shell startup files unless explicitly requested; prefer the warning alias shown in the documentation over replacing `rm` with `trash-put`.