From quant-pe
Prepare for due diligence meetings — management presentations, expert network calls, customer references, and advisor sessions. Generates targeted question lists, benchmarks to reference, and red flags to probe. Triggers on "prep for management meeting", "diligence call prep", "expert call questions", "customer reference questions", "meeting prep for [company]", "尽调会议准备", "管理层会议准备".
npx claudepluginhub vanlengs/floppy-quant-pluginsThis skill is limited to using the following tools:
> **Purpose**: Generate comprehensive preparation materials for PE/VC due diligence meetings, including management presentations, expert network calls, customer reference checks, and advisor sessions.
Creates isolated Git worktrees for feature branches with prioritized directory selection, gitignore safety checks, auto project setup for Node/Python/Rust/Go, and baseline verification.
Executes implementation plans in current session by dispatching fresh subagents per independent task, with two-stage reviews: spec compliance then code quality.
Dispatches parallel agents to independently tackle 2+ tasks like separate test failures or subsystems without shared state or dependencies.
Purpose: Generate comprehensive preparation materials for PE/VC due diligence meetings, including management presentations, expert network calls, customer reference checks, and advisor sessions.
This skill activates when the user requests preparation for any due diligence-related meeting or call:
English Triggers:
Chinese Triggers:
Step 1: Capture Meeting Context
Ask the user for the following information (if not already provided):
Step 2: Load Supporting Resources
If the user has uploaded documents, read them using read_file to extract:
Output Structure:
Generate a comprehensive Markdown report with the following 4 modules:
## Meeting Overview
| Field | Details |
|-------|---------|
| Target Company | [Company Name] |
| Industry | [Sector/Sub-sector] |
| Meeting Type | [Management/Expert/Customer/Advisor] |
| Duration | [Suggested: 45-60 min] |
| Key Objectives | [3-5 bullet points] |
| Attendees | [Suggested participants from your side] |
Generate layered questions organized by category:
For Management Meetings:
For Expert Network Calls:
For Customer Reference Calls:
For Advisor Sessions:
Question Format: Each question should include:
Include these technical questions where relevant (especially for tech/SaaS targets):
Architecture & Scalability:
"Walk us through your current architecture. How does it scale with 10x load?"
"What's your technical debt level and how do you manage it?"
Security & Compliance:
"What security certifications do you have (SOC 2, ISO 27001, HIPAA, etc.)?"
"How do you handle customer data privacy and compliance (GDPR, CCPA)?"
Product & Engineering:
"What's your engineering team structure and velocity?"
"How do you prioritize feature development vs. technical improvements?"
Technology Moat:
"What's your proprietary technology? How hard is it to replicate?"
"How do you leverage AI/ML? Is it core to your value prop or marketing?"
Provide reference benchmarks for comparison:
## Benchmark References
| Metric | Target | Industry Median | Top Quartile | Source |
|--------|--------|-----------------|--------------|--------|
| [Relevant KPI 1] | [if known] | [benchmark] | [benchmark] | [source] |
| [Relevant KPI 2] | ... | ... | ... | ... |
Benchmark Categories by Industry:
Research Method:
Option A: With web_search (if API key available)
Use web_search to find current industry benchmarks. Search queries like:
Option B: Without web_search (standalone mode) If web_search is unavailable:
Key Principle: The skill must function effectively WITHOUT external API dependencies. When benchmarks cannot be researched in real-time, provide:
## Red Flags to Probe
| Red Flag | Why It Matters | How to Probe |
|----------|---------------|--------------|
| [Specific concern] | [Risk implication] | [Questioning approach] |
Common Red Flags by Meeting Type:
Management Meetings:
Expert Calls:
Customer References:
Provide practical guidance for the meeting:
## Meeting Execution Tips
### Before the Call
- Review all available materials (BP, financials, prior call notes)
- Prepare a one-page briefing memo for your team
- Assign roles: lead questioner, note-taker, timekeeper
- Test technology (video conferencing, recording if permitted)
### During the Call
- Start with open-ended questions, then drill down
- Listen for inconsistencies or evasive answers
- Take detailed notes on specific claims (for follow-up verification)
- Leave 5-10 minutes for unexpected topics
### After the Call
- Debrief immediately with your team (15 min)
- Document key insights, red flags, and follow-up items
- Update your diligence tracker/CRM
- Identify gaps requiring additional investigation
Input:
Output:
User: "Prep for management meeting with Acme Tech, a SaaS company in cybersecurity"
Skill Response:
Ask clarifying questions (if needed):
Generate comprehensive prep document with:
Core Dependencies (required):
Optional Dependencies (enhanced experience if available):
Design Principle: This skill follows the "no external API key dependency" pattern. It must function effectively in standalone mode, using internal knowledge for benchmarks and frameworks. When web_search is unavailable, the skill clearly labels benchmark sources and provides representative ranges from training data.
After each meeting, encourage users to: