teaser
Draft anonymous one-page company teasers for sell-side M&A processes. Creates a compelling summary without revealing the company's identity, designed to gauge buyer interest before NDA execution. Triggers on "teaser", "blind teaser", "anonymous profile", "one-pager for process", or "draft teaser for sell-side".
What this skill does
# Teaser ## Workflow ### Step 1: Gather Inputs - Company description (what they do, how they make money) - Sector / industry - Key financial metrics: revenue, EBITDA, growth rate, margins - Geographic footprint - Key selling points (3-5 highlights) - What to anonymize vs. disclose - Target buyer audience (strategic, financial, or both) ### Step 2: Teaser Structure One page, professionally formatted: **Header** - Deal code name (e.g., "Project [Name]") - Sector descriptor (e.g., "Leading Specialty Industrial Services Platform") - "Confidential — For Discussion Purposes Only" **Company Description** (2-3 sentences) - What the company does, without naming it - Market position (e.g., "a leading provider of...", "a top-3 player in...") - Geography (region-level, not city-specific) **Investment Highlights** (4-6 bullet points) - Market leadership / positioning - Revenue quality (recurring %, retention, diversification) - Growth profile and trajectory - Margin profile and expansion opportunity - Management team strength - Strategic value / synergy potential **Financial Summary** (table or key metrics) | Metric | Value | |--------|-------| | Revenue | $XXM | | Revenue Growth | XX% CAGR | | EBITDA | $XXM | | EBITDA Margin | XX% | | Employees | XXX | **Transaction Overview** (2-3 sentences) - What's being offered (100% sale, majority stake, growth equity) - Indicative timeline - Contact information for expressions of interest ### Step 3: Anonymization Check Ensure the teaser doesn't inadvertently identify the company: - No company name, brand names, or product names - No specific city (use region: "Southeast US", "Midwest") - No named customers or partners - No employee count if it's too distinctive - Revenue ranges instead of exact figures if the sector is small - No logos, screenshots, or identifiable imagery ### Step 4: Output - Word document (.docx) — one page, clean formatting - PDF version for distribution - Optional PowerPoint version (single slide) ## Important Notes - The teaser's job is to generate interest, not close a deal — keep it tight and compelling - Less is more — a good teaser makes buyers want to sign the NDA to learn more - Use aspirational but accurate language — "leading", "differentiated", "high-growth" are fine if true - Include enough financial detail to qualify serious buyers but not so much that tire-kickers waste your time - Always have the client and legal review before distribution - Track who receives the teaser — it becomes the outreach log for the process
Related in General
modeling-omnistudio-epc-catalog
IncludedSalesforce Industries CME EPC product-modeling skill for Product2-based catalog creation. Use when creating EPC products, configuring product attributes, building offer bundles with Product Child Items, or reviewing EPC DataPack JSON metadata for product catalog changes. TRIGGER when: user creates or updates Product2 EPC records, AttributeAssignment payloads, AttributeMetadata/AttributeDefaultValues, Offer bundles, or ProductChildItem relationships. DO NOT TRIGGER when: designing OmniScripts/FlexCards/Integration Procedures (use building-omnistudio-omniscript, building-omnistudio-flexcard, or building-omnistudio-integration-procedure), implementing Apex business logic (use generating-apex), or troubleshooting deployment pipelines (use deploying-metadata).
relationship-science-coach
IncludedUse this skill for direct, practical adult relationship coaching: couples conflict, repair, trust, marriage, dating, flirting, attachment patterns, emotional connection, sex, desire differences, eroticism, kink negotiation, affection, love languages, breakups, and long-term passion. Draw on Gottman, EFT and Hold Me Tight, attachment science, modern sex research, Perel, Nagoski, Kerner, Schnarch, Love and Stosny, and flexible love-language tools. Be concrete and low-hedge. Redirect only for imminent danger, abuse, coercive control, minors, non-consent, self-harm, stalking, or medical/legal/psychiatric decisions.
building-sf-integrations
IncludedSalesforce integration architecture and runtime plumbing with 120-point scoring. Use this skill to set up Named Credentials, External Credentials, External Services, REST/SOAP callout patterns, Platform Events, and Change Data Capture. TRIGGER when: user sets up Named Credentials, External Services, REST/SOAP callouts, Platform Events, CDC, or touches .namedCredential-meta.xml files. DO NOT TRIGGER when: Connected App/OAuth config (use configuring-connected-apps), Apex-only logic (use generating-apex), or data import/export (use handling-sf-data).
venue-templates
IncludedAccess comprehensive LaTeX templates, formatting requirements, and submission guidelines for major scientific publication venues (Nature, Science, PLOS, IEEE, ACM), academic conferences (NeurIPS, ICML, CVPR, CHI), research posters, and grant proposals (NSF, NIH, DOE, DARPA). This skill should be used when preparing manuscripts for journal submission, conference papers, research posters, or grant proposals and need venue-specific formatting requirements and templates.
let-fate-decide
IncludedDraws the 12 Houses of the Zodiac Tarot spread to inject entropy into planning when prompts are vague, ambiguous, or casually delegated. Interprets the spread to guide next steps. Use when the user says 'let fate decide', 'YOLO', 'whatever', 'idk', or other nonchalant phrases, makes Yu-Gi-Oh references, or when you are about to arbitrarily pick between multiple reasonable approaches. Prefer over ask-questions-if-underspecified when the user's tone is casual or playful rather than precision-seeking.
net-ops
IncludedCross-platform network troubleshooting (Windows, macOS, Linux) via local or remote shell. Use for: DNS broken, can't resolve hostnames, nslookup/dig works but apps fail, NRPT, WFP, scutil, /etc/resolver, systemd-resolved, /etc/resolv.conf, NetworkManager, VPN DNS leak residue (ProtonVPN/Mullvad/WireGuard/AnyConnect), AV/firewall blocking DNS or DoH, Tailscale DNS interaction, intermittent connectivity, remote diagnostics over SSH.