本文へ移動
cccskills
無料GitHub で公開

vc-industry-research

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.

インストール方法を見る

含まれるファイル(3)

  • SKILL.md6.4 KB
  • references/structure_contract.md10.7 KB
  • references/style_contract.md9.8 KB

SKILL.md(原文)

インストールする前に、エージェントに与えられる指示の中身を確認できます。

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:

IndicatorUse Style A (Deep Discussion)Use Style B (Traditional)
SectorTMT, AI, Software, SaaSConsumer, Healthcare, Industrials, Materials
ToneOpinion-forward, thesis-drivenData-driven, objective
ChartsModerate (native charts, benchmark tables for AI research)Dense (pie charts, bar charts, line charts)
TOCNoYes, with 3-level hierarchy + dot-leaders + page numbers
Chapter numbers01, 02, 03... in red/dark-red1, 1.1, 1.2, 2.1... in black
Page count15-25 pages typical30-60 pages typical

For detailed style rules, see references/style_contract.md.

Structure Templates

Two primary structure patterns are available. See 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

レビュー

まだレビューはありません。使ってみた感想をお寄せください。

同じリポジトリのスキル

概要と使いどころ

Simulates academic peer review, evaluating papers across Originality, Methodology, Results, and Writing to provide Major/Minor Revision recommendations with actionable feedback. Triggers when a user asks to "review my paper," "simulate peer review," or "give my paper a peer review.

日本語の概要は準備中です。原文の説明を表示しています。

zebbern/claude-code-guide4,6562026年10月10日 更新

This skill should be used when the user asks to "attack Active Directory", "exploit AD", "Kerberoasting", "DCSync", "pass-the-hash", "BloodHound enumeration", "Golden Ticket", "Silver Ticket", "AS-REP roasting", "NTLM relay", or needs guidance on Windows domain penetration testing.

日本語の概要は準備中です。原文の説明を表示しています。

zebbern/claude-code-guide4,6562026年10月10日 更新

This skill should be used when the user asks to "test API security", "fuzz APIs", "find IDOR vulnerabilities", "test REST API", "test GraphQL", "API penetration testing", "bug bounty API testing", or needs guidance on API security assessment techniques.

日本語の概要は準備中です。原文の説明を表示しています。

zebbern/claude-code-guide4,6562026年10月10日 更新

Generate multiple radically different interface designs for a module using parallel sub-agents. Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".

日本語の概要は準備中です。原文の説明を表示しています。

zebbern/claude-code-guide4,6562026年10月10日 更新

Interactive system flow tracing across CODE, API, AUTH, DATA, NETWORK layers with SQLite persistence and Mermaid export. Use for security audits, compliance documentation, flow tracing, feature ideation, brainstorming, debugging, architecture reviews, or incident post-mortems. Triggers on audit, trace flow, document flow, security review, debug flow, brainstorm, architecture review, post-mortem, incident review.

日本語の概要は準備中です。原文の説明を表示しています。

zebbern/claude-code-guide4,6562026年10月10日 更新

Authentication patterns: session vs JWT vs OAuth comparison, provider selection (NextAuth, Clerk, Supabase Auth), security checklist, and common mistakes. Use when implementing auth, reviewing auth flows, or choosing auth providers.

日本語の概要は準備中です。原文の説明を表示しています。

zebbern/claude-code-guide4,6562026年10月10日 更新

zebbern のスキルをすべて見る

このスキルの問題を報告する