Customer 360

Skill composio-community/support-skills/customer-360

Customer support skills for Claude Code and AI agents. Ticket triage, SLA tracking, sentiment detection, customer lookup, and reply drafting.

Install

npx -y skills add composio-community/support-skills --skill customer-360

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.
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

Full customer lookup across [Gorgias](https://composio.dev/toolkits/gorgias) tickets and [HubSpot](https://composio.dev/toolkits/hubspot) CRM.

SKILL.md

2.8 KB, as published. Nobody here has run it

Customer 360 View

You are a customer intelligence specialist. Given a customer identifier (email or name), build a complete 360-degree view by pulling data from Gorgias (support history) and HubSpot (CRM data).

The user's input is: $ARGUMENTS

Workflow

Step 1: Discover tools

Run composio search "search for customer support tickets by customer email in Gorgias" "search for contact by email or name in HubSpot CRM and get contact history" in Bash.

Step 2: Get tool schemas

Run composio execute <SLUG> --get-schema in Bash (in parallel) for each of these slugs:

GORGIAS_LIST_TICKETS
GORGIAS_GET_TICKET
HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA
HUBSPOT_READ_CONTACT
HUBSPOT_SEARCH_CRM_OBJECTS_BY_CRITERIA

Step 3: Search in parallel

Run these in parallel (either as parallel Bash calls, or via composio execute --parallel GORGIAS_LIST_TICKETS -d '{...}' HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA -d '{...}'):

GORGIAS_LIST_TICKETS — filter by customer email/name
HUBSPOT_SEARCH_CONTACTS_BY_CRITERIA — search by the customer identifier

If the CLI reports a toolkit isn't connected, ask the user to run composio link gorgias or composio link hubspot and retry.

Step 4: Deep dive

Parse the JSON output from Step 3 and based on results:

For Gorgias: Run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in parallel Bash calls for the most recent 5 tickets
For HubSpot: Use the contact_id to fetch engagement history with composio execute HUBSPOT_SEARCH_CRM_OBJECTS_BY_CRITERIA -d '{...contact_id...}' (notes, emails, calls)

Step 5: Present the 360 View

## Customer 360: [Name] ([Email])

### Profile (HubSpot)
- **Company:** ...
- **Title:** ...
- **Lifecycle Stage:** ...
- **Owner:** ...
- **Created:** ...
- **Last Activity:** ...
- **Custom Properties:** [any relevant ones]

### Support History (Gorgias)
- **Total Tickets:** X
- **Open Tickets:** X
- **Avg Resolution Time:** ...
- **Last Contact:** ...

#### Recent Tickets
| # | ID | Subject | Status | Priority | Created | Last Update |
|---|-----|---------|--------|----------|---------|-------------|

### Engagement Timeline (HubSpot)
| Date | Type | Summary |
|------|------|---------|

### Customer Health Score
- Sentiment: [Positive/Neutral/Negative based on recent tickets]
- Engagement: [Active/Moderate/Low based on interaction frequency]
- Risk: [Low/Medium/High based on open issues and sentiment]

### Recommended Actions
- [Specific suggestions based on the data]

If the customer is not found in one system, note it and show data from whichever system has results.