carta-data-collection
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").
Install
With your agent
Install OMGSkills skill "carta/plugins:plugins/carta-investors/skills/carta-data-collection" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/carta/plugins /tmp/plugins && ln -s /tmp/plugins/plugins/carta-investors/skills/carta-data-collection ~/.claude/skills/carta-data-collectionFrom README
Data collection Data collection for an investment firm's portfolio companies. Step 0 asks what reading cannot answer; Step 1 resolves the firm and Step 2 gates on its settings; all three apply to every action. Step 3 routes to the action's own reference, which carries the procedure. Step 0 — Ask what reading cannot answer Before any read, name the unknowns Carta cannot supply. If reading Carta could produce the answer — "last quarter", "our roster", "what we usually ask them for" — read; never ask for what a read can answer. If neither a read nor a form could produce it — which of three firms of the same name is meant, whether the request is even about data collection — ask for all of them in one AskUserQuestion, before spending calls on the rest of the task. Two boundaries keep this cheap rather than chatty.