Clipboard Memory

v1.2.1

Recall what the user copied on this Mac via the local clipmem archive — text, commands, URLs, file paths, HTML, images, PDFs. Triggers on requests like "what...

0· 27·0 current·0 all-time
byTristan Manchester@tristanmanchester
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description claim clipboard recall on macOS and the skill only requires the clipmem binary and macOS paths; those needs match the stated functionality (no unrelated cloud credentials or unrelated binaries).
Instruction Scope
SKILL.md instructs the agent to run the clipmem CLI, inspect a local SQLite archive, export raw bytes to disk, restore to the clipboard, and run a local setup-check script — all consistent with a clipboard-recall tool and limited to local filesystem/cli actions. There are no instructions to send data to remote endpoints or to read unrelated credentials.
Install Mechanism
Install options are Homebrew (tristanmanchester/tap/clipmem) or cargo. These are expected for a native CLI but the Homebrew tap is a third-party tap (not core/homebrew) — verify you trust the tap/author before installing. No arbitrary download URLs or obscure hosts are used.
Credentials
The skill requests no environment variables, credentials, or unrelated config paths. It uses the standard macOS clipboard DB path by default, which is proportionate to the stated purpose.
Persistence & Privilege
always:false and default model invocation behavior. The skill does not request permanent platform-wide privileges or alter other skills' configs. It may write exported files to disk via clipmem export (expected behavior).
Assessment
This skill appears to do exactly what it says: query a local clipboard archive via the clipmem CLI. Before installing, consider: 1) clipmem will expose whatever you've copied (passwords, tokens, private images) — only install/trust this if you are comfortable the binary and its Homebrew tap/author are trustworthy; 2) export/restore actions can write files or restore data to your clipboard (avoid using --force or unsafe output paths); 3) prefer running the provided scripts and inspecting the brew tap or cargo package source yourself if you want extra assurance. If you want to limit risk, only allow the skill to be user-invoked (not autonomous) and verify the clipmem formula source before installation.

Like a lobster shell, security has layers — review code before you run it.

latestvk97c0a5re5jt4qd2h01zw873qh851sy6

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

📋 Clawdis
OSmacOS
Binsclipmem

Install

Install clipmem (brew)
Bins: clipmem
brew install tristanmanchester/tap/clipmem

Comments