post-meeting-execution

post-meeting-execution is a skill for Claude Code, Codex from swan-gtm/gtm-skills. It costs 124 tokens per session (3,711 once invoked), scanned A, original, MIT.

A post-meeting workflow that pulls a sales-meeting transcript, classifies the outcome, updates the account assessment, and drafts a follow-up email in the meeting owner's style.

In plain words
What is it for?
It helps process meeting notes, score qualification, update a CRM account, and prepare follow-up messages after external sales meetings.
Why use it?
It reduces the manual work after a sales call and helps prevent follow-ups or important meeting details from being missed. Its outputs are sent for review before use.

Skill for Claude CodeCodex

Written for no agent in particular: nothing here depends on one.

Good fit It helps process meeting notes, score qualification, update a CRM account, and prepare follow-up messages after external sales meetings.

Compare 6 skills from other repositories ↓
Install with agentmods
npx agentmods add skills/swan-gtm/gtm-skills/post-meeting-execution
Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent
npx skills add swan-gtm/gtm-skills --skill post-meeting-execution
Clone the repo
git clone --depth 1 https://github.com/swan-gtm/gtm-skills

Made for: Claude Code, Codex.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

agentmods badge for post-meeting-execution

README.md
[![agentmods](https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/post-meeting-execution/github.svg)](https://agentmods.dev/skills/swan-gtm/gtm-skills/post-meeting-execution)
Your own site
<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/post-meeting-execution"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/post-meeting-execution/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

agentmods 80×15 button for post-meeting-execution

Your own site · 80×15
<a href="https://agentmods.dev/skills/swan-gtm/gtm-skills/post-meeting-execution"><img src="https://agentmods.dev/badge/skills/swan-gtm/gtm-skills/post-meeting-execution.svg" alt="Reviewed on agentmods" width="80" height="20"></a>
Per session 124 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.
When invoked 3,711 The whole file, excluding the scripts and references it only reads on demand.
Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits
  • NVIDIA SkillSpector warn 7 Sept 2026
SkillSpector: 2 findings, up to medium

These are SkillSpector’s own severities. On a checked sample its high-severity flags on skills were ~96% false positives — a documented command, a public API, a “never do X” rule — so we show them as a caution to read, not a verdict. Why →

  • medium Output Handling · line 179
    Output size or generation rate is not bounded. Unbounded output enables denial-of-service through resource exhaustion, log flooding, or context-window stuffing.
    Fix: Set explicit limits on output length, generation count, and rate. Use max_tokens and truncation to prevent unbounded output.
  • medium Excessive Agency · line 221
    Skill enables autonomous high-impact decisions without human-in-the-loop verification. Critical operations (destructive commands, financial transactions, data deletion) should require explicit user confirmation.
    Fix: Add human-in-the-loop confirmation for destructive, irreversible, or high-impact operations. Never auto-execute commands that modify files, send data, or alter system state.
How audits are shown
Origin original No closer match found in the catalogue.
Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

ModelPer sessionOnce invoked
Fable 5.1 $0.00124 $0.03711
Opus 5 $0.00062 $0.01855
Sonnet 5 $0.00025 $0.00742
Haiku 4.5 $0.00012 $0.00371

Measured 9d ago against content hash 61b39df9bb61, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-12, from the pricing page.

Security

Grade A, and why

post-meeting-execution scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 9d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

skills/jeremy-hurst/post-meeting-execution/SKILL.md · 222 lines

How it starts

The opening of the file, as written. The whole thing — 222 lines — stays where its author put it; the contents beside it link to each section on GitHub.

Post-meeting execution

Template placeholders

Replace every {{...}} before enabling. See the setup checklist reference for the full setup list.

  • {{MEETING_OWNER}} — Person whose meetings this skill processes (one instance per person)
  • {{MEETING_NOTES_TOOL}} — Your meeting-notes tool (e.g. Circleback, Fireflies, Gong)
  • {{CRM}} — Your CRM (e.g. HubSpot, Attio, Salesforce)
  • {{REVIEW_CHANNEL}} — Slack channel where all post-meeting outputs post for review
  • {{INTERNAL_DOMAIN}} — Your company email domain, to tell internal from external attendees
  • {{FOLLOWUP_SCENARIOS_SKILL}} — Sub-skill: meeting-outcome categories, classification logic, per-category email frameworks
  • {{VOICE_GUIDE_SKILL}} — Sub-skill: the owner's tone, formatting, greeting style, approved links
  • {{LEAD_SCORING_SKILL}} — Sub-skill: your lead scoring & qualification methodology
  • {{ENTERPRISE_ACV_THRESHOLD}} — Deal size above which an account gets full sales treatment vs. self-serve (default: $20K)
  • {{SALES_ACTIVE_TAG}} — Workspace tag marking accounts with a live sales conversation
  • {{METRICS_LOG}} — Optional: spreadsheet/event log where external meetings are recorded for GTM metrics

Overview

After every meeting involving {{MEETING_OWNER}}, run a structured workflow in two phases:

  1. Deal creation decision — qualification scoring, human confirmation, contact/stakeholder loading
  2. Follow-up email — classify the outcome, draft in the owner's voice, send for approval

Non-blocking errors: memory, enrichment, and {{CRM}} write failures are non-blocking — log the error in the review item and continue; a failed step is never a reason to skip subsequent steps. The only blocking failure is a missing meeting record (Step 1).


Step 1 — Pull Meeting Context

Retrieve the full record from {{MEETING_NOTES_TOOL}}: summary, full transcript, action items, attendees (names, titles, companies), any logged decisions. If your notes tool auto-emails attendees the summary and recording, do NOT duplicate that in the follow-up email.

Read the full file on GitHub · 222 lines

Files

What ships with it

1 file beside SKILL.md in the same directory: the scripts, references and assets a skill reads on demand. Not counted in the per-session cost; read them before you install if any of them is executable.

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

  1. 9d ago First seen · 222 lines · 124 tokens per session scan A 61b39df9bb61

Subscribe to this mod's changes

post-meeting-execution is a skill published in the GitHub repository swan-gtm/gtm-skills (153 stars, last pushed 2d ago), licensed MIT. It adds 124 tokens to every session and 3,711 once invoked, about $0.0006 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-09-03.

Related

Other skills, from other repositories