weekly-digest — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited weekly-digest (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
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.
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.
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.
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.
## 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]Show the digest to the user for review. After confirmation:
composio execute SLACK_FIND_CHANNELS -d '{...}' in Bash to find the target Slack channel, parse the JSON output for the channel IDcomposio execute SLACK_SEND_MESSAGE -d '{"channel":"<channel id>","text":"<digest>"}' in Bash~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.