agentleFS
profbernardojprofbernardoj/everclaw/skills/relationships/SKILL.md

relationships

Skill112 starsChanged 3 months agoMITView on GitHub

Relationship CRM for tracking people, connections, and context. Categories: family, close_friends, church_friends, colleagues, broader_community, strangers, bad_actors, unknown. Use to add, search, list, or update people in the user's network.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When asked about someone, search first

    line 104
  2. Distinctive:

    When adding new people, ask clarifying questions

    line 105
  3. Distinctive:

    After interactions, prompt to log them

    line 106
  4. Distinctive:

    Never sync to cloud or external services

    line 117

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Relationships CRM

Overview

Track people in the user's life with rich context. Store relationship data, interaction history, and personal details in structured memory files.

Categories

CategoryDescription
familyImmediate and extended family
close_friendsTrusted inner circle
church_friendsFriends from church community
colleaguesProfessional contacts, collaborators, business partners
broader_communityAcquaintances, community members, loose connections
strangersOne-time contacts, unknown intent
bad_actorsPeople to avoid or be cautious around
unknownNot yet categorized

Commands

Add a person

/relationship add "Firstname Lastname" --category <category> [details]

Creates a new contact file or updates existing.

List by category

/relationship list <category>

Shows all contacts in a category.

Search

/relationship search <query>

Full-text search across all contacts.

Update

/relationship update "Firstname Lastname" --field <field> --value <value>

Updates a specific field.

Note interaction

/relationship interact "Firstname Lastname" --date YYYY-MM-DD --summary "what happened"

Logs an interaction to the contact's history.

File Structure

memory/relationships/
├── family/
│   ├── family-member.md
│   └── ...
├── close_friends/
├── church_friends/
├── colleagues/
├── broader_community/
├── strangers/
├── bad_actors/
├── unknown/
└── index.json    # Quick lookup index

Contact File Format

# Firstname Lastname

## Basics
- **Category:** family
- **Relationship:** Wife
- **First met:** YYYY-MM-DD or "since childhood" etc.
- **Last contact:** YYYY-MM-DD

## Context
[Background, how we know them, what they mean to the user]

## Key Details
- Birthday: YYYY-MM-DD
- Location: City, State
- Phone: +1...
- Email: ...
- Social: @handle

## Family
- Spouse: ...
- Children: ...

## Interactions
### YYYY-MM-DD - [Title]
[What happened, key points, follow-ups]

## Notes
[Running notes, things to remember]

Workflow

  1. When asked about someone, search first
  2. When adding new people, ask clarifying questions
  3. After interactions, prompt to log them
  4. Periodically suggest categorization updates
  5. Respect privacy — never share contact info externally without permission

Integration with Memory

  • Contacts live in memory/relationships/ for context persistence
  • Key people may also be referenced in MEMORY.md for high-level context
  • Daily notes in memory/YYYY-MM-DD.md can reference contacts

Privacy

  • Contact files stay local
  • Never sync to cloud or external services
  • Malicious actors flagged in bad_actors/ with caution notes

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.