Archive
v1.0.0Capture and preserve content as intelligent snapshots with semantic search, automatic extraction, and proactive resurfacing.
⭐ 0· 919·4 current·4 all-time
byIván@ivangdavila
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Benign
high confidencePurpose & Capability
Name/description (archive + semantic search + resurfacing) match the instructions: create ~/archive/, extract and store content, provide semantic search and limited proactive suggestions. No unrelated credentials, binaries, or install steps are requested.
Instruction Scope
Instructions stay largely within the stated purpose (capture, store, search, resurface). They do instruct the agent to 'fetch full content (web_fetch or browser)' which implies network access when the user requests URL capture; the SKILL.md also references using 'user history' and semantic matching but does not instruct reading unrelated system files or secret env vars. Note: the mechanism for generating semantic matches (local model vs external embedding service) is unspecified.
Install Mechanism
No install spec or code files — instruction-only skill. Nothing will be downloaded or written by an installer beyond the archive directory the skill itself creates on first use.
Credentials
No required environment variables, credentials, or config paths are declared. The requested access (filesystem under ~/archive/ and optional local PDF paths) is proportional to the stated functionality.
Persistence & Privilege
Not always:true and does not request elevated or cross-skill configuration. It writes/reads only its own archive files per instructions and describes opt-out behavior for resurfacing.
Assessment
This skill appears to be what it says: an on-device archiver that stores items under ~/archive/ and provides semantic search/resurfacing. Before installing, consider: 1) Network fetching: when you ask it to archive a URL, the agent will fetch remote content — confirm whether that fetch happens locally or via any third-party tool (to avoid unintended content leakage). 2) Local storage: everything is stored in ~/archive/ (full text, metadata and any local file paths) — avoid archiving secrets, credentials, or private files you don't want persisted. 3) Semantic processing: the skill is vague about how embeddings/searching are implemented; if it uses an external service you may need to supply API keys (none are requested now), so verify where processing occurs. 4) Resurfacing: proactive suggestions are limited but enabled by default; use the opt-out commands described if you prefer search-only. If you want higher assurance, ask the publisher how web fetches and semantic indexing are performed and whether any third-party endpoints are contacted during capture or search.Like a lobster shell, security has layers — review code before you run it.
latestvk973g123v1k5rz13npdj8p69vh818veg
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📦 Clawdis
OSLinux · macOS · Windows