customer-db

What problem does it solve?

This Skill solves the problem of losing customer context between sales-cs sessions by persisting customer records and follow-up status in a local SQLite database.

Core Features & Use Cases

• Persistent customer records: Maintains a per-peer SQLite database at ./db/customer.db with a stable schema (cs_record, primary key peer).
• Controlled field updates: Provides a safe update path to set purpose and prompt_source while always bumping updated_at, without overwriting with empty values.
• Follow-up task lifecycle: Creates, cancels, queries due tasks, expires stale tasks, and marks send/complete transitions (pending → sent_once → completed).

Use case: When a sales-cs workflow invites a lead and then needs delayed nudges, customer-db stores business_status handled by hooks, updates narrative fields when new info arrives, and schedules/executes follow-up messaging with clear state transitions.

Quick Start

Tell the AI to update the current customer’s purpose and prompt_source using the cs-update script, providing the peer from CustomerDB and the new values when you have clearer information.