crmlisted

# Personal CRM Manage contacts, log interactions, track relationship health, and surface follow-up priorities. ## Workspace-Aware Paths This skill works across both CEO and exec workspaces. On startup, read `.workspace-identity.json` from the workspace root to determine workspace type. | Resource | CEO Workspace | Exec Workspace | |----------|--------------|----------------| | Personal contacts | `crm/contacts/` | `personal/crm/contacts/` | | Tribe contacts (shared) | `crm/contacts/` (type: tribe*) | `corporate/crm/contacts/` (read-only) | | CRM config | `crm/config.md` | `corporate/crm/config.md` | | People index | `context/people.md` | `context/people.md` (personal root) | All path references below (e.g., `crm/contacts/`) should be resolved using this mapping based on the detected workspace type. **Tribe contacts are corporate-wide.** In exec workspaces, Tribe member contacts live in `corporate/crm/contacts/` (read-only, synced from CEO workspace). When searching or displaying contacts, always check BOTH personal and corporate CRM directories. When logging interactions for Tribe members in exec workspaces, log to the personal copy if it exists, otherwise note that the contact is read-only corporate. ## Variables - `$ARGUMENTS` — Subcommand and parameters. Format: `[action] [details]` ## Actions Parse the first word of `$ARGUMENTS` to determine the action: **Read `references/actions.md` before you run any action below.** It holds the full step sequence, the canoni