Client Relationship Manager

Lightweight AI-native CRM for solopreneurs and freelancers. Track clients, relationships, follow-ups, deal stages, and interaction history in plain text file...

Security Scan

The skill is a coherent plain-text CRM, but it asks you to inject standing instructions into your agent/system prompt (detected as a prompt‑override pattern) which is disproportionate and could grant persistent control — proceed with caution.

Purpose & Capability

The name/description (a plain-text-file CRM for solopreneurs) matches the instructions: create crm/ tree, maintain client files, pipeline.md, follow-ups.md, and have the agent read/update those files. There are no unrelated required binaries, env vars, or install steps. One note: the SKILL.md recommends adding a CRM protocol to AGENTS.md or the system prompt — that recommendation expands the skill's operational scope beyond simple file manipulation (see instruction_scope).

Instruction Scope

Most runtime instructions are appropriate for a text-file CRM (read/write files in crm/, prepare briefs, generate summaries). However, the SKILL.md explicitly instructs the user to add a persistent CRM protocol to AGENTS.md or the system prompt, which effectively modifies agent/system-level instructions and can override or steer the agent's behavior across contexts. The pre-scan flagged a 'system-prompt-override' pattern in the SKILL.md. That standing instruction is out-of-band for a file-based CRM and is a notable prompt-injection/persistence risk.

Install Mechanism

No install spec and no code files — instruction-only skill. This minimizes installation risk because nothing is downloaded or written by an installer. The runtime surface is the text instructions the agent follows and the workspace files it reads/writes.

Credentials

The skill requests no environment variables, credentials, or config paths (proportionate for a local text-file CRM). That said, the guidance to add the CRM Protocol into AGENTS.md or the system prompt effectively asks you to change agent configuration (a privileged location). While no secrets are requested, modifying agent prompts/config is a sensitive action and should be treated like granting elevated, persistent behavior to the agent.

Persistence & Privilege

Metadata shows always:false and no autonomous-disable flag — normal. But the SKILL.md asks the user to add persistent instructions to AGENTS.md or the system prompt, which gives the skill-like behaviour permanence outside the normal skill registry controls. This increases blast radius because those instructions can affect all future agent interactions; combined with the detected prompt-override pattern, this is the main risk factor.

Scan Findings in Context

[system-prompt-override] unexpected: The SKILL.md explicitly tells the user to add a 'CRM Protocol' into AGENTS.md or the system prompt so the agent will follow rules when managing clients. Asking users to add standing instructions to the system prompt is not necessary for a file-based CRM and looks like a prompt-override pattern the scanner flagged.

What to consider before installing

This skill otherwise appears coherent for managing plain-text CRM files, but do NOT blindly paste the provided 'CRM Protocol' into your system prompt or global AGENTS.md. Adding standing instructions to the system prompt effectively gives persistent control over your agent's behavior and can be abused. Safer steps: (1) Keep the CRM files in a dedicated workspace and only grant the agent file read/write rights for that directory; (2) use per-invocation user prompts (e.g., ask the agent to 'follow CRM protocol for this task') instead of modifying the global system prompt; (3) require manual confirmation before any file write (the SKILL.md already recommends this — keep it); (4) avoid storing secrets (passwords, API keys, payment details) in the CRM files; (5) verify the skill source/author before trusting long-term use (the registry metadata lacks a homepage and repo link — inspect theorigin or test in an isolated sandbox first). If you want higher assurance, ask the publisher for a canonical repo or signed release you can review.

by The Agent Ledger

A lightweight, AI-native CRM for solopreneurs and freelancers. No SaaS subscription. No monthly seat fees. Just plain text files your agent can read, update, and reason over — with you keeping full control of your data.

---

What This Skill Does

• Maintains structured client records in plain text
• Tracks deal stages, interaction history, and follow-up queues
• Prepares meeting briefs from client context
• Surfaces overdue follow-ups automatically
• Generates pipeline snapshots and revenue forecasts
• Stays out of the way when you don't need it

---

Setup (5 Steps)

Step 1: Create Your CRM Directory

crm/
├── clients/          # One file per client
├── pipeline.md       # Active deals and stages
├── follow-ups.md     # Pending follow-up queue
└── README.md         # Index of all clients

Ask your agent to create this structure:

"Set up a CRM directory at crm/ with subdirectories for clients, and files for pipeline.md and follow-ups.md."

