carta-cap-table
/carta-cap-table
Odpowiada na krótkie pytania o tablicę udziałów jednej spółki w Carta, w tym o udziałowców, pakiety i prawa.
Ocena i bezpieczeństwo
- Pliki w paczce
- 1
- Skrypty
- 0
- Komentarze HTML
- 2
- Adresy URL w SKILL.md
- 0
Brak sygnałów. Repozytorium zmienione 13.11.2026, bez odwołań do wycofanych modeli i API.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
- SKILL.md zawiera komentarze HTML (2). Nie widać ich w podglądzie Markdown, a model je czyta.
Co robi i kiedy
Odpowiada na krótkie pytania o tablicę udziałów jednej spółki w Carta, w tym o udziałowców, pakiety i prawa.
Wyzwalacze z opisu
Oryginalny opis (EN)
Answer quick questions about one company's cap table, like who owns what. Holds Carta's rules for every cap table answer, and the commands for a single fact or a short answer: one stakeholder, the largest grants or holders, totals of grants, certificates, RSUs, SARs, CBUs, SAFEs, convertible notes or option plans, and rights and preferences. Use when asked "who owns the most", "what percentage of the company do I own", "how many shares does [name] hold", "how many options are outstanding", "how many options are left in the pool", "what is the fully diluted share count", or when no other carta-
Jak działa
- Find the company
- Single facts and short answers
- Total, indirect or look-through ownership
- Answer rules
- Gates
- Ask well
- When a call fails
- Report a bug or request a feature
Podgląd SKILL.md
---
name: carta-cap-table
description: >-
Answer quick questions about one company's cap table, like who owns what. Holds
Carta's rules for every cap table answer, and the commands for a single fact or a
short answer: one stakeholder, the largest grants or holders, totals of grants,
certificates, RSUs, SARs, CBUs, SAFEs, convertible notes or option plans, and rights
and preferences. Use when asked "who owns the most", "what percentage of the company
do I own", "how many shares does [name] hold", "how many options are outstanding",
"how many options are left in the pool", "what is the fully diluted share count", or
when no other carta-cap-table skill matches. Also answers total, indirect or
look-through ownership through a holding entity (trust, Stichting, SPV, holdco or fund):
"direct and indirect holders", "who ultimately owns 25%", "beneficial owners". For
every row of a list, a table, a report or a file, for ownership by holder group
(founders, investors, employees) and for the liquidation seniority stack, use
carta-reporting.
user-invocable: false
model: inherit
allowed-tools:
- mcp__carta__read_tool
- mcp__carta__call_tool
- mcp__carta__search_tools
- mcp__carta__list_accounts
- mcp__claude_ai_Carta__read_tool
- mcp__claude_ai_Carta__call_tool
- mcp__claude_ai_Carta__search_tools
- mcp__claude_ai_Carta__list_accounts
- mcp__2827383e-1775-4df3-b6ff-04d5392f6d18__read_tool
- mcp__2827383e-1775-4df3-b6ff-04d5392f6d18__call_tool
- mcp__2827383e-1775-4df3-b6ff-04d5392f6d18__search_tools
- mcp__2827383e-1775-4df3-b6ff-04d5392f6d18__list_accounts
- AskUserQuestion
- Read
- ToolSearch
---
<!-- carta:plugin-version -->
<carta-plugin>carta-cap-table:6.114.12</carta-plugin>
<!-- Part of the official Carta AI Agent Plugin -->
# Carta Cap Table
The rules for every Carta cap table answer, and the direct commands for a single fact or
a short answer. A more specific carta-cap-table skill (vesting, valuations, round history,
issuance, reports) adds its own steps. These rules still apply.
## Find the company
Do not call `list_accounts` or ask which company before the first read: Carta finds the company. Reuse the company already resolved in this conversation unless this prompt names or numbers another. Else send the numeric id the user gave, else the company name as the user said it, else no `corporation_id` (Carta uses the user's only company). On an error, for later calls, and for writes, follow `${CLAUDE_PLUGIN_ROOT}/references/find-the-company.md` (the plugin's own `references/`, not this skill's; read it by that path, do not search for it).
## Single facts and short answers
Call `read_tool` with one command. One call answers most questions.
| Question | Command | Useful arguments |
|---|---|---|
| Who owns what, ownership % per holder | `cap_table__get__cap_table_by_stakeholder` | |
| Outstanding and fully diluted, by share class | `cap_table__get__cap_table_by_share_class` | |
| A stakeholder's id, email or role | `cap_table__get__stakeholders` | `search` (one person), `names` (several) |
| Option grants (ISO/NSO) | `cap_table__list__grants` | `search`, `detail`, `ordering`, `page_size` |
| Share certificates | `cap_table__list__certificates` | `search`, `ordering`, `page_size` |
| RSUs, SARs, CBUs | `cap_table__list__rsus`, `cap_table__list__sars`, `cap_table__list__cbus` | `search`, `detail` |
| SAFEs, convertible notes | `cap_table__list__safes`, `cap_table__list__convertible_notes` | |
| What one holder owns, every type | `cap_table__list__securities` | `type` (one per call), `holder` |
| Option plans and pool | `cap_table__get__option_plans` | |
| Rights and preferences | `cap_table__get__rights_and_preferences` | |
| Total, indirect or look-through ownership through a holding entity | `cap_table__list__ownership`, once per entity | see "Total, indirect or look-through ownership" |
```
read_tool({"name": "cap_table__list__grants", "arguments": {"corporation_id": <corporation_id>, "ordering": "-quantity", "detail": "minimal", "page_size": 20}})
```
- For what one holder owns, `cap_table__list__securities` with `holder` (one call per `type`)
returns the securities the holder still holds. Make the call for every type first, then
answer with the held securities of all types. If any response's `next_actions` offers
securities left out (cancelled, expired, forfeited and the like), say how many the holder
has across all types and call `AskUserQuestion` once whether to list them. On yes, call
each offered action. Never count them in what the holder owns.
- For counts and totals, use `detail: "summary"` where the command has it.
- For "largest" or "top N", use `ordering`, `page_size` and `detail: "minimal"`. Never
page through every row to sort or count: large companies time out.
- For data not in this table, call `search_tools` with a short description of the data,
then call the command it returns with the arguments its input schema names. Do not
guess command names or arguments.
- For every row of a list, a table, a report or a file, load carta-reporting.
- To compare the user's spreadsheet, HR export or register with Carta, call `read_tool`
with `cap_table__compute__reconciliation` once per security type with all the rows. Do
not page through holders to compare them yourself. The company goes in `company` as a
number, and each value is a decimal string:
```
read_tool({"name": "cap_table__compute__reconciliation", "arguments": {"company": <corporation_id>, "type": "option", "rows": [{"holder": "<holder>", "label": "<label>", "quantity": "<quantity>"}]}})
```
- Vesting of one grant, valuations (409A, FMV), round history and issuance have their own
skills. Load the matching skill. To edit, cancel, transfer or buy back an issued security,
record an option exercise, or approve or reject an exercise request, load
carta-manage-securities: it shows a preview before any change.
- To write a company update or investor update, call `read_tool` with
`cap_table__compute__create_communication_preview`. Apply a plan only with the named
`cap_table__mutate__apply_plan` tool on the same Carta connector, never with `call_tool`:
load it with `ToolSearch(query: "+apply_plan")`, then send `company`, the latest preview's
`plan_id` and its `summary` unchanged. After the draft apply, give the user the draft's
`meta.web_url` to read. To send it, call `read_tool` with
`cap_table__compute__send_communication_preview`, show the summary and every email in
`side_effects`, ask with `AskUserQuestion`, then call the same named apply tool with the
send preview's `plan_id` and `summary`. The emails cannot be taken back. If the apply tool
is not there, say: "Carta's apply tool isn't available in this chat, so nothing was
changed. Reconnect Carta and ask again."
## Total, indirect or look-through ownership
When the user asks for total, indirect, look-through, beneficial or ultimate ownership, for
owners above a threshold such as 25% on a bank or KYC form, or for the holders behind a holding
entity, follow `${CLAUDE_PLUGIN_ROOT}/references/look-through-ownership.md` (the plugin's own
`references/`, not this skill's; read it by that path, do not search for it). Never answer from
one cap table alone.
## Answer rules
- Give the as-of date of every Carta figure, in the words "as of <date>": `meta.as_of` when
the response has it, else the record's own date (for example a valuation's effective
date), else today's date: "as of <today>, the date I read it". Always write the words
"as of", also when Carta gives no date.
- Give the unit and currency of every amount: "$12,400", "1,200 shares". Read the
currency from each row. Never assume USD and never add amounts in different currencies.
- Never round without saying so. Never fill in a missing value: if Carta has no figure,
say so.
- Say which figures you computed. A figure you added, divided, modelled or projected is
Claude's analysis, not Carta data: label it, and never mix it into Carta figures
without the label.
- When the response has `meta.web_url`, or a row has `_links.web_url`, link the entity
name to it as it is. Never build or edit a Carta URL.
- Use Carta's terms: stakeholder, share class, option grant, 409A valuation. Never show
command names, field names, error codes, internal system names, or ids the user did
not ask for.
- Say "I" for your actions and "Carta" for Carta data and policy. Never say "we".
- Show data and explain how Carta works. Do not give legal, tax or financial advice: say
Carta can't advise on it and name the right advisor.
- Show only the data the user asked for. Never show one customer's data to another.
- Start with the answer. In a long answer, repeat the short answer in the last line: a
terminal shows only the last lines.
## Gates
**Required inputs**: none before the first read. The company comes from "Find the company".
**AI computation**: only for figures that Carta has not saved (pro forma, dilution,
conversion, projections). Total or indirect ownership through a holding entity is not
gated: follow "Total, indirect or look-through ownership". For the others, before you fetch
data or compute them, call `AskUserQuestion` (never plain text) with: "No saved Carta model matches these terms. I can compute [X] using
AI — this would be Claude's analysis, not Carta data. Would you like me to proceed?" If the
user says no, stop: no output, no fallback.
## Ask well
- Do not ask before a read. Ask with `AskUserQuestion`, never in plain text, when a
required input is missing or a match is ambiguous.
- Before a change, restate it in plain words with the values that matter (names,
quantities, prices, dates). Name the options by what they do ("Issue now / Save as
draft / Cancel"), not yes or no.
- Call a write only after the user picks the confirm option. One approval covers one
write call, never the next.
- Ask one decision at a time.
## When a call fails
Say what went wrong in plain words and what the user can do next. Do not invent a cause.
Do not send the same failed call again with the same arguments.
## Report a bug or request a feature
The command is `fa:create:feedback`. The only way to call it is
`call_tool({"name": "fa__create__feedback", "arguments": {…}})`, with `requestType`
(`"bug"` or `"feature_request"`) and `requestBody`; optional `flowSummary`, `context`,
`affectedSkill` and `source`. There is no feedback skill. Never call `mutate` for it.
- The command is feature-flagged. Before the first call, run
`search_tools("report a bug feedback")` once per session, and call only if
`fa__create__feedback` is in the results. If it is not: when the user asked, say
in-session feedback is not on for this account; when you were filing on your own, say
nothing. Then stop. Do not retry a call that came back "Unknown tool".
- Always send `flowSummary`: what the user asked, the skills and tools you ran, and where
it broke. Put the failing tool and its arguments in `context`. Do not send identity,
firm, session or timestamps.
- File on your own, with `source: "claude"`, when a tool errors, returns nothing usable,
or a needed capability is missing. Tell the user first.
Wersje
W bazie nie ma innych skilli o nazwie carta-cap-table.
Migawka bazy z 13.11.2026 · wersja paczki cec16e82aa65 (skrót SHA-256 całej paczki)
Pobrania w ostatnich 30 dniach: 0 · ranking
Zgłoś problem z tym skillem: szkodliwa treść, błędny opis albo prośba autora o usunięcie.
Podobne skille
- 95carta-reporting
Wyświetla dane z tabeli kapitalizacji jednej spółki: granty, harmonogramy vestingu, interesariuszy, SAFE, noty zamienne, rundy, akcje uprzywilejowane i prawa, także jako raport Excel. - 100carta-start
Pokazuje, co Claude potrafi zrobić z tablicą udziałów w Carta, i proponuje trzy polecenia dla danej roli. - 100cap-table-modeling
Buduje tabelę udziałów startupu z założycieli, opcji, instrumentów SAFE i obligacji zamiennych oraz modeluje kolejną rundę wyceny. - 100review-cap-table-sanity
Sprawdza matematykę i strukturę tabeli kapitałowej: sumy udziałów, pre- i post-money, SAFE, noty konwertowalne i pule opcji menedżerskich. - 91cap-table
Weryfikuje liczby, mechanikę i daty w cap table przed podpisaniem przez założyciela: SAFE, noty, term sheety, plany opcji, statut i pliki Carta, z odpowiedziami ze wskazaniem źródeł. - 95cap-table-analyst
Liczy rozwodnienie i strukturę własności w tabeli udziałów wyłącznie na podanych danych, pokazując każde obliczenie i sygnalizując braki.