meeting-outcome-logger

Classifies customer meeting outcomes and sentiments into CRM-ready records with attendees and durations.

1|Updated Mar 23, 2026
One-click install
npx skills add https://github.com/stephenrogan/csm-skills --skill meeting-outcome-logger
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: meeting-outcome-logger
Source: https://github.com/stephenrogan/csm-skills/tree/main/skills/meeting-outcome-logger
Command: npx skills add https://github.com/stephenrogan/csm-skills --skill meeting-outcome-logger

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Captures and structures the outcomes, sentiment, decisions, and next steps from customer meetings, turning unstructured notes into a CRM-ready record that’s easy to share and act on.

Core Features & Use Cases

  • Classifies meeting outcomes (e.g., Positive progress, Concern surfaced, Escalation needed) and attaches a sentiment assessment to guide follow-up.
  • Produces a structured CRM record including attendees, duration, decisions, actions, and account status changes.
  • Supports downstream workflows by exporting consistent data for reporting, health signals, and renewal planning.
  • Use Case: After a QBR, generate a CRM log that records decisions, assigned owners, deadlines, and any risks or opportunities discussed.

Quick Start

After a customer meeting, provide the account name, meeting type, attendees, duration, a brief description of what happened, decisions made, and actions committed.

Frequently Asked Questions about meeting-outcome-logger

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I log customer meeting outcomes into a CRM-ready format?▼

Meeting notes are transformed into structured CRM records by capturing attendees, duration, decisions, actions, and account status changes. This process turns unstructured notes into a standardized, actionable format for downstream workflows.

How do I record sentiment and action items from a QBR?▼

Recording sentiment and action items from a QBR involves classifying the meeting outcome, assessing customer sentiment, and detailing assigned owners with deadlines. This generates a structured log for tracking risks and renewal planning.

Can I use this for escalations and ad hoc interactions?▼

Yes, you can use this for escalations and ad hoc interactions. The scope covers post-meeting recording across various meeting types, ensuring consistent data capture for health signals and follow-up actions regardless of the interaction type.

What is the best way to capture account status changes from meetings?▼

The best way to capture account status changes is to include them in the post-meeting input along with attendees and decisions. The skill enforces a standard CRM-friendly format that automatically incorporates these changes into the final record.

Does this workflow support downstream reporting and renewal planning?▼

Yes, this workflow supports downstream reporting and renewal planning by exporting consistent data. It classifies outcomes and captures sentiment, which directly feeds into health signals and structured reporting for your accounts.