Sentiment check
Customer support skills for Claude Code and AI agents. Ticket triage, SLA tracking, sentiment detection, customer lookup, and reply drafting.
npx -y skills add composio-community/support-skills --skill sentiment-checkAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 13 stars13 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Analyze customer message text for sentiment, urgency, and emotional tone.
SKILL.md
3.1 KB, 751 tokens by cl100k_base, as published. Nobody here has run it
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:
- Run
composio search "get ticket details from Gorgias"in Bash - Run
composio execute GORGIAS_GET_TICKET --get-schemain Bash to inspect inputs if needed, then runcomposio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}'in Bash. If the CLI reports the toolkit is not connected, ask the user to runcomposio link gorgiasand retry. - 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]
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.