call-summary
Skill3 starsChanged 57 days agoMITView on GitHub
Summarize a customer call transcript into the standard format so cross-customer synthesis works. Use whenever logging a customer call.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Big-LAORE/Biblioth-que-de-skillstheir own version, first seen Nov 1, 2026
- anthropics/knowledge-work-pluginstheir own version, first seen Oct 13, 2026
- akachandan1/proofstacktheir own version, first seen Oct 11, 2026
- composio-community/support-skillstheir own version, first seen Apr 10, 2026
- KevinReactiv8/claude-skillstheir own version, first seen Mar 30, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- anthropics/knowledge-work-plugins★ 36ksame name
- composio-community/support-skills★ 18same name
- Big-LAORE/Biblioth-que-de-skills★ 1same name
- akachandan1/proofstack★ 0same name
- KevinReactiv8/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository14 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- competitive/CLAUDE.mdCLAUDE.md
- customers/CLAUDE.mdCLAUDE.md
- delivery/CLAUDE.mdCLAUDE.md
- design/CLAUDE.mdCLAUDE.md
- engineering/CLAUDE.mdCLAUDE.md
- product/CLAUDE.mdCLAUDE.md
- quality/CLAUDE.mdCLAUDE.md
- team/CLAUDE.mdCLAUDE.md
- dsu-digestSkill
- email-voiceSkill
- linkedin-voiceSkill
- os-builderSkill
- person-noteSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 2 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Always produce this exact structure so summaries are consistent across all accounts:
- Distinctive: line 21
Keep it tight. The summary should let me skip the transcript 90% of the time.
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Customer Call Summary
Always produce this exact structure so summaries are consistent across all accounts:
<Account> - <Date>
- Attendees: (theirs / ours)
- Segment & stage:
- Context: 1-2 lines on why we met
- What they want / pain points:
- Feature requests: (link to feature-index slug if one exists)
- Commitments: who owes what, by when (ours and theirs)
- Risks / sentiment:
- Follow-ups: action - owner - due date
- Insight candidates: anything worth adding to
customers/hypotheses.md
Keep it tight. The summary should let me skip the transcript 90% of the time.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.