Menú
Status of witness and spousal-consent signature requests on option grants, RSAs, PIUs — who still needs to sign, and what's awaiting signature, signed, or expired. Covers one award, one company, or a whole portfolio. Read-only.
Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.
Basado en la clasificación ocupacional SOC
Spin up an interactive local web console for FIRM-LEVEL scenario modeling over Carta Fund Admin data — a React app to reprice portfolio companies and model exits ACROSS MULTIPLE COMPANIES, with five tabs: Overview (fund-family rollup, investment pacing, concentration), Companies (per-company repricing + LP make-whole waterfall + carry banking), Exit & IRR (exit scenarios, XIRR, GP & LP returns, plus a per-fund DPI/RVPI/TVPI glidepath in the LP Returns view), Reserves (per-fund dry-powder planning), and Cohort Standing (peer-cohort + S&P-equivalent benchmarking). Scenarios persist locally. Invoke with a firm name, e.g. "fund modeling for Demo Capital" or "model portfolio scenarios for <firm>". Fund Admin only. NOT Tactyc/Fund Forecasting — use carta-fund-forecasting for Tactyc funds. NOT for single-exit waterfalls on one company. NOT read-only fund data queries — use carta-explore-data.
Retrieves Carta Total Compensation market benchmarks (salary, equity, total cash) for a role. Output to chat or CSV. Market benchmarks are triggered by queries like: "sales benchmarks", "comp benchmarks", "market rate", "what does a [role] pay", "put benchmarks in a CSV", "get benchmarks", "get carta's market benchmarks", "show me benchmarks for [role]", "compensation ranges for [role]", "p25/p50/p75 for [role]". Do NOT use for job classification or role mapping — use carta-compensation-rolematcher for that. Do NOT use for "how is OUR company positioned vs market", "who at our company is below market", or "our internal pay bands vs benchmarks" — those are roster-level positioning, use carta-compensation-scorecard. Do NOT use for fund performance benchmarks (use carta-performance-benchmarks) or portfolio structural metrics like SAFE terms and option pool sizes (use carta-market-benchmarks).
Classify a job title or description into the CTC taxonomy (job area, focus, level, track). Use when the user wants to know how a role is categorized or mapped to the taxonomy structure — not to fetch salary, equity, or benchmark numbers. Do NOT use when the user is asking for "market rates", "benchmark data", "compensation ranges", "what does X pay", or "show me benchmarks" — use carta-compensation-benchmarks for that. Do NOT use when the user is asking how their own company compares to market — e.g. "our internal pay bands vs Carta benchmarks", "compare our pay bands against the 25th/50th/75th percentile", "who at our company is below market" — that's roster-level positioning, use carta-compensation-scorecard. Do NOT use for general career advice or job search queries unrelated to compensation benchmarking.
Carta Total Compensation scorecard — shows how a corporation's employees compare to market. Two lenses: corporation-level rollup (band distribution — what % of employees are below / at / above market) and per-employee scorecard (each employee's compa-ratio + percentile + market band). Triggered by queries like: "scorecard", "how is our comp positioned", "who's below market", "which employees are below P50", "show me the roster", "are we paying market", "comp posture", "employee compa-ratios", "is [employee] underpaid", "pay adjustment analysis", "our internal pay bands vs benchmarks", "score these employees". Operates on the corporation's already-ingested CTC roster (HRIS-synced employees). Do NOT use for market-rate lookups for a role (use carta-compensation-benchmarks). Do NOT use for job classification (use carta-compensation-rolematcher). Do NOT use for fund performance scorecards or portfolio-level metrics.
PRIMARY and DEFAULT skill for ALL Carta investors data queries — use before any other skill for Carta Web / Fund Admin data. Carta Web / Fund Admin investors data queries against the data warehouse. For investments, portfolio companies, fund data, fund metrics, NAV, TVPI, DPI, IRR, cash flows, balance sheets, cap tables, ownership %, shareholders, 409a valuations, FMV, MOIC, fund holdings, what a fund is invested in, financing rounds, investment rounds, tranches, priced rounds, convertible notes, SAFEs. Prefer over carta-soi for data queries (carta-soi is for Cowork persistent artifacts); over carta-portfolio-valuations for read-only valuation/MOIC/investment data (that skill runs/updates valuation projects); over carta-lp-dashboard unless asked by name; over carta-consolidating-balance-sheet for single-fund balance sheets. Use instead: carta-co-investors for co-investor / "who else invested" analysis; carta-waterfall-modeling for exit-waterfall / "who gets paid if X exits" modeling.
End-to-end AGM deck generator. Extracts a firm's brand identity from their website, pulls live fund data from the Carta MCP (NAV, TVPI, portfolio, capital activity, benchmarks, fees, balance sheet, LP base), generates a branded HTML presentation with built-in slide navigation, and applies the "Powered by Carta" badge to every slide. Supports an optional past-deck reference for style matching. Trigger phrases: "AGM deck", "generate AGM deck", "create AGM presentation", "build AGM slides", "annual general meeting deck", "investor meeting deck", "LP meeting deck", "fund presentation", "branded fund deck", "build an AGM deck".
| name | carta-witness-signatures |
| description | Status of witness and spousal-consent signature requests on option grants, RSAs, PIUs — who still needs to sign, and what's awaiting signature, signed, or expired. Covers one award, one company, or a whole portfolio. Read-only. |
| when_to_use | Use when asked whether a witness or a spouse has signed, who still needs to sign an award, which signature requests are awaiting signature or have expired, when a signing link expires, or to list witness / spousal-consent requests for a single award, a company, or across a portfolio. Phrasings like "did the witness sign", "is the spousal consent done", "which grants are waiting on a signature", or "any expired signing links". |
| model | inherit |
| allowed-tools | ["mcp__carta__call_tool","mcp__carta__list_contexts","mcp__carta__set_context","mcp__carta__list_accounts","AskUserQuestion"] |
Show the status of the extra signatures some equity awards need before they're fully in place.
When someone is granted equity, the award sometimes needs a signature from a person other than the recipient before it's complete:
Each one is tracked as a signature request tied to a single award. A request moves through these stages:
| Stage | What it means |
|---|---|
| Awaiting details | The request exists, but the witness or spouse's name and email haven't been added yet. |
| Awaiting signature | Details are in and the signing link has been sent. Waiting on the witness or spouse to sign. |
| Signed | Done — the witness or spouse has signed. |
| Expired | The signing link's deadline passed before it was signed. Signing links expire about 30 days after they're sent. |
These three awards can carry signature requests: option grants, RSAS (restricted stock awards), and PIUs (profits interest units).
list_accounts (companies appear as corporation_pk: entries).OPTION_GRANT, RSA, or PIU) and the award itself. The company-wide list (below) returns these, so start there if you don't already know which award you mean.list_accounts (portfolios appear as organization_pk: entries) — this is the investor or firm view across the companies they hold or manage.If a required input is missing, ask for it with AskUserQuestion before fetching (see carta-interaction-reference §4.1).
Pick the command that matches the scope of the question.
One company — every request for a single company:
call_tool({"name": "cap_table__list__witness_signatures_for_corporation", "arguments": {"corporation_id": corporation_id}})
Optional filters: request_type (WITNESS or SPOUSAL_CONSENT), status (a list of PENDING, FILLED, SIGNED, EXPIRED), page, page_size.
One award — every request on a single award you've already identified:
call_tool({"name": "cap_table__get__witness_signatures_for_security", "arguments": {"corporation_id": corporation_id, "security_type": "OPTION_GRANT", "security_id": security_id}})
security_type is one of OPTION_GRANT, RSA, PIU.
A portfolio — requests across every company in a portfolio:
call_tool({"name": "cap_table__list__witness_signatures_for_portfolio", "arguments": {"portfolio_id": portfolio_id}})
Optional filters: request_type, status, issuer_id (narrow to one company), page, page_size.
Spousal consent in portfolio view: the portfolio list returns witness requests only, unless you narrow it to a single company with
issuer_id. Spousal-consent requests appear only for a single company that has the feature turned on. If a user asks about spousal consent across a whole portfolio, narrow to one company at a time.
Default status filter: when you don't pass
status, the results show the requests that usually need attention — those awaiting signature and those that have expired. To see requests still awaiting details or already signed, passstatusexplicitly (e.g."status": ["SIGNED"]).
Each request carries:
status: PENDING, FILLED, SIGNED, or EXPIRED — map to the friendly labels in the Background table.request_type: WITNESS or SPOUSAL_CONSENT.expires_at: the signing deadline.issuer_name: the company that granted the award.security_label: the award's reference (for example, "ES-1007").security_type: OPTION_GRANT, RSA, or PIU.witness_name, witness_email: the witness or spouse who needs to sign (blank until details are added).acceptance_date: when the recipient accepted the award.Required inputs: a company (corporation_id) for the company and award commands; a portfolio (portfolio_id) for the portfolio command; plus security_type and the award for the single-award command. If missing, call AskUserQuestion before proceeding.
Format: Table.
BLUF lead: Lead with the counts — how many are awaiting signature, signed, and expired — then the table.
4 signature requests: 2 awaiting signature, 1 signed, 1 expired.
Translate codes to plain language. Never show the raw status, type, or any internal reference. Use "Awaiting signature", "Witness" / "Spousal consent", and "Option grant" / "RSA" / "PIU". Identify each request by company, award reference, and the person's name — not by any internal number.
Sort order: Awaiting signature first, then by soonest deadline; expired next; signed last.
Date format: MMM d, yyyy (e.g. "Jan 15, 2026").
| Company | Award | Type | Needs to sign | Status | Deadline |
|---|---|---|---|---|---|
| Acme | ES-1007 (Option grant) | Witness | Dana Lee | Awaiting signature | Jun 1, 2026 |
| Acme | PIU-12 (Profits interest unit) | Spousal consent | Sam Rivera | Signed | — |
For a single award, lead with the award and the count, then list its requests.
End with a next step — for example, point out which requests are closest to expiring, or note that reminders and deadline extensions are handled in Carta.