Skip to main content
skill CX Codex

vc-industry-research — Claude Code skill: PE/VC research reports

vc-industry-research turns a prompt into a PE/VC-style industry report: sector deep-dive, investment memo or market analysis, in Chinese or English, PDF by default.

MIT ★ 4,719 updated 2026-10-24

Install into Claude Code · Skills CLI (Vercel) All methods and platforms ↓
npx skills add zebbern/claude-code-guide --skill vc-industry-research -a claude-code
Open on GitHub

What vc-industry-research does

The skill runs a sector study the way a primary-market desk would. Scope and page count come from your prompt, research happens through web search, and funding history gets its own step: rounds, deal sizes, lead investors, IPO and exit events.

Two layouts set the look. Style A suits TMT, AI and SaaS — argument first, chapters numbered 01, 02, no table of contents. Style B covers consumer, healthcare and industrials with charts and tables, plus a three-level contents page carrying dot leaders and page numbers. Both contracts live in references/style_contract.md and references/structure_contract.md. PDF comes out unless you ask for DOCX or PPTX.

Every figure gets a source note and exhibits are numbered, which is what separates the file from a plain summary. Chinese reports lean on KaiTi, SimSun and STKaitiSC-Regular; when those fonts are missing the skill substitutes a neighbouring family, so the cover won't match the template.

What it helps with

  • draft a TMT sector deep-dive as a PDF report
  • write an investment memo with sourced figures
  • map funding rounds and exits across a sector
  • lay out a Chinese-language report with a numbered contents page
  • audit a draft so every figure carries a citation

Example prompts for the agent

  • Put together a SaaS sector deep-dive in English, Style A, around twenty pages.
  • Analyse the cybersecurity market in China and write it up in Chinese with a contents page, Style B.
  • Build a funding and IPO history for consumer health and turn it into an investment memo as DOCX.

How to install vc-industry-research

1Skills CLI (Vercel)

npx skills add zebbern/claude-code-guide --skill vc-industry-research -a claude-code

2Manually: put the files in place

~/.claude/skills/vc-industry-research/SKILL.md

Copy the whole skill folder; for one project use .claude/skills/vc-industry-research/

Step by step, with commands for each platform: How to install skills in Claude Code: five ways

Questions about vc-industry-research

How do I install vc-industry-research in Claude Code?

Run npx skills add zebbern/claude-code-guide --skill vc-industry-research -a claude-code. The skill file lands at ~/.claude/skills/vc-industry-research/SKILL.md.

What does vc-industry-research do?

It produces institutional-style industry research: a sector deep-dive, a deal memo or a market overview, with numbered exhibits and a source behind each data point.

Which formats and languages does it support?

Reports come out in Chinese or English, picked from your query. PDF is the default; DOCX and PPTX need an explicit request.

Source text

SKILL.md · MIT
---
name: vc-industry-research
description: "Generate professional primary market / venture capital industry research reports, including sector deep-dives, investment memos, and market analysis. Produces detailed PDF reports covering TMT, consumer, healthcare, and industrials. Triggered by requests to analyze an industry, create a market report, write a sector deep-dive, or generate any PE/VC-style research document in Chinese or English."
---

# Primary Market Industry Research Report

Generate professional industry research reports in an institutional primary-market (PE/VC) research style.

## Reference Source

