Client Relationship Manager
ReviewAudited by ClawScan on May 10, 2026.
Overview
Prompt-injection indicators were detected in the submitted artifacts (system-prompt-override); human review is required before treating this skill as clean.
Use this only if you are comfortable managing CRM data in local plain-text files. Keep the crm/ folder protected, review edits before approving them, avoid storing secrets or passwords there, and keep any AGENTS.md/system-prompt or cron setup scoped to where you actually want the CRM behavior. The provided SKILL.md text was truncated, so review the full file before installing global standing instructions. ClawScan detected prompt-injection indicators (system-prompt-override), so this skill requires review even though the model response was benign.
Findings (3)
Artifact-based informational review of SKILL.md, metadata, install specs, static scan signals, and capability signals. ClawScan does not execute the skill or run runtime probes.
The agent may keep offering CRM actions whenever client-related topics appear, even outside the immediate setup conversation.
This asks the user to install persistent standing instructions that make the agent react to client/prospect mentions. It is disclosed and includes a confirmation requirement, but it can affect future agent behavior until removed.
Add to your `AGENTS.md` or system prompt: ... When I mention a client or prospect: ... Never auto-update files without confirming the entry first.
Prefer project-scoped AGENTS.md instructions over global/system-prompt changes, and keep the confirmation rule in place.
Incorrect edits could affect your pipeline, follow-up queue, or client history.
The skill relies on local file mutation for CRM records. This is purpose-aligned and explicitly requires user confirmation before writing.
Your agent drafts the interaction log entry and updates the next action + due date. You confirm before it writes.
Review proposed edits before approving them, and consider using backups or version control for the crm/ directory.
Client and business information may be exposed to anyone or any tool with access to the CRM folder.
The CRM stores personal contact information, business value, and relationship history in persistent plain text that agents can later read and reason over.
Each client lives in `crm/clients/[client-slug].md` ... **Email:** [email] ... **Phone:** [phone — optional] ... **Value:** [$X/project | $X/month] ... ## Interaction Log
Protect the crm/ directory, avoid storing passwords or API keys in it, and be careful when syncing, sharing, or backing up these files.