lookup-fund-portfolio
Finds and returns the portfolio companies listed on a VC or investment fund's website. Use this skill when the user says things like "look up portfolio of [fund]", "get portfolio companies for [fund website]", "what companies does [fund] invest in", "find portfolio page for [url]", "list investments of [fund]", or "/lookup-fund-portfolio". Input: fund website URL or domain. Output: structured JSON list of portfolio company names. Saves the result locally at ~/.carta-crm/fund-portfolios/ for auditing.
What this skill does
## Overview
Find and extract the portfolio company list from an investment fund's website.
The result is saved locally as a JSON file and returned to the caller.
## Step 1 — Normalize the target URL
Take the input and produce a clean root URL:
- If it starts with `http://` or `https://`, use as-is.
- If it's a bare domain (e.g., `sequoiacap.com`), prepend `https://`.
- Strip any path — use the root only (e.g., `https://sequoiacap.com`).
Also extract the bare domain (e.g., `sequoiacap.com`) for the output filename.
## Step 2 — Discover the portfolio page
Try fetching these paths in order, stopping at the first one that returns meaningful company data:
1. `[root-url]/portfolio`
2. `[root-url]/companies`
3. `[root-url]/investments`
4. `[root-url]/portfolio-companies`
5. `[root-url]/our-portfolio`
6. `[root-url]/founders`
For each fetch, use this prompt: "List every company name mentioned on this page. Also return the page title so I can identify which fund this is."
If none of the above return a clear company list, fetch the homepage and look for any navigation links that suggest a portfolio or companies section. Then follow those links.
## Step 3 — Fallback: web search
If WebFetch fails to find a usable portfolio page (e.g., JavaScript-heavy SPA, login wall, empty results), run a WebSearch:
```
[fund name] portfolio companies site:[domain]
```
Or if the fund name is unknown:
```
[domain] investment fund portfolio companies list
```
Use the search results to either find the direct portfolio URL to retry with WebFetch, or extract company names directly from search snippets.
## Step 4 — Extract company names
From the fetched content, extract a clean list of portfolio company names:
- Include only company/startup names — not fund names, investor names, or team members
- Remove duplicates
- Normalize capitalization (use the company's own capitalization where visible)
- Do not include descriptions, sectors, or URLs — names only at this stage
- If the page is paginated or has "Load more", note how many companies were retrieved vs. total shown
Aim for completeness — capture every visible company name on the page.
## Step 5 — Save the portfolio record
Write the result to a local audit file:
```bash
mkdir -p ~/.carta-crm/fund-portfolios
cat > ~/.carta-crm/fund-portfolios/[domain].json << 'ENDJSON'
{
"fund": "[fund name]",
"website": "[root url]",
"portfolio_page": "[url used to retrieve data]",
"retrieved_at": "[today's date as YYYY-MM-DD]",
"company_count": [N],
"companies": [
"Company A",
"Company B",
"Company C"
]
}
ENDJSON
```
Confirm the file was written with `echo $?` (should be 0).
## Step 6 — Return the result
Return the full JSON record to the caller. Then summarize:
> "Found **N portfolio companies** for **[Fund Name]** from [portfolio_page]. Saved to `~/.carta-crm/fund-portfolios/[domain].json`."
If the list appears incomplete (e.g., page was paginated, or only logos were shown without text names), add a note:
> "Note: page may be incomplete — only N companies were visible as text. The fund may have more investments not listed."
Related in Sales & CRM
process-mapper
IncludedUse when a BizOps lead, COO, or process-improvement owner needs to document an end-to-end business process (procurement, employee onboarding, incident handoff, customer-onboarding, claims adjudication) in BPMN-style notation, measure cycle times by stage, surface where work spends most of its time waiting vs. being worked, and quantify the gap between processing time and total elapsed time. Pairs Lean / Six Sigma / Theory-of-Constraints canon with deterministic stdlib-only Python tools to produce a process map, a ranked bottleneck list (with severity + root-cause hypothesis), and a cycle-time analysis (P50, P90, value-add ratio, Little's-Law throughput). Distinct from sales-pipeline, system-reliability (SLO), and strategic-OKR work — this is tactical process documentation for internal operations.
payment-integration
IncludedIntegrate payments with SePay (VietQR), Polar, Stripe, Paddle (MoR subscriptions), Creem.io (licensing). Checkout, webhooks, subscriptions, QR codes, multi-provider orders.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.
customer-success-manager
IncludedMonitors customer health, predicts churn risk, and identifies expansion opportunities using weighted scoring models for SaaS customer success
sales-engineer
IncludedAnalyzes RFP/RFI responses for coverage gaps, builds competitive feature comparison matrices, and plans proof-of-concept (POC) engagements for pre-sales engineering. Use when responding to RFPs, bids, or proposal requests; comparing product features against competitors; planning or scoring a customer POC or sales demo; preparing a technical proposal; or performing win/loss competitor analysis. Handles tasks described as 'RFP response', 'bid response', 'proposal response', 'competitor comparison', 'feature matrix', 'POC planning', 'sales demo prep', or 'pre-sales engineering'.