- **Type**: Uploaded artifact (PDF)
- **Reference File Type**: PDF
- **Languages**: Chinese or English (auto-detect from user query; default to user's language)

## Supported Outputs

- PDF (default)
- DOCX
- PPTX (if explicitly requested)

**Default output**: PDF. If user explicitly requests DOCX or PPTX, honor that request.

## Workflow

1. **Understand the research scope** from user query: target industry, sub-topics, depth, page count
2. **Determine report style** based on user preference or task context:
   - **Style A (Deep Discussion)**: Opinion-heavy, TMT/tech focus, numbered chapters (01, 02...), no TOC
   - **Style B (Traditional Sector)**: Data-heavy, many charts and tables, TOC with multi-level numbering
3. **Plan content structure** using the appropriate structure contract (see references)
4. **Research and gather data** using web search and data source tools as needed
5. **Review investment & financing history** for the sector: search for key funding rounds, deal sizes, lead investors, IPO/exit events, and capital flow trends in the target industry. Sources include Crunchbase, PitchBook, CB Insights, IT桔子, 烯牛数据, and public deal announcements
6. **Generate the report** following the style and structure contracts precisely
7. **Review for completeness**: ensure all exhibits are numbered, sources cited, and formatting consistent

## Style Selection Guide

Choose the report style based on context:

| Indicator | Use Style A (Deep Discussion) | Use Style B (Traditional) |
|-----------|------------------------------|---------------------------|
| Sector | TMT, AI, Software, SaaS | Consumer, Healthcare, Industrials, Materials |
| Tone | Opinion-forward, thesis-driven | Data-driven, objective |
| Charts | Moderate (native charts, benchmark tables for AI research) | Dense (pie charts, bar charts, line charts) |
| TOC | No | Yes, with 3-level hierarchy + dot-leaders + page numbers |
| Chapter numbers | 01, 02, 03... in red/dark-red | 1, 1.1, 1.2, 2.1... in black |
| Page count | 15-25 pages typical | 30-60 pages typical |

For detailed style rules, see [references/style_contract.md](references/style_contract.md).

## Structure Templates

Two primary structure patterns are available. See [references/structure_contract.md](references/structure_contract.md) for full details.

### Style A Structure (Deep Discussion)

```
Cover Page:
  [White background]
  [Institution logo (top-right): icon + institution name (bilingual)]
  [Main title: bold KaiTi, left-aligned, large, dark-red accent underline]
  [Author line: "Cr.: [Author Name]"]
  [Date line: "Date: YYYY-Mon"]
  [QR code (right side)]

Executive Summary (~1 page)
  [Bordered/quoted paragraph block]

01 [Chapter Title]
  [Section Heading in red/dark-red KaiTi]
  [Subsection Heading in red/dark-red KaiTi]
```

### Style B Structure (Traditional Sector)

```
Cover Page:
  [White background, ultra-minimal]
  [Full title: centered, KaiTi, large]
  [Institution logo: centered below title]
  [Institution name: centered below logo]
  [Date: centered, bottom area (YYYY.MM format)]

Table of Contents (page 2-3)
  [Title "目录": centered, large character spacing]
  [1  [Main Chapter]..................p3]
  [  1.1 [Section]...................p3]

Content Pages:
  [Header: report title centered + horizontal rule below]
  [Footer: page number]
```

## Typography Strategy

### For Chinese-language reports
- **Headings**: KaiTi (楷体) — calligraphic, distinctive institutional feel
- **Style A body**: SimSun (宋体) — formal serif tone
- **Style B body**: STKaitiSC-Regular (华文楷体) — consistent with heading font family
- **Latin text**: Times New Roman (body + italic for sources), Arial Bold (header emphasis)
- **Chart labels**: DengXian (等线) or Calibri for English labels
- All document text paths use CJK-capable fonts consistently

### For English-language reports
- **Headings**: Georgia or Times New Roman — institutional serif feel
- **Body text**: Times New Roman or Garamond — formal, readable
- **Chart labels / tables**: Calibri or Arial
- **Header emphasis**: Arial Bold

### General
- When exact reference fonts unavailable, prefer fonts from the same visual family
- For bilingual content, ensure CJK and Latin fonts are harmonized in weight and size

## Exhibit Numbering

- **Figures**: Sequential numbering with caption below — "图 N" (Chinese) or "Figure N" (English)
- **Tables**: Sequential numbering with caption above — "表 N" (Chinese) or "Table N" (English)
- Data source note below each exhibit: "数据来源:xxx" (Chinese) or "Source: xxx" (English)
- Reset numbering for each major section in Style B; continuous in Style A

## Source Citation Rules

- Every data point, statistic, or claim must have a source
- Inline: cite source parenthetically or in footnote
- Exhibits: "数据来源:" (Chinese) or "Source:" (English) below each figure/table
- Preferred sources: government databases, industry associations, public company filings, reputable analyst reports, authoritative media

## Key Quality Checks

- [ ] Cover page matches selected style (Style A or B) precisely
- [ ] Color palette matches selected style — NO custom dark themes or modern gradients
- [ ] All chapter/section numbering is consistent and matches selected convention
- [ ] TOC has dot-leaders AND page numbers (Style B only)
- [ ] Running header with horizontal rule on all content pages (Style B)
- [ ] All figures and tables are numbered and captioned
- [ ] All data points have source attribution
- [ ] Typography applied consistently per language (CJK fonts for Chinese reports, serif fonts for English reports)
- [ ] Tables have clean borders: no vertical rules, header row has top/bottom borders, table has top/bottom thick borders (Style B)
- [ ] Institution/publisher identity present (logo area or header text)
- [ ] No placeholder text left in document

© zebbern · MIT · zebbern/claude-code-guide

Similar skills

All skills for Finance and business →

From the same set86

The whole set →
raycasting-optimization The raycasting-optimization rule covers ways to reduce Three.js raycasting work, from filtering objects by layer to using BVH or GPU picking. Useful when a scene has complex meshes or frequent pointer checks. CX Codex +1 ★ 4,719repo stars mobile-optimization mobile-optimization is a rule for accelerating Three.js scenes on smartphones and tablets. It reduces GPU load and memory use, helping maintain a stable frame rate. CX Codex +1 ★ 4,719repo stars webxr-setup The webxr-setup rule for Claude Code guides building VR and AR scenes in Three.js WebXR. It helps coding agents set up render loops, controllers, and hit-testing. CX Codex +1 ★ 4,719repo stars error-handling-recovery The error-handling-recovery rule covers WebGL context loss, resource rebuilding, and fallback UI. Use it when a Three.js scene must recover from graphics failures. CX Codex +1 ★ 4,719repo stars tsl-complete-reference The tsl-complete-reference rule for Claude Code provides a TSL reference for writing node shaders without invalid syntax. CX Codex +1 ★ 4,719repo stars test-suite-architect test-suite-architect sets up QA infrastructure based on Google Testing Standards and OWASP: AAA test case templates, P0-P4 bug tracking, quality gate checks, and LLM test execution. CX Codex +1 ★ 4,719repo stars ssh-penetration-testing ssh-penetration-testing guides SSH service assessments, from configuration checks to credential testing and port forwarding. Use it to plan an authorized SSH security review. CX Codex +1 ★ 4,719repo stars tos-clause-scanner tos-clause-scanner takes a terms-of-service document or privacy policy and returns a structured audit: unfair clauses, hidden data permissions, auto-renewal traps. CX Codex +1 ★ 4,719repo stars

Project sponsors

Companies that keep this analytics open