Check cap-table records against signed source documents and report ownership, security, date, and total differences for expert review.
Instructions your experts follow when using this skill.
This skill finds record differences. It does not determine legal ownership, value securities, or edit the cap table.
Ask the owner or counsel which signed records and approved cap-table system are authoritative. Record the covered entity, as-of date, currency where relevant, fully diluted definition if supplied, and named legal and finance reviewers.
For each holder or award, compare only fields present in the supplied records:
Check totals by security class and in aggregate. Keep issued, outstanding, reserved, and fully diluted totals separate. Do not calculate ownership percentages until the denominator definition has been supplied.
Return source fact A, source fact B, the difference, affected total, likely
record owner, and the document or decision needed. Use possible duplicate
rather than merging similar names. Mark unsigned, missing, superseded, and
conflicting records.
Never create, change, delete, merge, or backdate an ownership record. Never decide that an unsigned grant is valid, interpret a security, set a valuation, calculate tax treatment, or advise on a transaction. Limit personal data in the output. Route every ownership, securities, governance, legal, tax, and valuation question to qualified counsel, the finance lead, or the approved administrator.
Phrases that help your experts find this skill.
When the user wants to create or update their product marketing context document. Also use when the user mentions 'product context,' 'marketing context,' 'set up context,' 'positioning,' 'who is my target audience,' 'describe my product,' 'ICP,' 'ideal customer profile,' or wants to avoid repeating foundational information across marketing tasks. Use this at the start of any new project before using other marketing skills — it creates `.agents/product-marketing.md` that all other skills reference for product, audience, and positioning context.
When the user wants to research, profile, or analyze competitors from their URLs. Also use when the user mentions 'competitor profile,' 'competitor research,' 'competitor analysis,' 'profile this competitor,' 'analyze competitor,' 'competitive intelligence,' 'competitor deep dive,' 'who are my competitors,' 'competitor landscape,' 'competitor dossier,' 'competitive audit,' or 'research these competitors.' Input is a list of competitor URLs. Output is structured competitor profile markdown files. For creating comparison/alternative pages from profiles, see competitors. For sales-specific battle cards, see sales-enablement.
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.