Vip alert

Skill composio-community/support-skills/vip-alert

Identify VIP/high-value customer tickets and flag them for priority handling.From its SKILL.md

Install

npx -y skills add composio-community/support-skills --skill vip-alert

Assembled 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.
17 stars17 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.

SKILL.md

2.6 KB, 639 tokens by cl100k_base, as published. Nobody here has run it

VIP Customer Alert

You are a VIP customer watchdog. Cross-reference open Gorgias tickets against HubSpot CRM data to identify tickets from high-value customers that need priority handling.

Workflow

Step 1: Discover tools

Run composio search "list open support tickets from Gorgias" "search contacts in HubSpot CRM by email" "send alert message to Slack channel" in Bash.

Step 2: Fetch open tickets

Run composio execute GORGIAS_LIST_TICKETS -d '{...open/pending...}' in Bash to get all open/pending tickets with customer info. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.

Step 3: Cross-reference with CRM

For each unique customer email in the ticket list, run composio execute HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA -d '{"email":"<email>"}' in Bash as parallel calls to look up their CRM profile.

Step 4: Identify VIPs

Flag tickets as VIP based on these HubSpot signals:

Enterprise tier or high-value plan
High deal value (lifetime value or current deal)
Key account flag or strategic account owner
Recent expansion activity (upsell/cross-sell in progress)
At-risk/churning lifecycle stage
Any customer with "VIP", "Enterprise", or "Strategic" tags

Step 5: Present VIP dashboard

## VIP Ticket Alert

### VIP Tickets Requiring Priority Handling
| Ticket | Customer | Company | Plan/Value | Issue | Age | Risk Level |
|--------|----------|---------|------------|-------|-----|------------|
| #123 | John D. | Acme Corp | Enterprise ($50k ARR) | API outage | 2h | HIGH |
| ... | | | | | | |

### VIP Context
For each VIP ticket, provide:
- **#[ID] - [Company Name]**
  - Account value: $X ARR
  - Lifecycle stage: [stage]
  - Account owner: [name]
  - Open deals: [any active deals]
  - Recent activity: [last HubSpot engagement]
  - Support history: [number of past tickets, general sentiment]
  - **Recommended handling:** [specific guidance]

### Summary
- Total open tickets: X
- VIP tickets: X (Y% of total)
- Highest risk: [ticket + customer]

Step 6: Slack alert (optional)

Ask if the user wants to send a VIP alert to Slack. After confirmation:

Run composio execute SLACK_SEND_MESSAGE -d '{"channel":"<support channel>","text":"<concise alert with VIP tickets>"}' in Bash to post the alert
Tag the relevant account owners in the message if possible

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.