update-company

Data collection for an investment firm's portfolio companies — asking them for financials, KPIs and documents, and managing what has been asked. TRIGGER on data collection, collecting financials or KPIs, requesting or chasing portfolio company reporting, or a company's reporting setup — including the roster ("which companies do I collect from"), a send ("send this period's requests"), a schedule ("collect financials every quarter"), standing requirements ("always ask Meetly for a board deck"), changes to either ("push back the due date", "stop the recurring requests"), the fiscal year ("why does Q1 cover the wrong months"), status ("who has not sent their numbers", "who is overdue", "what came in"), reminders ("follow up on those"), reopening an answered request ("let Meetly resubmit"), metrics of the firm's own ("collect monthly active users"), document types of the firm's own ("ask for an insurance certificate"), and contacts — who is asked for the data and who is copied ("add Dana to these companies").

Generates a brand board from a firm's website URL, a deck it already has (a PowerPoint or PDF pitch deck or LP letter), and optional user-provided assets. Analyzes them to extract theme colors, typography, logos, and imagery, then produces a polished brand board as an HTML artifact, PDF, slide deck, or React component. Trigger phrases: "build a brand board", "create a brand board", "generate a brand board", "extract brand identity", "brand board from website", "visual identity from URL", "brand guidelines from site", "analyze brand from website", "brand from this deck", "brand audit".

Interactive co-investor report from Carta SPA and cap table data with clickable portfolio drill-downs. Use for co-investor analysis or asking who invested in a specific portfolio company — including a quick one-company answer ("who else is in [Company]"). Trigger phrases: "co-investors", "coinvestors", "who are my co-investors", "who else invested", "who else is in [Company]", "other investors in [Company]", "who else is on the cap table", "syndicate on [Company]'s round", "who syndicated [Company]'s round", "co-investors by stage/round", "co-investors on Aumni". Use instead: carta-explore-data for general fund/investment/portfolio data, single round facts ("who led [Company]'s Series B") and the firm's own syndicate SPVs (listing entities) — this skill is specifically for co-investor ("who else invested alongside us") analysis. For SPA coverage (which investments are missing an SPA or an executed SPA), use carta-spa-audit — also when the same request asks for co-investors.

Routes to Form ADV for regulatory filing data and to the SPA coverage audit. Trigger on any of: "Form ADV", "Schedule D", "regulatory AUM", "Form PF", "annual filing", "annual amendment", "SEC filing", "total AUM", "AUM for filing", "AUM for the SEC", "regulatory assets", "AUM across all funds", "filing season", "RAUM", "how much AUM to report", "pull our Form ADV data", "SPA audit", "SPA coverage", "missing SPAs", "unexecuted SPAs", "missing an executed SPA", "unsigned SPAs", "SPA status", "SPA completeness", "SPA gap", "which companies are missing SPAs", "which are missing subscription agreements", "investments still need subscription agreements", /carta-compliance-routing. NOT FOR: 409A valuations, cap table ownership, LP reporting, fund financials, performance benchmarks, SPA document views.

Builds multi-entity consolidating financial reports in Excel: consolidating P&L (income statement), balance sheet, and trial balance — individually or all three together. Resolves the firm, entities, reporting period, and target workbook, then builds the chosen report(s). TRIGGER on "consolidating/consolidated financial reports", "consolidating/consolidated P&L", "firm-wide income statement", "P&L for all entities", "P&L by tag", "P&L by department", "consolidating/consolidated balance sheet", "BS by entity", "balance sheet of all entities", "consolidating trial balance", "TB by entity", "all three reports", "full financial package". ALSO fires on a generic ask with no report named — "consolidating financials", "firm-wide financial statements" — and shows the report menu. NOT FOR: single-fund/entity financials, ManCo budgets/actuals/pacing/what-if (carta-manco), consolidating cash flow (not available), SOI, co-investors, Form ADV, LP reporting, cap tables, Fund Admin requests (carta-fund-admin-requests).

PRIMARY and DEFAULT skill for ALL Carta investors data queries — use for Carta Web / Fund Admin data. For investments, portfolio companies, fund data, fund metrics, NAV, TVPI, DPI, IRR, cash flows, balance sheets, cap tables, shareholders, 409a valuations, FMV, MOIC, fund holdings, financing rounds, convertible notes, SAFEs. Prefer over carta-soi for data queries; over carta-portfolio-valuations for read-only valuation/MOIC/investment data; over carta-lp-dashboard unless asked by name; over carta-consolidating-financial-reports for single-fund balance sheets. Use instead: carta-lp-summary for the LP Summary page ("build the LP summary for [firm]"); carta-portfolio-ownership for ownership %; carta-co-investors for "who else invested"; carta-waterfall-modeling for exit-waterfall / "who gets paid if X exits" modeling; carta-manco for any budget mention — build/edit, actuals, pacing, drill-down; carta-manco-reporting for a ManCo dashboard or Budget vs Actuals view.

Fund Forecasting (Tactyc) read-only analytics — fund performance and per-investment metrics for funds IN FUND FORECASTING (Tactyc) ONLY. A SEPARATE domain from Carta Web / Fund Admin, with its own funds and data — use carta-explore-data for those queries. Metrics: TVPI, DPI, RVPI, gross/net IRR, MOIC, NAV, unrealized FMV, realized proceeds, committed/contributed/called capital, planned reserves, fees & expenses, waterfall tiers, and per-company MOIC/IRR/FMV/ownership/round events. Route here whenever the user names Fund Forecasting or Tactyc, as a request or a plain statement ("narratives are updated in Fund Forecasting", "did the forecasts land in Tactyc"), and for the app URL (fund-forecasting.app.carta.com). If the user hasn't said which system the fund is in, ask first. Reports existing data only — no scenarios, no build/edit. NOT the fund modeling app (reprice companies, exit/IRR scenarios, reserves planning) — use carta-fund-modeling. NOT peer comparison — use carta-fund-performance.