---

Step 2: Add Your First Client Record

Each client lives in crm/clients/[client-slug].md. Use this template:

# [Client Name]
**Company:** [Company or "Individual"]
**Contact:** [Primary contact name]
**Email:** [email]
**Phone:** [phone — optional]
**Timezone:** [their timezone]
**Introduced:** [YYYY-MM-DD]
**Source:** [How you met — referral, cold outreach, inbound, etc.]
**Tags:** [industry, service-type, etc.]

## Status
**Stage:** [Lead / Prospect / Active / Paused / Closed-Won / Closed-Lost]
**Value:** [$X/project | $X/month | TBD]
**Next Action:** [What needs to happen next]
**Next Action Due:** [YYYY-MM-DD]

## Background
[2-3 sentences on who they are, what they do, what problem they're trying to solve]

## Our Work Together
[What service/product you're providing or discussing]

## Interaction Log
### YYYY-MM-DD — [Medium: email/call/meeting/message]
[Brief summary of what was discussed, decided, or agreed]

### YYYY-MM-DD — [Medium]
[...]

---

Step 3: Set Up Your Pipeline

crm/pipeline.md tracks all active deals in one view:

# Pipeline
_Last updated: YYYY-MM-DD_

## Active Deals

| Client | Stage | Value | Next Action | Due |
|--------|-------|-------|-------------|-----|
| [Name] | Proposal Sent | $X | Follow up if no response | YYYY-MM-DD |
| [Name] | Negotiating | $X | Send revised scope | YYYY-MM-DD |
| [Name] | Active | $X/mo | Monthly check-in | YYYY-MM-DD |

## Pipeline Summary
- **Total pipeline value:** $X
- **Weighted forecast (50% close rate):** $X
- **Active client MRR:** $X

## Recently Closed
| Client | Outcome | Value | Date |
|--------|---------|-------|------|
| [Name] | Won | $X | YYYY-MM-DD |
| [Name] | Lost | — | YYYY-MM-DD |

---

Step 4: Set Up Your Follow-Up Queue

crm/follow-ups.md is your daily action list:

# Follow-Up Queue
_Last updated: YYYY-MM-DD_

## Overdue
- [ ] **[Client Name]** — [What to do] _(was due YYYY-MM-DD)_

## Due Today
- [ ] **[Client Name]** — [What to do]

## Due This Week
- [ ] **[Client Name]** — [What to do] _(YYYY-MM-DD)_

## Due Next Week
- [ ] **[Client Name]** — [What to do] _(YYYY-MM-DD)_

## Someday / No Date
- [ ] **[Client Name]** — [Reconnect when budget opens]

---

Step 5: Give Your Agent the Standing Instructions

Add to your AGENTS.md or system prompt:

## CRM Protocol

When I mention a client or prospect:
1. Check if they have a record in crm/clients/ — if not, offer to create one
2. After any meeting or call I describe, offer to log an interaction entry
3. If I ask for a "CRM review" or "pipeline check," read crm/pipeline.md and crm/follow-ups.md and report: overdue items, upcoming actions, pipeline value, and any clients I haven't touched in 30+ days
4. If I say "prep me for [client]," read their client file and give me: background, last interaction, current stage, and what I should know before talking to them

Never auto-update files without confirming the entry first.

---

Usage Patterns

Meeting Prep

"Prep me for my call with Acme Corp at 2pm."

Your agent reads crm/clients/acme-corp.md and gives you:

• Who you're talking to and their background
• Current deal stage and value
• Last interaction summary
• What was agreed or outstanding
• Suggested talking points based on next action

Log an Interaction

"Just got off a call with Sarah at Designworks. She liked the proposal but wants a 10% discount. Follow up Friday."

Your agent drafts the interaction log entry and updates the next action + due date. You confirm before it writes.

CRM Review

"Give me a CRM review."

Your agent reads pipeline.md and follow-ups.md and reports:

• Overdue follow-ups
• Actions due today and this week
• Pipeline summary (total value, count by stage)
• Clients not touched in 30+ days (potential churn risk)
• Any deals with stale "next action" dates (no movement in 14+ days)

Add a New Lead

"Add Jane from TechStartup as a lead. Met her at a conference. She's interested in monthly consulting. Her email is [e-mail]."

Your agent creates crm/clients/techstartup-jane.md using the template, fills in what you've told it, and flags the fields that need more information.

Weekly Pipeline Update

"Update the pipeline."

Your agent reads all client files, cross-references with pipeline.md, and proposes updates for any stages that appear stale or inconsistent with recent interaction logs.

---

Deal Stages (Customize These)

Stage	Definition
Lead	Identified as a potential client, no real conversation yet
Prospect	Had initial conversation, they know what you offer
Qualified	Confirmed budget, timeline, and decision-maker involvement
Proposal Sent	Formal proposal or scope submitted, awaiting response
Negotiating	Active discussion on terms, scope, or price
Active	Paying client, work in progress
Paused	Project on hold — agreed to revisit later
Closed-Won	Project complete or ongoing retainer secured
Closed-Lost	Didn't move forward — log the reason

Adapt these to your sales process. The stage names in client files and pipeline.md should match.

---

Automated Follow-Up Review (Optional)

Add a periodic check to your HEARTBEAT.md:

## CRM
- Read crm/follow-ups.md and flag any overdue items
- Check for clients in crm/clients/ with no interaction in 30+ days
- If pipeline hasn't been updated in 7 days, flag for review

Or set a weekly cron:

openclaw cron add \
  --name "weekly-crm-review" \
  --cron "0 9 * * MON" \
  --model "anthropic/claude-3-5-haiku-20241022" \
  --session isolated \
  --message "Read crm/pipeline.md and crm/follow-ups.md. Report: overdue follow-ups, pipeline value by stage, clients not touched in 30+ days, and deals with no movement in 14+ days. Be concise." \
  --announce \
  --to "[YOUR_TELEGRAM_CHAT_ID]" \
  --tz "America/Chicago"

---

Customization Options

Industry-Specific Stage Names

Replace the default stages with language that fits your context:

• Freelancers: Inquiry → Brief → Quoted → In Progress → Review → Invoiced → Paid
• Coaches: Discovery → Enrolled → Active → Alumni
• Agencies: RFP → Scoping → Proposal → Negotiation → Onboarding → Retained

Client Tiers

Add a tier field to segment by relationship priority:

**Tier:** A (Top client / referral source) | B (Active, standard) | C (Occasional) | D (Dormant)

Revenue Tracking

Extend pipeline.md with a monthly revenue section:

## Revenue (Current Month)
- Invoiced: $X
- Collected: $X
- Outstanding: $X
- Projected (next 30 days): $X

Referral Tracking

Add a referrals section to client files:

## Referrals Sent
- Referred [Name] to [Client] on [date] — [outcome if known]

## Referrals Received From This Client
- [Name/Company] — [date] — [outcome]

---

Integration With Other Agent Ledger Skills

Skill	How They Work Together
solopreneur-assistant	Include pipeline summary in your weekly business dashboard
inbox-triage	Flag emails from pipeline clients as higher urgency
project-tracker	Link active clients to their project files for unified status
decision-log	Log major client decisions (pricing changes, scope decisions)
content-calendar	Track case study opportunities from Closed-Won clients

---

Troubleshooting

Problem	Fix
Agent doesn't know about a client	Check that client file is in crm/clients/ and agent has access to the directory
Pipeline gets stale	Add CRM review to your HEARTBEAT.md or set a weekly cron
Too many files to manage	Use README.md in crm/ as a client index with quick status for each
Agent writes to files without confirming	Reinforce "never auto-update without confirming" in your AGENTS.md
Deal stages are confusing	Pick 4-5 stages max and define them clearly in your AGENTS.md

---

Privacy Note

All CRM data lives locally in your workspace. Nothing is synced, shared, or processed externally unless you explicitly ask your agent to send something. Your client data stays yours.

If you're subject to client confidentiality obligations (legal, financial, healthcare), keep this in a local-only workspace and avoid syncing to cloud-backed directories without reviewing your obligations.

---

About This Skill

Built by The Agent Ledger — practical guides and tools for AI-augmented solopreneurs.

Subscribe for new skills, guides, and subscriber-only content at theagentledger.com.

License: CC-BY-NC-4.0 — free for personal use, not for resale or redistribution.

---

Disclaimer: This skill provides a framework for organizing information. It does not replace professional CRM software for enterprise use cases, and the author makes no warranty as to fitness for any particular purpose. Use responsibly and in compliance with any applicable data protection laws and professional obligations.