agentleFS
Sign inStart free
d-wweid-wwei/openclaw-financial-services/skills/fsi-ib-teaser/SKILL.md

fsi-ib-teaser

Skill16 starsChanged 9 months agoApache-2.0View on GitHub

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".

The file

We split this skill into the rules it gives an agent

8 rules. About 0 are common, 8 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈8

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Ensure the teaser doesn't inadvertently identify the company:

    line 62
  2. Distinctive:

    No company name, brand names, or product names

    line 63
  3. Distinctive:

    No specific city (use region: "Southeast US", "Midwest")

    line 64
  4. Distinctive:

    No named customers or partners

    line 65
  5. Distinctive:

    No employee count if it's too distinctive

    line 66
  6. Distinctive:

    No logos, screenshots, or identifiable imagery

    line 68
  7. Distinctive:

    Use aspirational but accurate language — "leading", "differentiated", "high-growth" are fine if true

    line 80
  8. Distinctive:

    Always have the client and legal review before distribution

    line 82

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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)

MetricValue
Revenue$XXM
Revenue GrowthXX% CAGR
EBITDA$XXM
EBITDA MarginXX%
EmployeesXXX

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free