skills/investor-audits/SKILL.md
Handle investor audit confirmations and quarterly portfolio reporting requests. Use when: (1) Email from auditor (PwC, KPMG, EY, CBIZ, Deloitte) requesting confirmation, (2) Investor asks for quarterly reporting (revenue, runway, cap table), (3) User asks to 'help with audits' or 'process audit requests', (4) Email contains 'audit confirmation' or 'investment confirmation'. Maps requests to standard company data and drafts accurate responses.
npx skillsauth add dazuck/operator-skills investor-auditsInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Efficiently respond to investor auditors and quarterly reporting requests using standardized company data.
Accuracy over speed. Auditors need precise numbers as of specific dates. Wrong data creates more work than delayed data.
NEVER make up information. If data is not in the reference files, DO NOT guess or fabricate. Flag as missing and ask user to provide source.
Standard data, custom responses. 95% of requests ask for the same underlying info in different formats. Maintain clean reference data, adapt presentation per request.
Quarterly snapshots. Auditors want point-in-time data (usually quarter-end), not live data. Local snapshots are actually better than API integrations for this use case.
Before drafting ANY response, use a subagent to verify:
⚠️ VERIFICATION CHECKLIST (run via subagent)
□ Investor legal name matches cap table exactly
□ Share class stated in request matches their actual holdings
□ All numbers copied from reference files (not calculated/estimated)
□ If request mentions amounts, verify against our records
□ Flag ANY discrepancies to user before drafting response
If the investor states something that doesn't match our records (e.g., "our Series A-3 position" when they have A-2), flag this discrepancy - do not assume they're right or silently use their version.
Skill-specific reference data lives in the skill's references/ directory:
references/
├── company-info.md # Legal names, addresses, EIN, formation, banking
├── cap-table-YYYY-MM-DD.xlsx # Cap table export (SOURCE OF TRUTH)
├── cap-table-YYYY-MM-DD.csv # CSV export for quick lookups
├── cap-table-YYYY-QX.md # Pricing reference + column mapping only
├── entity-mappings.md # Common name → legal entity mappings
├── financials-YYYY-QX.md # Summarized financials from bookkeeper
├── certificate-of-incorporation.pdf # Certificate of Incorporation
├── insurance.md # D&O limits, coverage details
├── d-and-o-binder-YYYY.pdf # Actual policy document
└── response-templates.md # Standard response language
Shared financial data (used by multiple skills) lives in a shared data directory ([YOUR_DATA_PATH]):
data/
├── financials-YYYY-MM-DD.xlsx # Raw bookkeeper financials (SOURCE OF TRUTH)
├── runway-model.xlsx # Runway model
references/company-info.mdCRITICAL: Use source files (Excel/CSV/PDF) directly. NEVER manually transcribe data into markdown.
Note: Pending requests are tracked via the audits Gmail label - emails ARE the tracker.
Fill this in for your company. Used to sign responses and verify company identity in audit requests.
| Field | Value | | -------------- | -------------------------- | | Legal name | [YOUR_LEGAL_COMPANY_NAME] | | DBA | [YOUR_DBA_IF_APPLICABLE] | | State | Delaware (or your state) | | EIN | [from company-info.md] | | Address | [from company-info.md] | | Accounting | [YOUR_BOOKKEEPER] | | Cap table | [Carta / Pulley / etc.] |
When an audit/reporting request comes in, identify:
| Field | Extract | | ------------------- | ------------------------------------------------------------ | | Requester | Audit firm + contact (e.g., "KPMG - [Name]") | | On behalf of | Which investor fund | | As-of date | What date they want data for (usually Dec 31 or quarter-end) | | Deadline | When response is due | | Items requested | List of specific data points |
Most requests ask for combinations of:
| Request Language | Maps To |
| ---------------------------------------------------------- | ----------------------------------------------------- |
| "Cap table", "ownership %", "shares held" | cap-table-YYYY-QX.md |
| "Investment confirmation", "cost basis", "amount invested" | cap-table-YYYY-QX.md (includes cost basis column) |
| "Financials", "balance sheet", "P&L" | financials-YYYY-QX.md or bookkeeper export |
| "Loans", "convertibles", "SAFEs" | cap-table-YYYY-QX.md (section for debt instruments) |
| "D&O insurance", "liability limits" | insurance.md |
| "Runway", "cash position" | financials-YYYY-QX.md |
Before drafting response, verify:
⚠️ DATA FRESHNESS CHECK
Cap table: Q4 2025 (as of Dec 31, 2025) ✓ Current
Financials: Nov 2025 ⚠️ Dec not yet closed
Insurance: 2025 policy ✓ Current
Positions: Last updated Jan 15, 2026 ✓ Current
Flag if:
Generate response email with:
Requests are tracked via the audits Gmail label. The emails themselves are the tracker - no separate tracking file needed.
Auditors verifying their client's investment position.
They need:
Response template:
Dear [Auditor],
We confirm the following investment position for [Investor Fund] in
[YOUR_LEGAL_COMPANY_NAME] as of [date]:
Shares: [X] Series [Y] Preferred Stock
Price per share: $[X.XX]
Total investment: $[X,XXX,XXX]
Ownership: [X.XX]% undiluted / [X.XX]% fully diluted
[Investor Fund] holds no loans, convertible notes, or other instruments.
Please find attached our cap table as of [date].
Best regards,
[YOUR_NAME]
[YOUR_TITLE], [YOUR_COMPANY]
Comprehensive request covering multiple data points.
They need:
Response approach:
Investor fund's internal reporting, not external audit.
They need:
Response approach:
cap-table-YYYY-QX.mdIf data is missing or stale:
⚠️ MISSING DATA
Cannot complete response - need:
□ Q4 2025 cap table (export from cap table provider)
□ Dec 2025 financials (request from bookkeeper)
Suggested action:
1. Export cap table from your provider
2. Email bookkeeper requesting month-end close
When multiple requests pending (in audits label):
audits labelaudits label when doneOutput must include: Fetched: X requests | Processed: X requests | Verified: ✓
Before sending any response:
development
Document work and learnings for publication. Assesses session work, recommends format (tweet, thread, week notes, full write-up), drafts in your voice, writes to draft folder.
development
Explain technical projects or codebases to a non-engineer. Use for "orient me" or "explain this repo".
tools
Adapt any skill to your specific workflow, or create new ones for repetitive tasks. Use when adapting skills to your tools/process.
development
Prepare a demo artifact for daily team show & tell. Aggregates work from the last 24 hours into a presentable format with evidence (command output, screenshots). Use when asked to "prep for show and tell", "what did I do today", or "prepare my demo".