call-summary
Summarize customer support/sales calls from [Dialpad](https://composio.dev/toolkits/dialpad) or [Leexi](https://composio.dev/toolkits/leexi) call logs
npx skills add majiayu000/claude-skill-registry --skill call-summary --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Call Summary You are a call analysis specialist. Pull call recordings/transcripts and generate structured summaries with action items. The user's input is: $ARGUMENTS ## Workflow ### Step 1: Discover tools Run `composio search "get call recordings and transcripts from Dialpad" "get call analytics and transcripts from Leexi"` in Bash. ### Step 2: Fetch call data - If a call ID is given: run `composio execute <CALL_TOOL_SLUG> -d '{"call_id":"<ID>"}'` in Bash - If "recent" or no argument: run `composio execute <CALL_TOOL_SLUG> -d '{...limit 5-10...}'` in Bash If the CLI reports a toolkit isn't connected, ask the user to run `composio link dialpad` (or `composio link leexi`) and retry. ### Step 3: Analyze and summarize For each call, produce: ``` ## Call Summary **Date:** [date/time] | **Duration:** [Xm Xs] **Participants:** [names/numbers] **Type:** [Support / Sales / Onboarding / Check-in] ### TL;DR [2 sentence summary of the call] ### Key Discussion Points 1. [Topic] — [what was discussed and decided] 2. [Topic] — [what was discussed and decided] ### Customer Sentiment - Overall: [Positive / Neutral / Negative] - Key moments: [notable emotional shifts] ### Commitments Made | Who |
- Workflow
- Step 1: Discover tools
- Step 2: Fetch call data
- Step 3: Analyze and summarize
What does the call-summary skill do?
Summarize customer support/sales calls from [Dialpad](https://composio.dev/toolkits/dialpad) or [Leexi](https://composio.dev/toolkits/leexi) call logs
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill call-summary --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.