carta-cap-table

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).

No description in the SKILL.md.

No description in the SKILL.md.

No description in the SKILL.md.

No description in the SKILL.md.

飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、应用模式（BaseApp/AppMode 页面与组件）、Workspace 目录、workflow、角色权限、模板中心（多维表格模板分类/列表/搜索）；遇到 Base/多维表格/bitable、BaseApp/AppMode、/base/ 或 /app/ 链接时使用。BaseApp 不走 lark-apps；文件导入/导出转 lark-drive，认证/授权转 lark-shared。

Use for lark-cli setup/auth tasks: auth login/status/logout, user vs bot identity, business-domain permissions (--domain, including all/docs/drive), missing scopes, revoking authorization, or handling _notice JSON.

飞书知识库：管理知识空间、空间成员和文档节点。创建和查询知识空间、查看和管理空间成员、管理节点层级结构、在知识库中组织文档和快捷方式。当用户需要在知识库中查找或创建文档、浏览知识空间结构、查看或管理空间成员、移动或复制节点时使用。当用户给出 doubao.com 的 /wiki/ URL/token 时，也应直接使用本 skill，不要因为域名不是飞书而回退到 WebFetch；路由依据是 URL 路径模式和 token，而不是域名。不负责：上传文件到知识库节点下（走 lark-drive）、编辑文档/表格/Base 内容（走 lark-doc / lark-sheets / lark-base）。

飞书任务：管理任务、清单和任务智能体。创建待办任务、查看和更新任务状态、拆分子任务、组织任务清单、分配协作成员、上传任务附件、注册或注销任务智能体、更新任务智能体的主页数据、写入智能体任务记录。当用户需要创建待办事项、查看任务列表、跟踪任务进度、管理项目清单或给他人分配任务、为任务上传附件文件、注册注销任务智能体、更新智能体主页数据、写入任务记录时使用。