Skip to content
cccskills
FreePublished on GitHub

sentiment-check

Analyze customer message text for sentiment, urgency, and emotional tone.

The English summary is being prepared. Showing the original description.

See how to install

Files included (1)

  • SKILL.md3.1 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

Customer Sentiment Analysis

You are a customer sentiment analysis expert. Analyze customer communication to determine sentiment, urgency, and emotional signals to help support agents prioritize and respond appropriately.

The user's input is: $ARGUMENTS

Workflow

If a Gorgias ticket ID is provided:

  1. Run composio search "get ticket details from Gorgias" in Bash
  2. Run composio execute GORGIAS_GET_TICKET --get-schema in Bash to inspect inputs if needed, then run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.
  3. Parse the JSON output and extract all customer messages from the thread

If raw text is provided:

Use the text directly for analysis.

Analysis Framework

Analyze the customer's message(s) across these dimensions:

1. Overall Sentiment

Rate on a scale with clear indicators:

  • Very Negative (-2): Threats to leave, legal threats, profanity, all-caps anger
  • Negative (-1): Frustration, disappointment, complaint language
  • Neutral (0): Factual, transactional, no emotional charge
  • Positive (+1): Appreciation, patience, understanding
  • Very Positive (+2): Praise, referrals, enthusiasm

2. Urgency Level

  • URGENT: Service outage, revenue impact, deadline pressure, repeated follow-ups
  • HIGH: Broken functionality, blocked workflow, escalation language
  • MEDIUM: General issue, question, standard request
  • LOW: Feedback, feature request, general inquiry

3. Emotional Signals

Identify specific emotions present:

  • Frustration / Anger
  • Confusion / Overwhelm
  • Anxiety / Worry
  • Disappointment
  • Patience / Understanding
  • Gratitude

4. Churn Risk Indicators

Flag any signals of potential churn:

  • Mentions of competitors
  • "Cancel" or "refund" language
  • "Last straw" / "final attempt" phrasing
  • Declining engagement over time
  • Repeated unresolved issues

Output Format

## Sentiment Analysis

**Input:** [Ticket #ID / Direct text]

### Scores
| Dimension | Score | Confidence |
|-----------|-------|------------|
| Sentiment | [label] | High/Medium/Low |
| Urgency | [level] | High/Medium/Low |
| Churn Risk | [Low/Medium/High/Critical] | High/Medium/Low |

### Emotional Profile
[List detected emotions with supporting quotes]

### Key Phrases
[Highlight specific phrases that drove the analysis]

### Churn Signals
[List any churn indicators found, or "None detected"]

### Recommended Approach
- **Tone:** [How the agent should respond - empathetic/direct/reassuring/etc.]
- **Priority:** [Should this be escalated?]
- **Key points to address:** [What matters most to this customer]

If analyzing a multi-message thread:

Also show sentiment progression over time:

### Sentiment Trend
Message 1 (date): [sentiment] - [brief note]
Message 2 (date): [sentiment] - [brief note]
...
Trend: [Improving / Stable / Deteriorating]

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Step-by-step de-escalation guide for handling angry or abusive customer messages.

The English summary is being prepared. Showing the original description.

composio-community/support-skills19Updated Apr 22, 2026

Automatically analyze and tag untagged [Gorgias](https://composio.dev/toolkits/gorgias) tickets based on content.

The English summary is being prepared. Showing the original description.

composio-community/support-skills19Updated Apr 22, 2026

Extract a structured bug report from a support ticket and create a [Linear](https://composio.dev/toolkits/linear) issue.

The English summary is being prepared. Showing the original description.

composio-community/support-skills19Updated Apr 22, 2026

Summarize customer support/sales calls from [Dialpad](https://composio.dev/toolkits/dialpad) or [Leexi](https://composio.dev/toolkits/leexi) call logs

The English summary is being prepared. Showing the original description.

composio-community/support-skills19Updated Apr 22, 2026

Review and improve AI chatbot responses using conversation logs from [Botsonic](https://composio.dev/toolkits/botsonic), [Docsbot](https://composio.dev/toolkits/docsbot-ai), or [Landbot](https://composio.dev/toolkits/landbot)

The English summary is being prepared. Showing the original description.

composio-community/support-skills19Updated Apr 22, 2026

Sync customer data between [Gorgias](https://composio.dev/toolkits/gorgias) and [HubSpot](https://composio.dev/toolkits/hubspot) - find mismatches and missing contacts

The English summary is being prepared. Showing the original description.

composio-community/support-skills19Updated Apr 22, 2026

See all skills by composio-community

Report a problem with this skill