Relationship Intelligence

v1.0.0

Personal CRM and relationship intelligence. Extracts contacts from conversations, tracks commitments, detects cooling relationships, delivers morning briefs,...

0· 206·0 current·0 all-time
byMukund Kunapareddy@mukund2
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
medium confidence
Purpose & Capability
Name/description (personal CRM / relationship intelligence) align with the instructions: it stores contacts, commitments, reminders, relationship graphs, scores, and produces briefs. sqlite3 is appropriate for the local DB. Optional Google integration (calendar/gmail/contacts) is coherent with the described features.
Instruction Scope
SKILL.md stays within CRM responsibilities (saving contacts, tracking commitments, creating reminders, briefings). It asks to create and use a SQLite DB at ~/.local/share/memi-ri/memi.db and to learn patterns over time. A few behaviors are underspecified: how photos/screenshots and Gmail data are accessed (user-provided vs. agent-initiated) and what exact data is sent to the configured LLM provider. Those are privacy-relevant but not inherently incoherent with the stated purpose.
Install Mechanism
There is no install spec and no code files — lowest install risk. The skill expects local sqlite3 and optionally a 'gog' binary for Google integrations. The origin and trustworthiness of 'gog' are not described in SKILL.md/README, so if you enable Google features verify what 'gog' is before installing.
Credentials
The skill declares no required environment variables or credentials, which is reasonable for a local DB-first CRM. It references Google OAuth for integrations but doesn't require explicit env vars (presumably 'gog' handles auth). There's a minor inconsistency in the registry metadata: the extracted data shows 'gog' under 'required (at least one)' while README says gog is optional. Confirm whether Google access will prompt an OAuth flow and where tokens are stored.
Persistence & Privilege
The skill persists personal data locally in a DB under the user's home directory (expected for a CRM). always:false (not force-installed) and normal model invocation are fine. Note: the skill will accumulate sensitive contact data over time — verify your LLM provider and account choice because personal data may be sent there as part of prompts/briefs.
Assessment
This skill appears to be what it claims: a local personal CRM that stores contacts and generates briefs. Before installing, confirm two things: (1) whether the optional 'gog' binary is truly optional for the features you want and where it comes from (it handles Google Calendar/Gmail/Contacts access), and (2) how and when data will be sent to your configured LLM provider — the skill will store sensitive contact and interaction data locally, but prompts and briefs may include that data when calling the model. If you plan to enable Google integrations, inspect and trust the 'gog' tool and its OAuth storage. If privacy is a priority, consider restricting Google integrations and reviewing what sample prompts/briefs the skill will send to the model.

Like a lobster shell, security has layers — review code before you run it.

latestvk974na2jtkmxe9kvran7173mrs82h2zy

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

🤝 Clawdis
Binssqlite3
Any bingog

Comments