lp-update-generator
Skill69 starsChanged 24 days agoNo licenceView on GitHub
Draft a quarterly LP update letter from raw fund inputs. Use this skill whenever the user wants to write or draft an LP update, investor letter, quarterly letter, fund update, or limited partner communication. Trigger on phrases like "draft my LP update," "quarterly investor letter," "write our Q[X] update," "LP communication," "investor update," "write to our LPs," or "quarterly letter to investors." Also trigger when the user provides fund performance data, portfolio updates, or market commentary and asks to turn them into an investor communication. This skill is format-agnostic — it does not depend on attachments, a specific data format, or a fixed set of inputs.
In this repository55 other files it gives its agents.
- ai-workflow-auditSkill
- ambition-upgradeSkill
- call-transcript-followupSkill
- cim-first-passSkill
- claim-sentiment-extractorSkill
- coinvest-triage-memoSkill
- conference-attendee-screenSkill
- conference-prep-plannerSkill
- credit-agreement-covenant-extractorSkill
- ddq-answer-library-curatorSkill
- ddq-red-flag-scannerSkill
- ddq-response-drafterSkill
- deal-pipeline-tracker-updaterSkill
- earnings-call-extractorSkill
- executive-briefingSkill
- expert-call-question-guideSkill
- expert-call-synthesisSkill
- fomc-statement-diffSkill
- fund-doc-consistency-checkerSkill
- fund-marketing-one-pagerSkill
- fund-news-alertSkill
- hedge-fund-diligenceSkill
- hundred-day-plan-drafterSkill
- ic-memo-drafterSkill
- ic-minutes-generatorSkill
- ic-question-anticipatorSkill
- inbox-triageSkill
- intro-email-generatorSkill
- investment-folder-organizerSkill
- investment-podcast-analyzerSkill
- investment-skill-creatorSkill
- key-debates-ledgerSkill
- linkedin-post-generatorSkill
- lp-meeting-prep-briefSkill
- manager-ai-practices-diligenceSkill
- marketing-compliance-prescreenSkill
- market-map-builderSkill
- market-sizing-builderSkill
- network-referral-path-mapperSkill
- pe-nda-reviewSkill
- performance-attribution-narratorSkill
- principal-background-briefSkill
- professional-profile-briefSkill
- public-company-first-passSkill
- public-co-unit-economicsSkill
- quarterly-letter-synthesizerSkill
- regulatory-exam-binderSkill
- relationship-status-summarizerSkill
- sellside-research-triageSkill
- side-letter-term-extractorSkill
- teach-meSkill
- tear-sheet-private-coSkill
- thesis-red-teamSkill
- waterfall-carry-checkerSkill
- weekly-market-recap-writerSkill
The file
We split this skill into the rules it gives an agent
9 rules. About 0 are common, 8 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
1
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
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.

