agentleFS
Sign inStart free
latour-ailatour-ai/skills/lp-meeting-prep-brief/SKILL.md

lp-meeting-prep-brief

Skill69 starsChanged 26 days agoNo licenceView on GitHub

Compile a one-page briefing before any LP meeting: the relationship timeline and who-knows-whom from CRM and email history, the LP's current holdings across the firm's funds with performance framed in the metrics they use, open items promised or requested in prior conversations, recent news about their organization worth acknowledging, and the five questions they are most likely to ask — each with a suggested answer — plus anything sensitive the partner should raise proactively. For IR, fundraising, and BD teams at private equity, private credit, hedge fund, real assets, and venture managers, and the partners they send into the room. Trigger on phrases like "prep me for the [LP] meeting," "briefing for [pension] on Thursday," "what do I need to know before I see [LP]," "meeting prep for [investor]," "build the one-pager for tomorrow's LP call," or when a user names a scheduled LP meeting and attaches relationship materials. Do NOT use for capturing what happened after the meeting — use the call-transcript-followup skill. Do NOT use for a multi-meeting conference schedule — use the conference-prep-planner skill. Do NOT use for a deep profile of one individual — use the professional-profile-brief skill. LP data is confidential; assume a firm-approved AI environment.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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.

Check your setup, free