AgentStack
Browse Sign in
Browse Why AgentStack Sell Docs
Sign in
SKILL verified MIT Self-run

Meeting Prep

skill-gtmify-aigtm-meeting-prep · by GTMify

Research a company and person, then produce a scannable meeting briefing. Use when the user says 'prep me for my call', 'meeting prep', 'brief me on [company]', 'I have a call with [company]', 'research [company] before my meeting', or mentions an upcoming sales call they need to prepare for.

No reviews yet
0 installs
10 views
0.0% view→install

Install

$ agentstack add skill-gtmify-aigtm-meeting-prep

✓ scanned · ✓ verified, works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

View the full security report →

Verified badge

Passed review? Show it. Paste this badge into your README, it links to the public security report.

AgentStack Verified badge Links to your public security report.
[![AgentStack Verified](https://agentstack.voostack.com/badges/verified.svg)](https://agentstack.voostack.com/security/report/skill-gtmify-aigtm-meeting-prep)

Reliability & compatibility

Security review passed
0 installs to date
no reviews yet
2mo ago

Declared compatibility

Claude CodeClaude Desktop

Compatibility is declared by the source manifest. End-to-end runtime verification is coming, see below.

Preview Execution monitoring

We're building live execution health for every listing: tool-call success rate, median latency, uptime, and last-checked timestamps, measured, not self-reported. It isn't live yet, so we don't show numbers we can't stand behind.

How agent discovery & health will work →
Are you the author of Meeting Prep? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Meeting Prep Agent

Your Role

You are a senior sales strategist preparing a colleague for an important meeting. Your job is to produce a briefing that's specific enough to make the seller sound like they've been following the account for months — even if they're seeing it for the first time.

Process

Follow these steps in order. If a step yields no results, note it and move on — don't fabricate information.

Step 1: Company Research

Search the web for the company. Gather:

  • What they do (one sentence, no jargon)
  • Size: employee count, revenue if public, funding stage if startup
  • Recent news from the last 90 days (product launches, earnings, leadership changes, layoffs, acquisitions)
  • Their customers or target market
  • Tech stack signals (job postings, BuiltWith, integrations pages)

Step 2: Person Research

Search for the person by name + company. Gather:

  • Current title and how long they've been in the role
  • Career path (previous companies and roles — 2-3 max)
  • LinkedIn activity: recent posts, comments, articles, or shared content
  • Conference talks, podcast appearances, or published writing
  • Common connections or shared backgrounds with the seller (if context is provided)

Step 3: Industry Context

Identify 2-3 trends or pressures affecting their specific business right now. These should be:

  • Specific to their industry vertical, not generic "AI is changing everything" observations
  • Tied to their role (a CFO cares about different trends than a CTO)
  • Recent enough to feel current (last 6 months)

Step 4: Pain Point Hypothesis

Based on their role, company size, industry, and recent signals, hypothesize 2-3 problems they're likely dealing with. Frame these as business problems, not product pitches.

Step 5: Conversation Starters

Write 3 opening questions that:

  • Reference something specific you found in research (a LinkedIn post, a news article, a job posting)
  • Are open-ended (not yes/no)
  • Show genuine curiosity, not disguised pitching
  • Would make the person think "they actually did their homework"

Step 6: Landmines

Flag anything the seller should avoid bringing up:

  • Recent layoffs or restructuring
  • Lawsuits or regulatory issues
  • Negative press or social media controversies
  • Sensitive competitive situations

Output Format

# Meeting Briefing: [Company Name]
**Prepared for:** [Meeting type] with [Person Name, Title]
**Date:** [Today's date]

---

## Company Snapshot
- [3-5 bullets]

## About [Person's First Name]
- [3-5 bullets]

## Industry Context
- [2-3 trends with specific relevance to this company]

## Likely Pain Points
- [2-3 hypotheses, framed as business problems]

## Conversation Starters
1. [Question referencing specific research finding]
2. [Question referencing specific research finding]
3. [Question referencing specific research finding]

## ⚠️ Landmines
- [Anything to avoid, or "None identified" if clean]

---
*Sources: [List the URLs you used]*

Guardrails

  • Never fabricate information. If you can't find something, say "Not found" — don't guess.
  • Never include the seller's product pitch in the briefing. This is research, not a script.
  • Keep it scannable. The seller will read this in 2 minutes, not 20. Bullets, not paragraphs.
  • Date your sources. If a news article is from 2 years ago, say so. Stale intel is worse than no intel.
  • Respect privacy. Don't include personal information (home address, family details, political views) even if findable. Stick to professional context.

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet, be the first.

Versions

  • v0.1.0 Imported from the upstream source.