Leads

v3.4.1

Manage sales leads locally. Use when adding prospects, scoring leads, setting follow-ups, tracking conversions, or viewing funnels.

0· 252·0 current·0 all-time
bybytesagain4@xueyetianya
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description match the implementation: commands add/list/score/follow-up/convert/pipeline are implemented in scripts/script.sh and store data in ~/.leads/leads.json. Required tools (bash, python3) are appropriate for the stated purpose.
Instruction Scope
SKILL.md instructs the agent to run the shipped script and all data is stored locally. The script reads/writes only ~/.leads/leads.json and does not reference other system paths or external endpoints in the visible sections. Note: data is stored as plain JSON (unencrypted), so it will contain any PII you add.
Install Mechanism
No install spec or remote downloads; the skill is instruction-only with a bundled script. Nothing is fetched from external URLs or written outside the user's home directory in the visible code.
Credentials
The skill declares no required environment variables or credentials and the code does not access secrets or unrelated env vars. It does rely on HOME (to build ~/.leads) which is normal and proportional.
Persistence & Privilege
always is false and the skill is user-invocable — standard. The skill does not request permanent agent-wide privileges or modify other skills in the visible code.
Assessment
This skill appears to do what it says: a local, file-based CRM implemented in the included script. Before installing, consider: (1) All lead data is stored unencrypted at ~/.leads/leads.json — avoid storing highly sensitive information there or restrict the file permissions (chmod 600). (2) Review the full scripts/script.sh in the installed package (the provided listing was truncated near the end), since I reviewed the visible portions only; any hidden/remaining lines could change the assessment. (3) This runs with your user privileges, so inspect the code for unwanted operations and back up/delete the JSON file if you stop using the skill. If you want encrypted storage or remote sync, treat that as a separate integration and verify what credentials it would require.

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

latestvk97acevjd97v1gwyarfy5e4wph833sdf

License

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

Comments