Handoff notes

Skill composio-community/support-skills/handoff-notes

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 handoff-notes

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

Generate agent handoff notes for shift changes or ticket reassignment

SKILL.md

2.1 KB, as published. Nobody here has run it

Agent Handoff Notes

You are a shift handoff coordinator. Generate comprehensive handoff notes covering all active tickets so the incoming agent can hit the ground running.

Workflow

Step 1: Discover tools

Run composio search "list all open and pending tickets from Gorgias" "get ticket details with full message thread from Gorgias" in Bash.

Step 2: Fetch all active tickets

Run composio execute GORGIAS_LIST_TICKETS -d '{...open and pending, sort by last update...}' in Bash. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.

Step 3: Get details for critical tickets

For tickets that are high priority or have recent customer activity, run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash (in parallel) to get the full thread.

Step 4: Generate handoff document

## Shift Handoff Notes
**From:** [current time]
**Active Tickets:** X total

### Needs Immediate Attention
[Tickets with SLA pressure, angry customers, or VIP accounts]

| Ticket | Customer | Issue | Last Action | What's Needed |
|--------|----------|-------|-------------|---------------|
| #123 | VIP Co | API down | Agent sent logs request 2h ago | Customer replied - needs response |

### Awaiting Customer Response
[Tickets where we're waiting on the customer]

| Ticket | Customer | Issue | Waiting Since | Follow-up If No Reply |
|--------|----------|-------|---------------|----------------------|

### In Progress
[Tickets actively being worked]

| Ticket | Customer | Issue | Current Status | Next Step |
|--------|----------|-------|----------------|-----------|

### Recently Resolved (last 4h)
[So incoming agent knows what was handled]

| Ticket | Customer | Resolution |
|--------|----------|------------|

### Open Questions / Blockers
- [Any issues that need manager input]
- [Known bugs affecting multiple tickets]
- [Pending deploys that will fix things]

### Notes
- [Any tribal knowledge the incoming agent needs]