AGENT SKILL

cim-builder

Structure and draft a Confidential Information Memorandum for sell-side M&A processes. Organizes company information into a professional, investor-ready document with consistent formatting and narrative flow. Use when preparing sell-side materials, drafting a CIM, or organizing company data for a sale process. Triggers on "CIM", "confidential information memorandum", "offering memorandum", "info memo", "draft CIM", or "sell-side materials".

License 许可
MIT
最近更新
2026-11-10
Stars
★ 1
Forks
0

01 前言 Front Matter

name
cim-builder
description
Structure and draft a Confidential Information Memorandum for sell-side M&A processes. Organizes company information into a professional, investor-ready document with consistent formatting and narrative flow. Use when preparing sell-side materials, drafting a CIM, or organizing company data for a sale process. Triggers on "CIM", "confidential information memorandum", "offering memorandum", "info memo", "draft CIM", or "sell-side materials".

03 SKILL.md 正文

CIM Builder

Workflow

Step 1: Gather Source Materials

Ask for available inputs:

  • Management presentations
  • Historical financials (3-5 years)
  • Budget/forecast
  • Company website and marketing materials
  • Customer data (anonymized if needed)
  • Org chart
  • Prior presentations or board decks
  • Quality of earnings report (if available)

Step 2: CIM Structure

Standard CIM table of contents:

I. Executive Summary (2-3 pages)

  • Company overview — what they do, why they win
  • Investment highlights (5-7 key selling points)
  • Financial summary — headline revenue, EBITDA, growth, margins
  • Transaction overview — what's being sold, indicative timeline

II. Company Overview (3-5 pages)

  • History and founding story
  • Mission and value proposition
  • Products and services description
  • Business model and revenue streams
  • Key differentiators and competitive advantages

III. Industry Overview (3-5 pages)

  • Market size and growth dynamics (TAM/SAM/SOM)
  • Key industry trends and tailwinds
  • Competitive landscape
  • Regulatory environment
  • Barriers to entry

IV. Growth Opportunities (2-3 pages)

  • Organic growth levers (new products, markets, pricing)
  • M&A / add-on opportunities
  • Operational improvements
  • Technology investments
  • White space analysis

V. Customers & Sales (3-5 pages)

  • Customer overview (number, segments, geography)
  • Top customer analysis (anonymized if pre-LOI)
  • Customer concentration and retention metrics
  • Sales process and go-to-market strategy
  • Pipeline and backlog

VI. Operations (2-3 pages)

  • Organizational structure
  • Key personnel
  • Facilities and geographic footprint
  • Technology and systems
  • Supply chain / vendor relationships

VII. Financial Overview (5-8 pages)

  • Historical income statement (3-5 years)
  • Revenue analysis — by segment, geography, customer type
  • EBITDA bridge and margin analysis
  • Balance sheet overview
  • Cash flow summary
  • Capital expenditure history
  • Working capital analysis
  • Management forecast / budget (if included)

VIII. Appendix

  • Detailed financial statements
  • Customer list (anonymized)
  • Product catalog
  • Management bios

Step 3: Drafting Guidelines

  • Tone: Professional, factual, compelling but not hyperbolic
  • Narrative: Tell a story — why this business is attractive, defensible, and positioned for growth
  • Data-driven: Support every claim with data. "Strong growth" → "Revenue grew at a 15% CAGR from 2021-2024"
  • Visuals: Charts and graphs for financial trends, market size, competitive positioning
  • Length: 40-60 pages total — enough detail to inform first-round bids, not so long buyers won't read it
  • Confidentiality: Include a disclaimer page. Anonymize sensitive customer data unless seller approves

Step 4: Output

  • Word document (.docx) with professional formatting
  • Separate Excel appendix with detailed financials
  • Charts and exhibits embedded in the document

Important Notes

  • The CIM is a sales document — lead with strengths, but don't hide material issues (buyers will find them in diligence)
  • Investment highlights should address the 3 things every buyer cares about: growth potential, margin profile, and defensibility
  • Financial normalization / pro forma adjustments should be clearly labeled and explained
  • Work with legal on the confidentiality disclaimer and any regulatory disclosures
  • Get management to review for factual accuracy before distribution
  • The CIM sets expectations on valuation — make sure the narrative supports the asking price

04 同仓库更多 Skills

YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

vercel-sandbox

Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

slack

Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

electron

Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

dogfood

Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

agent-browser

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.

★ 1
YYC-Cube
YYC-Cube/YYC3-Knowledge-Base

shadcn

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.

★ 1