conversation-intelligence

Analyze conversation data to identify speakers, recognize emotions, and extract key information.

2|Updated May 15, 2026
One-click install
npx skills add https://github.com/mashharuki/floci-sample --skill conversation-intelligence
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: conversation-intelligence
Source: https://github.com/mashharuki/floci-sample/tree/main/.agents/skills/conversation-intelligence
Command: npx skills add https://github.com/mashharuki/floci-sample --skill conversation-intelligence

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyannote.audio, faster-whisper, transformers, anthropic, spacy, ja-core-news-lg, numpy, scikit-learn, pydantic, pandas, pyannote.metrics, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill streamlines the process of analyzing conversation data, enabling users to efficiently extract valuable insights and automate various tasks related to speaker identification, emotion recognition, and information extraction.

Core Features & Use Cases

  • Speaker Identification: Automatically identify speakers in multi-party conversations and track their speaking times.
  • Emotion Recognition: Analyze the emotional tone of the conversation and provide insights into the speaker's emotional state.
  • Information Extraction: Extract key information such as who, what, when, where, why, and how from the conversation.
  • Use Case: Imagine you have a series of recorded meetings or customer interactions. Use this Skill to analyze the conversations, identify key topics, extract action items, and generate summaries for each conversation.

Quick Start

Use the conversation-intelligence skill to analyze the conversation data from the file 'meeting_transcripts.txt'.

Frequently Asked Questions about conversation-intelligence

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

FAQPage Schema
How do I automate speaker identification and emotion recognition from meeting transcriptions?

Automating speaker identification and emotion recognition from meeting transcriptions involves using libraries like pyannote.audio and transformers to track speaking times and analyze emotional states. This Skill applies these models to analyze multi-party conversation data and extract key information.

What is the best way to extract action items and key topics from customer interaction recordings?

The best way to extract action items and key topics from customer interactions is applying ASR and information extraction techniques. Using faster-whisper and anthropic libraries, this process identifies who, what, when, where, why, and how, generating actionable summaries from conversational data.

Can I analyze conversation data using pyannote.audio and faster-whisper together?

Yes, you can analyze conversation data using pyannote.audio and faster-whisper together. This Skill integrates pyannote.audio for speaker identification, faster-whisper for ASR, and transformers for emotion recognition to process multi-party conversations and track speaking times.

Do I need specific Python models to perform conversation analysis and information extraction?

Yes, performing conversation analysis and information extraction requires specific Python models and libraries. You need pyannote.audio, faster-whisper, transformers, anthropic, and spacy, alongside the ja-core-news-lg model, to execute ASR, emotion recognition, and data extraction.

How does conversation analysis handle multi-party speaker identification and speaking time tracking?

Conversation analysis handles multi-party speaker identification by applying pyannote.audio to differentiate speakers in the audio stream. It tracks speaking times and recognizes emotional tones, providing deep insights into each participant's state during meetings or customer interactions.

What are the limitations when using transformers for emotion recognition in conversation data?

Limitations when using transformers for emotion recognition in conversation data depend heavily on the accuracy of the underlying ASR models and the quality of the input audio. Effective information extraction requires clear meeting transcriptions and appropriate model configurations.