managing-personal-crm

Maintains relationship notes and routes follow-ups from interaction evidence across configured sources.

6|Updated Jul 10, 2026
One-click install
npx skills add https://github.com/jrgilbertson/the-rookery --skill managing-personal-crm-jrgilbertson
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: managing-personal-crm
Source: https://github.com/jrgilbertson/the-rookery/tree/main/skills/managing-personal-crm
Command: npx skills add https://github.com/jrgilbertson/the-rookery --skill managing-personal-crm-jrgilbertson

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Keeping a personal CRM useful is hard: raw interactions pile up in Messages, email, and X while Person notes go stale, follow-up commitments get lost, and cleanup of duplicate or outdated contacts never happens. This Skill turns scattered interaction evidence into reviewed, durable relationship meaning without turning the CRM into an activity log. ## Core Features & Use Cases - Interaction capture and contact tracking: Reads bounded evidence from configured sources (Apple Messages via imsg, X via Grok CLI, email, meetings) and proposes monotonic updates to date_last_contacted and relationship-load-bearing prose in Obsidian Person notes. - Three operating modes: Direct mode for one-person capture and preparation, Embedded mode that returns relationship effects inside a caller workflow's bundle, and Catch-up mode for staged triage, merge, and reconstruction of Person-note collections. - Approval-gated writes: Every effect (Person note edit, Task creation, merge, delete) is presented as a numbered proposal, rechecked against the canonical destination, applied once via the Obsidian CLI, and read back with an honest outcome label. - Use Case: Before a meeting, ask for a close-up on one person; the Skill combines their canonical Person note with fresh source context into a brief, and proposes any warranted follow-up Task for your approval. ## Quick Start Ask the agent to capture your recent interaction with a specific person and update their Person note with any durable meaning or follow-up task.

Frequently Asked Questions about managing-personal-crm

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I capture a relationship interaction into my personal CRM?▼

Ask the agent to capture the interaction in direct mode. It reads bounded evidence from configured sources, resolves identity conservatively, and presents a numbered review bundle of proposed Person-note or Task effects that you approve, edit, defer, or skip individually.

How do I clean up or merge duplicate Person notes in Obsidian?▼

Request a catch-up run. The Skill confirms a source inventory, triages every Person note into dispositions like active, dormant, merge, or delete, then reconstructs retained relationships. Merges and deletes require separate approved actions and a verified reversible trash probe.

Does this personal CRM skill work with Apple Messages?▼

Yes, when the host configures the imsg CLI as the local Apple Messages source with macOS Full Disk Access. It performs read-only chat, history, search, and stats queries with explicit limits, and never sends messages or performs write operations.

Can the skill read X (Twitter) interactions for contact tracking?▼

Yes, through an installed Grok CLI or a permitted read-only X provider. It uses bounded public search and fetch for relationship evidence only, never posts or mutates X, and marks X unavailable if authentication or queries fail.

When should I not use this relationship management skill?▼

Do not use it for plain contact lookup, generic writing or communication tasks, broad email or meeting processing, simple task creation, or chief-of-staff reviews without relationship relevance. Those requests stay with their narrower owning workflows.

Why does the skill report Partial or Unable to determine safely?▼

Those endings appear when a required source is unavailable, a query hits its result limit, or identity cannot be resolved conservatively. The Skill narrows only the affected conclusions rather than fabricating contact, memory, or writes.