network-referral-path-mapper
Skill69 starsChanged 24 days agoNo licenceView on GitHub
Given a target — a company to source, an LP to raise from, an executive to reference, a name on next week's calendar — work the firm's whole relationship surface (email and calendar history, the CRM, board and portfolio rosters, public professional profiles) and return every connection path ranked by strength: who holds the relationship, how recently and how often they interact, what the shared context was, and whether the intermediary actually makes introductions. Surfaces the two or three second-degree routes worth trying when the direct path is cold, flags when two colleagues are about to reach out to the same person, and ends with the drafted ask for whoever is best placed to make the intro — or a plain "no known path" when the firm has none. For deal-origination and business-development teams, investor-relations teams, family-office and allocator staff, and research managers checking interaction history before meetings. Trigger on phrases like "who do we know at [firm]," "who can get us to [name]," "warm path to [target]," "does anyone here know [person]," "how are we connected to [company]," "best route into [LP]," "have we ever talked to these people," or when a user provides a target name plus a CRM export or contact list and asks about connections. Do NOT use for summarizing where one existing relationship stands before re-engaging — use the relationship-status-summarizer skill. Do NOT use for a briefing on one LP ahead of a meeting — use the lp-meeting-prep-brief skill. Do NOT use for a banker's deal-by-deal history before a coverage meeting; this skill maps paths, not deal records. Do NOT use for screening a conference delegate list — use the conference-attendee-screen skill. Email, calendar, and CRM data are internal and personal to the colleagues who generated them; the skill reports relationships, never message contents, and assumes the owner of a relationship is asked before it is used.
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
- lp-update-generatorSkill
- manager-ai-practices-diligenceSkill
- marketing-compliance-prescreenSkill
- market-map-builderSkill
- market-sizing-builderSkill
- 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
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
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.

