summarize-meeting
Skill8 starsChanged 51 days agoApache-2.0View on GitHub
Summarize a Kleoth meeting in this Claude Code session — you read the transcript and write summary.json (the MeetingSummary shape) and summary.md yourself, with no API key and no API cost. Use when the user wants a Kleoth meeting directory summarized here, by you, rather than through one of Kleoth's AI providers.
- Reads credentials
9 other projects use a version of this.
Adopted by
Most recently taken up by
- yuusakuri/agent-skillstheir own version, first seen Nov 1, 2026
- daviszhen/agent-skillstheir own version, first seen Oct 25, 2026
- Memories-ai-labs/Luci-skillstheir own version, first seen Oct 15, 2026
- stefanomartiradonna/claude-skillstheir own version, first seen Aug 14, 2026
- Adhamxon/claude-code-skillstheir own version, first seen Jul 30, 2026
- maeng777/claude-skillstheir own version, first seen Jun 19, 2026
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- Memories-ai-labs/Luci-skills★ 8same name
- Adhamxon/claude-code-skills★ 2same name
- skytiger6724/qwen-skills★ 2same name
- yuusakuri/agent-skills★ 2same name
- daviszhen/agent-skills★ 1same name
- miovrag/claude-skills★ 1same name
- maeng777/claude-skills★ 0same name
- olafgeibig/skills★ 0same name
- stefanomartiradonna/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 repository2 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- transcribe-meetingSkill
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 3 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 20
If the meeting has no transcript yet (neither transcript.md nor transcript.json: the app shows it as *Untranscribed*.
- Very specific: line 27
Read the transcript: Read <dir>/transcript.md (speaker-tagged Name: text lines).
- Distinctive: line 33
Write every value (title, tldr, overview, each task, each highlight) in the same language as the transcript.
- Distinctive: line 35
Keep speaker and owner names exactly as they appear in the transcript.
- Very specific: line 63
If the binary isn't built yet, run swift build first.
- Distinctive: line 70
No API key is needed; this uses your Claude Code session.
- Very specific: line 73
Never read or echo .env or any API key.
“Common” is measured: kept by at least 6 in 10 of the 9 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
Summarize a Kleoth meeting in this session
Kleoth normally summarizes through an AI provider: the app does it after each transcription, and
the CLI does it with kleoth summarize <dir> --provider openrouter|local|claude-code|codex. This
skill is the in-session alternative: you — Claude Code — read the transcript and write the
summary directly. The output is interchangeable with the provider path: the same summary.json
shape, and a summary.md rendered by the kleoth CLI.
Input
A meeting directory written by the Kleoth app or by kleoth transcribe
(meeting-yyyy-MM-dd-HHmmss/, containing transcript.md and meta.json). The directory path is
the argument to this skill. If none was provided, ask the user which meeting to summarize.
If the meeting has no transcript yet (neither transcript.md nor transcript.json: the app shows
it as Untranscribed; it may already have a meta.json, which the app writes when the recording
stops), stop and say so: transcribe it first, in the app or with the
transcribe-meeting skill.
Steps
- Read the transcript. Read
<dir>/transcript.md(speaker-taggedName: textlines). If it is missing but<dir>/transcript.jsonexists, reconstruct the dialogue from itswords[]/transcripts[]andspeaker_id. Read<dir>/meta.jsonfor the title, date and participants, and<dir>/speakers.json(if present) for the display names. - Summarize, following the same rules as Kleoth's
Summarizer:- Write every value (title, tldr, overview, each task, each highlight) in the same language as the transcript. Don't translate it into English or anything else.
- Keep speaker and owner names exactly as they appear in the transcript.
- Be precise and factual. Do not invent information. If something is ambiguous, say so.
- Include an action item only if a concrete task was stated or clearly implied. If the owner is
unstated use
"unassigned"; if the due date is unstated usenull.
- Write
<dir>/summary.jsonwith the Write tool: valid JSON, snake_case keys exactly as below (whatMeetingStoreandkleoth renderread), every key present. No prose, no markdown fences:{ "title": "a concise, specific 4-8 word meeting title", "tldr": "2-4 sentences capturing the essence of the meeting", "overview": "a detailed, faithful account of the whole meeting as flowing prose in several paragraphs separated by blank lines (no bullets, no headings): what was discussed and in what order, the context and reasoning, concrete specifics (names, numbers, dates, agreements and who made them), and how things were left", "action_items": [{ "owner": "name or \"unassigned\"", "task": "...", "due": "date or null" }], "per_speaker_highlights": [{ "speaker": "name", "highlights": ["their most important statements, positions and commitments"] }] }action_itemsmay be an empty array; the other values may not be blank. - Record who wrote it. In
<dir>/meta.json, set"summary_provider": "claude-code"and remove"model", so the meeting doesn't credit an earlier model with this summary. Leave every other field as it is. - Render
summary.mdwith the CLI (no API call, so the formatting matches the provider path exactly):
If the binary isn't built yet, runswift run kleoth render <dir> # add --no-transcript to omit the transcript appendixswift buildfirst. - Report: tell the user the summary was written in this Claude Code session at no API cost,
and print the path to
summary.md.
Notes
- No API key is needed; this uses your Claude Code session.
kleoth summarize <dir> --provider claude-codegets a summary from Claude Code without this session: it runsclaude -pin isolation and writes the same files.- Never read or echo
.envor any API key.
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.

