Clients

v1.0.0

Build a personal client system for tracking relationships, projects, documents, and history.

2· 987·0 current·0 all-time
byIván@ivangdavila
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 match the content of SKILL.md: it describes building a local client workspace and the instructions only require creating and managing folders/files under ~/clients/. No unrelated binaries, credentials, or installs are requested.
Instruction Scope
The SKILL.md stays focused on file/folder structure, profiles, projects, documents, and logging communications in ~/clients/. However, it uses vague directives like 'Pull context' and 'surface relevant history' without specifying data sources; that could lead an agent to look beyond the ~/clients/ folder (emails, calendar, Slack, or other files) if the agent has broader permissions. The file does not explicitly instruct reading system or external services, but the wording leaves room for broader context-gathering behavior.
Install Mechanism
No install spec and no code files are present (instruction-only). This minimizes disk writes and prevents arbitrary code downloads; low install risk.
Credentials
No environment variables, credentials, or config paths are requested. The skill does not ask for unrelated secrets or external service tokens.
Persistence & Privilege
The skill does not request always:true or other elevated persistence. It is user-invocable and uses the platform defaults for invocation.
Assessment
This skill is basically a recipe for creating and maintaining a ~/clients/ folder and appears safe and coherent. Before installing or enabling it, consider: 1) Back up any existing ~/clients/ or similar folders so the skill won't overwrite data. 2) Confirm what data sources the agent is allowed to access — if you don't want it reading your email, calendar, Slack, or other files, ensure those integrations/credentials are not granted. 3) Be cautious about storing sensitive client data in plain files; consider encrypting or limiting sensitive attachments. 4) Test the skill with a dummy client to observe what the agent does when asked to 'pull context' or 'surface relevant history' so you can explicitly restrict unintended access. If you plan to connect email/Slack/calendar to get context, provide only the minimum credentials and review their scope first.

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

latestvk975x3fjgd5myzhr3wq1t411fh80y3nm

License

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

Runtime requirements

💼 Clawdis
OSLinux · macOS · Windows

Comments