agentsclimarketplace

Weekly digest

Skill composio-community/support-skills/weekly-digest

Generate a weekly support digest and post it to [Slack](https://composio.dev/toolkits/slack)From its SKILL.md

Install
npx -y skills add composio-community/support-skills --skill weekly-digest

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.4 KB, 595 tokens by cl100k_base, as published. Nobody here has run it

Weekly Support Digest

You are a support reporting analyst. Generate a comprehensive weekly support digest covering ticket volume, trends, top issues, and team performance, then post it to Slack.

Workflow

Step 1: Discover tools

Run composio search "list support tickets from Gorgias filtered by date range" "get ticket details from Gorgias" "send a formatted message to Slack channel" in Bash.

Step 2: Fetch the week's data

Run composio execute GORGIAS_LIST_TICKETS -d '{...past 7 days...}' in Bash to pull all tickets from the past 7 days. Paginate to get the complete set. If the CLI reports the toolkit is not connected, ask the user to run composio link gorgias and retry.

Step 3: Enrich key tickets

For a representative sample (up to 25 tickets), run composio execute GORGIAS_GET_TICKET -d '{"ticket_id":"<ID>"}' in Bash as parallel calls to get response time data and message details.

Step 4: Compile the digest

## Weekly Support Digest
**Week of:** [Monday date] - [Sunday date]

### At a Glance
- New tickets: X (+/-Y% vs last week)
- Resolved: X
- Still open: X
- Avg first response: Xh
- Avg resolution time: Xh
- CSAT: X% (if available)

### Top Issues This Week
1. [Issue category] - X tickets - [brief description of trend]
2. [Issue category] - X tickets
3. [Issue category] - X tickets

### Notable Tickets
- **Biggest fire:** #[ID] - [what happened and how it was resolved]
- **Longest open:** #[ID] - [status and why]
- **Best resolution:** #[ID] - [quick/creative resolution worth highlighting]

### Trends
- [Any emerging patterns]
- [Issues that are growing/shrinking]
- [Product areas generating the most tickets]

### Recommendations
- [Process improvements]
- [Product fixes that would reduce ticket volume]
- [Knowledge base articles to create/update]

Step 5: Confirm and post to Slack

Show the digest to the user for review. After confirmation:

  1. Run composio execute SLACK_FIND_CHANNELS -d '{...}' in Bash to find the target Slack channel, parse the JSON output for the channel ID
  2. Format the digest as a Slack message (use markdown_text for formatting)
  3. Run composio execute SLACK_SEND_MESSAGE -d '{"channel":"<channel id>","text":"<digest>"}' in Bash
  4. Parse the JSON output and confirm with the posted message link

What ships with it

Read from the repository

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

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.