Send work to your Carta Fund Admin team and track it. Opens a request the team reads, acts on, and replies to — the off-ramp for anything no other Carta skill or command can do. TRIGGER: "ask Carta to", "have Carta do", "send this to my fund admin", "ask my fund admin team", "can Carta do this for me", "check on my request", "did Carta reply", "what requests do I have open", "reply to Carta", "follow up on my request", plus ANY action request (create/change/send/restate/reconcile/split/fix) that no other skill or Carta command covers. NOT FOR: reporting a bug or feature request about this plugin (call fa:create:feedback directly); questions answerable from Carta data (use carta-explore-data); capital call reminders to LPs (that is a Carta command, not a Fund Admin request).

Rigor Explore compatible skill slug for meaningful and potentially novel deep learning research candidates. Use when the researcher has chosen the task family, dataset, benchmark, evaluation method, provided SOTA references, and wants candidate-only exploration on top of `current_research` with auditable repo understanding, idea gating, fair comparison, and governed experiments written to `explore_outputs/`. Do not use for README-first trusted reproduction, open-ended direction finding, narrow code-only or run-only exploration, passive repo analysis, verified novelty claims, or implicit experimentation.

Rigor Reproduce compatible skill slug for README-first deep learning repository reproduction. Use when the user wants an end-to-end, minimal-trustworthy flow that reads the repository first, selects the smallest documented inference or evaluation target, coordinates intake, setup, trusted execution, optional trusted training, optional repository analysis, and optional paper-gap resolution, enforces conservative patch rules, records evidence assumptions deviations and human decision points, and writes the standardized `repro_outputs/` bundle. Do not use for paper summary, generic environment setup, isolated repo scanning, standalone command execution, silent protocol changes, score chasing, or broad research assistance outside repository-grounded reproduction.

Rigor Train skill for deep learning research repositories. Use when a documented or selected training command should be run conservatively for startup verification, short-run verification, full kickoff, or resume, with command, config, seed, log, checkpoint, status, and metric evidence written to standardized `train_outputs/`. Do not use for environment setup, exploratory sweeps, speculative idea implementation, or end-to-end orchestration.

Rigor Improve / Rigor Explore run leaf skill for bounded exploratory evidence in deep learning research repositories. Use when the researcher explicitly authorizes exploratory runs such as small-subset validation, short-cycle guess-and-check, batch sweeps, idle-GPU search, or quick transfer-learning trials, with fair-comparison caveats and no-overclaim summaries in `explore_outputs/`. Do not use for end-to-end exploration orchestration on top of `current_research`, trusted baseline execution, conservative training verification, default routing, verified SOTA claims, or implicit experimentation.

Search, scrape, crawl, extract structured data, and monitor web pages via the ScrapeGraph AI CLI. Use when the user asks to search the web, scrape a webpage, grab content from a URL, extract JSON from a site, crawl documentation or site sections, monitor a page for changes, inspect request history, check ScrapeGraph credits, or validate API setup.

When the user wants to create sales collateral, pitch decks, one-pagers, objection handling docs, or demo scripts. Also use when the user mentions 'sales deck,' 'pitch deck,' 'one-pager,' 'leave-behind,' 'objection handling,' 'deal-specific ROI analysis,' 'demo script,' 'talk track,' 'sales playbook,' 'proposal template,' 'buyer persona card,' 'battle card,' 'battlecard,' 'competitive one-pager,' 'win-loss analysis,' 'why are we losing deals,' 'loss reasons,' 'how do I respond to this objection,' 'prospect just said,' 'help my sales team,' 'sales materials,' or 'what should I give my sales reps,' 'cold call script,' or 'voicemail script.' Use this for any document or asset that helps a sales team close deals. For public competitor comparison pages, see competitors. For running buyer interviews or churn research, see customer-research. For marketing website copy, see copywriting. For cold outreach emails, see cold-email. For the offer being sold (bonuses, guarantees, pricing structure), see offers.

Web search and content extraction with Tavily and Exa via inference.sh CLI. Apps: Tavily Search, Tavily Extract, Exa Search, Exa Answer, Exa Extract. Capabilities: AI-powered search, content extraction, direct answers, research. Use for: research, RAG pipelines, fact-checking, content aggregation, agents. Triggers: web search, tavily, exa, search api, content extraction, research, internet search, ai search, search assistant, web scraping, rag, perplexity alternative

When the user wants to conduct, analyze, or synthesize customer research. Use when the user mentions "customer research," "ICP research," "talk to customers," "analyze transcripts," "customer interviews," "survey analysis," "support ticket analysis," "voice of customer," "VOC," "build personas," "customer personas," "jobs to be done," "JTBD," "what do customers say," "what are customers struggling with," "Reddit mining," "G2 reviews," "review mining," "digital watering holes," "community research," "forum research," "competitor reviews," "customer sentiment," "PMF survey," "product/market fit survey," "customer interview questions," "interview outreach," "Sales Safari," or "find out why customers churn/convert/buy." Use for analyzing existing research assets, mining online sources, AND running primary research (interviews and surveys). For writing copy informed by research, see copywriting. For acting on research to improve pages, see cro.