agentleFS
latour-ailatour-ai/skills/relationship-status-summarizer/SKILL.md

relationship-status-summarizer

Skill69 starsChanged 25 days agoNo licenceView on GitHub

Surface where a professional relationship stands by pulling from Gmail — last touchpoint, what was discussed, open threads, commitments, and a suggested next move. Use whenever a user wants to re-engage someone, prep for outreach, or get a quick status check before reaching out. Trigger on "where do I stand with [Name]", "catch me up on my history with [Name]", "what's my relationship with [Name]", "when did I last talk to [Person]", "what was the last thing discussed with [Name]", "should I reach out to [Person]", "help me re-engage [Name]", "what do I owe [Person]", "any open threads with [Company]", "what's my history with [Name]", or any variation of wanting to understand a relationship's current state before making a move. Also trigger when the user mentions a person's name and asks about follow-ups, last contact, or relationship warmth. Designed for BD, fundraising, and IR professionals managing large networks who need a fast, honest read on where things stand.

1 other project uses a version of this, 1 of them edited.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

≈ “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.

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.