Documents
v1.0.0Build a personal document system for instant access to IDs, contracts, certificates, and important files.
⭐ 4· 2.7k·26 current·28 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 and description match the instructions: the SKILL.md describes creating a ~/docs workspace, cataloging documents, and surfacing locations/expiry dates. There are no unexpected dependencies, environment variables, or external services requested.
Instruction Scope
Instructions are limited to creating and organizing a local ~/docs workspace and surfacing references. Two issues to note: (1) a minor path inconsistency — the doc instructs creating ~/docs/ but example digital paths use ~/documents/scans/ — which could cause confusion; (2) while the guidance advises storing sensitive numbers as 'references, not plain text', many examples (index/emergency access) imply storing or surfacing sensitive identifiers. The SKILL.md does not instruct the agent to read unrelated system files or send data externally.
Install Mechanism
No install spec or code files — instruction-only. Nothing will be written by an installer and no external packages are pulled.
Credentials
The skill requests no environment variables, credentials, or config paths, which is proportionate to a local document cataloging tool.
Persistence & Privilege
always is false and the skill can be invoked autonomously (the platform default). Because the skill's purpose is to surface personal and potentially sensitive information, users should be careful about granting the underlying agent filesystem access or allowing fully autonomous runs that could read ~/docs. The skill itself does not request privileged or cross-skill configuration changes.
Assessment
This skill is coherent and low-risk from a technical footprint perspective, but it deals with sensitive personal data. Before installing or using it: (1) confirm whether the agent will have filesystem access and whether you trust it to read ~/docs; (2) store actual numbers and scanned documents in encrypted storage (the skill suggests this but doesn't provide tools) or keep those secrets in a password manager rather than plain files; (3) fix the folder-path inconsistency (~/docs vs ~/documents) and test on non-sensitive sample files first; (4) consider disabling autonomous invocation or requiring explicit user approval before the agent reads or reports sensitive entries; (5) verify the agent will not upload documents to external endpoints — if network access is allowed, audit where data is sent; (6) keep backups and an access log for any sensitive document store. If you want, I can suggest specific encryption tools or a safer folder layout and access policy.Like a lobster shell, security has layers — review code before you run it.
latestvk971epvakehap82ccmz37tyrcs80yxhk
License
MIT-0
Free to use, modify, and redistribute. No attribution required.
Runtime requirements
📄 Clawdis
OSLinux · macOS · Windows