Skip to content
Back to skills

Handoff Notes

ASecurity

Generate agent handoff notes for shift changes or ticket reassignment

  • 18 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
data-aigobashapi

Works with

  • cli
  • api

Security analysis

A100/100

Scanned May 27, 2026

npx -y skills add composio-community/support-skills --skill handoff-notes --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Handoff Notes?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Handoff Notes
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/composio-community-handoff-notes/badge)](https://www.skillsdirectory.com/skills/composio-community-handoff-notes)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: handoff-notes
description: Generate agent handoff notes for shift changes or ticket reassignment
disable-model-invocation: true
---

# 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]
```

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.