Personal CRM

What it does

When your agent uses it

• Says who do I owe a follow-up to
• Did I last talk to
• Track this contact
• Log this conversation

Example prompts

• “who do I owe a follow-up to,”
• “when did I last talk to,”
• “personal CRM,”
• “/personal-crm”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

1. 1Who (if ambiguous, ask)
2. 2When (default to today)
3. 3Channel (call / email / DM / coffee / dinner / event)
4. 4What was discussed — let the user dump notes, you structure them
5. 5Anything you committed to
6. 6Anything they committed to
7. 7What you learned about them (a new project, a family update, a frustration — anything that should go in the Context section)

What it can do on your machine

Read from SKILL.md and the folder at commit fdbf39b. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  No URLs in SKILL.md.

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names no API keys, tokens, secrets or passwords.

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Personal CRM loads about 1.6k tokens when it runs. Until then it costs about 146 tokens; SKILL.md has 584 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~146

When it runs · the whole SKILL.md, loaded when a task matches

~1.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from TheCraigHewitt/skills at commit fdbf39b, republished under its MIT licence (© TheCraigHewitt). 584 words, ~1,567 tokens.

name

personal-crm

description

Maintain a personal CRM — track relationships, last-touch dates, follow-ups owed, context from past conversations, and who deserves a check-in. Use this whenever the user says 'who do I owe a follow-up to,' 'when did I last talk to,' 'personal CRM,' 'track this contact,' 'log this conversation,' 'who should I check in with,' 'add [name] to my contacts,' or asks about their relationships and follow-up history. The skill maintains a structured `contacts/` folder with one markdown file per person, automatically surfaces follow-ups, and pulls context before any meeting.

# [Name]

**Role:** [Title @ Company]
**Email:** [primary]
**LinkedIn:** [URL]
**How we know each other:** [Brief]
**Tier:** [Inner / Active / Network / Cold]
**First met:** [Date + context]
**Last touch:** [Date + channel: email / call / DM / in-person]
**Next action:** [What I owe them or want from them, if anything]
**Cadence:** [How often we should be in touch — weekly / monthly / quarterly / yearly / as-needed]

## Context
The 3-5 things worth remembering about this person. Family, hobbies, what they're working on, what they care about. Not for psyops — for being a thoughtful person who pays attention.

## Recent conversations
Reverse-chronological log. For each:
### YYYY-MM-DD — [channel]
What we talked about. What I committed to. What they shared. What I should follow up on.

## Promises made
Open commitments I've made to them, with target dates.

## Promises received
Things they said they'd do. Don't nag — but useful to remember.

# Follow-ups owed — [date]

## Overdue
- **[Name]** ([days overdue]): [promise / next action]

## Due this week
- **[Name]** ([day]): [promise / next action]

## Coming up
- **[Name]** ([date]): [promise / next action]

# Check-ins worth making — [date]

## Inner circle going cold
- **[Name]** — last touch [X days/weeks ago]. Cadence: [weekly/monthly]. Suggested move: [specific opener based on Context]

## Active circle overdue
- ...

## Worth reigniting
- **[Name]** — last touch [months/years ago]. Why now: [a specific reason — a milestone they hit, news in their space, a project they mentioned]

# Pre-meeting: [Name] — [meeting time]

**Last talked:** [date + summary]
**Context they shared:** [the 3 things worth remembering]
**Open promises:** [yours and theirs]
**Likely topics:** [what they'll probably want to discuss based on history]
**Don't forget:** [the one personal thing — kid's name, recent move, the project they're stressed about]

© TheCraigHewitt, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in cowork/personal-crm of TheCraigHewitt/skills.

• SKILL.md
• evals/evals.json

Open the folder on GitHubat commit fdbf39b