Agent skill

meeting-prep

Strategic meeting prep grounded in lookalike deals.

activeReaches the webInstructions only487 words

From octavehq/lfgtm · 28 skill entries · 11 · pushed 2026-11-02

What it does when it runs

Strategic meeting prep grounded in lookalike deals. Opens with the closest won and lost deals and what happened on their calls, charts what each attendee is likely to raise, names the approved content to bring, structures the pitch around the company's own framework when one exists, and ends on the next best action (the move, why now, the strategy behind it, and the follow-through). Rendered as self-contained HTML, or as Markdown in chat and agent hosts, with copy-ready prompts to continue. Use when user says "meeting prep", "battle plan", "prep me for my meeting", "prep for my call", "what should I expect from this meeting", "deals like this one", or wants a coached game plan for an upcoming meeting. Do NOT use for account reference documents; use /octave:research instead.

Automated analysis of the skill and the 8 files bundled beside it. A skill’s own description is written to be selected by an agent, so it describes the job and not the dependencies.

Keys and connectors you must supply: None found.
Hosts it reaches: fonts.googleapis.com
fonts.gstatic.com
Tool permissions it declares: No allowed-tools in the frontmatter. It only issues instructions, so there is nothing to bound.
Actions present in the files: None. Instructions only.

Our read

Computed from the artifact. Nothing here has been run, so none of it is a claim about how well the skill works — only about what it is and what it needs.

Maintenanceactive

Pushed within the last 30 days, with commits in the last 90.

CouplingReaches the web

Reaches a third-party host at runtime, but needs no key of its own.

Blast radiusInstructions only

No shell, no file writes, no network calls in the skill or its bundled files.

What it does to your systemsUnreviewed

The source changed after it was read, so the earlier reading is not shown.

Sends messages: Unreviewed
Writes records: Unreviewed
Spends credits: Unreviewed
Needs credentials: No key or connector found by pattern match

Read from source, not tested by running. Machine-read from SKILL.md at commit 6facb2c with jev-1.13.0; labels that write, send or spend were also checked against the cited line by a second reviewer. How this is read

Substancebrief

Under 600 words, no bundled reference files.

LicenceMIT

Permits redistribution with attribution, per the repository.

Ask about meeting-prep

Opens your assistant with this page's recorded context. Check the linked sources before relying on it.

Is this safe to install?Claude ChatGPT

Adapt it to my stackClaude ChatGPT

What else do I need for it to workClaude ChatGPT

Rather ask a human? Talk to Cheetah

Install it

View source on GitHub ↗

git clone --depth 1 --filter=blob:none --sparse https://github.com/octavehq/lfgtm.git /tmp/lfgtm
git -C /tmp/lfgtm sparse-checkout set "skills/meeting-prep"
mkdir -p ~/.claude/skills/meeting-prep
cp -R "/tmp/lfgtm/skills/meeting-prep/." ~/.claude/skills/meeting-prep/

Picked up without a restart. A project skill of the same name is shadowed by your personal one. For one repository only, swap ~/.claude/skills for .claude/skills. Claude Code docs ↗

Or take the whole library

This repo ships a .claude-plugin manifest, so Claude Code can install all 28 skills at once. Plugin skills are invoked as /<plugin>:<skill>, so they never collide with your own.

/plugin marketplace add octavehq/lfgtm
/plugin

The folder is the same in every client that implements the format — 46 of them — so if yours is not above, only the destination changes.

The skill

Source on GitHub ↗

Reproduced in full from octavehq/lfgtm/blob/228b8983ef7bba9143c3de359bfd63f630dcb9b8/skills/meeting-prep/SKILL.md, which is licensed MIT (repository). 487 words, 5 headings.

/octave:meeting-prep - Strategic Meeting Prep

Run the task

Read the task method before selecting context, claims, or output. It is the execution method for this skill. Supporting templates supply structure and styling; populate them from the task method and current evidence, not their illustrative figures or assertions.

Infer meeting type and duration. Use one content schema: lookalikes, context, goals, competitive, expect, content, say-ask, next-action, in that order, then the keep-going prompts. The outline, HTML IDs, review, and delivery summary use meeting-sections.md. The scaffold supplies layout, not a second content schema.

Resolve the account and deal first, then lead the analysis with seeded ask_octave calls about the account and its lookalike deals, and verify what they cite with the narrow tools. The two sections that set this prep apart, lookalike deals and the next best action, are built by lookalikes and expectations and strategy gap. Never invent quotes, numbers, customers, roles or content; counts carry their base; other customers stay internal.

Use GTM context for strategic tasks and evidence and inputs for material claims and missing facts. A narrow list/get or a render-only handoff does not require unrelated research. Read host runtime for available tools, portable resource paths, routing, and review fallback.

Resolve current tool schemas before execution; use returned IDs and pagination. Inventory rows locate records; hydrate selected entities/resources before relying on their contents. Reuse supplied or inherited context and authorization. Ask grouped questions only for material unresolved inputs, continue independent work, incorporate replies, and recheck affected output.

Usage

/octave:meeting-prep <target> [--type <meeting-type>] [--style <preset>]

References by task

Read the lookalike and strategy-gap references for every full prep run, the positioning references only when choosing an approach, then the format/layout references when rendering. Do not repeat intake or change approved claims when routing to a renderer.

Delivery and changes

Deliver the asset id or URL when the prep was published and the copy-ready "keep going" prompts described in meeting-sections.md, so a user or agent can fetch the prep through the Octave MCP and continue. In a host that cannot render HTML (ChatGPT, Claude chat, an internal agent), deliver the same sections as Markdown.

Apply output readiness to text and artifacts. HTML also uses the review protocol and the matching format checks. A working preview can be shared with its status; unrun checks are NOT RUN. Reviewers return findings on an immutable version; one author applies edits and rechecks the final version.

For visual output, inherit the selected sender/workspace brand through brand kit usage; honor an explicit override and avoid repeated brand extraction. Public hosting requires the approved audience and publish manifest, followed by URL/access/link verification.

For comparisons, trends or rates, use the analytics contract. Only requested persistence loads workspace mutations; report changes as applied only after scoped readback.

Files bundled with it

These load only when the skill asks for them, so they cost nothing until it runs.

Other skills for the same job

Different authors, same problem. Matched on the words in the skill name, across every library in the catalogue except this one.

meeting-prep-cc by BrianRWagner · 450
meeting-prep by explorium-ai · 354
meeting-prep-brief by Othmane-Khadri · 60
meeting-prep-brief by JJenglert1 · 59
meeting-prep by GTMify · 25
meeting-prep by etrebels · 21
meeting-prep by ekatasingh1107 · 2
gtm-meeting-prep by rvanshur · 2

Need help setting it up?

This page tells you what meeting-prep does and what it needs. Cheetah builds the agent setup it runs inside: data, CRM, sequencing and the guardrails.

Book a call →

The directory stays free. There is nothing gated behind this.