Personal CRM

**Judgement:** This is a well-architected, high-quality personal CRM skill that’s clearly designed around real-world relationship maintenance rather than generic to-do management. Its two-file design and conversational flows should work smoothly in most OpenClaw-style agent environments and scale to moderately large personal networks. **Key strengths:** - Strong, domain-specific data model (tiers, relationship types, birthdays, standing events, history). - Smart storage strategy (NETWORK / NETWORK-ACTIVE) for good performance and token efficiency. - Very user-friendly interaction patterns that avoid guilt, nagging, or robotic reminders. - Clear maintenance routines (weekly refresh, daily briefings) that agents can plug into. **Main risks / limitations:** - **User discipline dependency:** Accuracy and usefulness depend on the user actually doing weekly refreshes and logging touchpoints; the system can drift if neglected. - **Integration fragility:** Calendar/email import flows assume certain tools/CLIs (e.g., Google Calendar, Facebook exports). In environments without these, those features become manual-only. - **Privacy sensitivity:** Centralizing detailed personal relationship data (including birthdays, contact info, and history) in local files requires that the user’s workspace be secure; misuse or misconfiguration of any external integrations (email, calendar, platform search) could expose sensitive relationship information. - **Relational nuance:** While nudges are gentle, any automated relationship advice can misread complex social contexts; users should treat suggestions as prompts, not prescriptions. **Best-fit scenarios:** - Individuals who want a lightweight, text-file-based personal CRM embedded in their AI agent rather than a separate SaaS tool. - Knowledge workers, freelancers, or founders who need to maintain a warm professional network over months/years. - People who frequently forget birthdays or drift out of touch with friends/family and want gentle, low-pressure reminders. - Users comfortable with simple file-based workflows and occasional manual maintenance (e.g., a short Monday review), who care about privacy and keeping data local.