meeting-audio-grounding
Skill444 starsChanged 7 months agoMITView on GitHub
Convert a meeting audio file into a transcript bundle, then use meeting-grounding to produce structured meeting grounding outputs.
In this repository15 other files it gives its agents.
- archive-groundingSkill
- audio_structuringSkill
- document-groundingSkill
- grounded-research-litSkill
- grounded-reviewSkill
- grounded-summarySkill
- input-routerSkill
- meeting-groundingSkill
- meeting-video-groundingSkill
- one-reportSkill
- pptx-groundingSkill
- remote-inputSkill
- report-exportSkill
- skill-evolveSkill
- table-groundingSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
20 rules. About 0 are common, 15 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈15
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Use this skill when:
- Distinctive: line 25
Do not use this skill when:
- Distinctive: line 44
All these formats are supported via WhisperX's ffmpeg backend.
- Distinctive: line 71
If the meeting contains multiple independent topics that should be researched separately downstream, the bundle may also contain:
- Distinctive: line 98
always writing the meeting-level:
- Very specific: line 109
Run the existing scripts/run.sh entrypoint for this skill.
- Very specific: line 115
Read transcript/meeting_transcript.txt as the primary grounding evidence.
- Very specific: line 117
Always save the meeting-level structured note to grounded.md inside the same bundle directory.
- Distinctive: line 118
If the transcript clearly contains multiple independent topics, also save:
- Distinctive: line 121
Do not stop after confirming that the transcript bundle exists.
- Very specific: line 127
If topic children are created, each child grounded note must also follow the same meeting-grounding schema.
- Distinctive: line 129
Do not invent a new schema here.
- Distinctive: line 133
Do not implement a new ASR pipeline.
- Distinctive: line 134
Do not implement a new meeting summarizer.
- Distinctive: line 135
Do not directly summarize the raw audio without first running the existing workflow.
- Distinctive: line 138
Treat the transcript as the primary evidence.
- Distinctive: line 139
Keep the workflow simple and stable.
- Distinctive: line 143
If the input audio file does not exist, fail clearly.
- Very specific: line 144
If meeting_transcript.txt is not produced, fail clearly.
- Distinctive: line 145
Do not pretend the task succeeded if only part of the workflow completed.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Meeting Audio Grounding
Convert a meeting audio file into structured meeting grounding outputs by:
- reusing the existing
audio_structuringskill to producemeeting_transcript.txt - reusing the existing
meeting-groundingskill to turn that transcript into meeting grounding outputs
This skill is for meeting audio inputs where the primary information comes from speech. It is intentionally transcript-first.
When to Use
Use this skill when:
- the input is a meeting recording or discussion audio file
- the main information is expected to come from spoken content
- you want to reuse the existing audio transcription and meeting grounding workflow
Do not use this skill when:
- the task is only to produce a transcript without meeting grounding
- the task is to write a polished final report directly from raw audio
- the input is not a meeting/discussion recording
Input
A single meeting audio file.
Typical examples:
.mp3.wav.m4a.webm.aac.ogg
All these formats are supported via WhisperX's ffmpeg backend.
Optional input:
transcription_language: language code such asenorzh
Output Bundle
For each input audio file, create one bundle directory:
data/grounded_notes/<ground_id>/Inside that bundle, the expected outputs are always:
<bundle_dir>/
├─ extracted.md
├─ extracted_meta.json
├─ grounded.md
├─ audio/
│ └─ meeting_audio<original_ext>
└─ transcript/
└─ meeting_transcript.txtIf the meeting contains multiple independent topics that should be researched separately downstream, the bundle may also contain:
<bundle_dir>/
├─ topic_manifest.json
└─ child_outputs/
├─ topic_01/
│ └─ grounded.md
├─ topic_02/
│ └─ grounded.md
└─ ...Important separation of responsibilities
scripts/run.shis responsible for:- preparing the bundle directory
- ensuring the input audio is present under
audio/ - calling the existing
audio_structuringskill - creating the bundle files:
audio/meeting_audio<original_ext>transcript/meeting_transcript.txtextracted.mdextracted_meta.json
- The agent is responsible for:
- reading the transcript bundle
- applying the existing
meeting-groundingskill - always writing the meeting-level:
grounded.md
- and, when appropriate, also writing:
topic_manifest.jsonchild_outputs/topic_xx/grounded.md
grounded.md must be a real grounding note.
It must not remain a placeholder scaffold.
Required Agent Workflow
- Run the existing
scripts/run.shentrypoint for this skill. - Confirm that the bundle exists and that these files are present:
extracted.mdextracted_meta.jsonaudio/transcript/meeting_transcript.txt
- Read
transcript/meeting_transcript.txtas the primary grounding evidence. - Reuse the existing
meeting-groundingskill on that transcript. - Always save the meeting-level structured note to
grounded.mdinside the same bundle directory. - If the transcript clearly contains multiple independent topics, also save:
topic_manifest.jsonchild_outputs/topic_xx/grounded.md
- Do not stop after confirming that the transcript bundle exists.
Output Format
The final grounded.md must follow the existing meeting-grounding schema exactly.
If topic children are created, each child grounded note must also follow the same meeting-grounding schema.
Do not invent a new schema here.
Instructions
- Do not implement a new ASR pipeline.
- Do not implement a new meeting summarizer.
- Do not directly summarize the raw audio without first running the existing workflow.
- Reuse the existing
audio_structuringskill for transcription. - Reuse the existing
meeting-groundingskill for transcript grounding. - Treat the transcript as the primary evidence.
- Keep the workflow simple and stable.
Failure Handling
- If the input audio file does not exist, fail clearly.
- If
meeting_transcript.txtis not produced, fail clearly. - Do not pretend the task succeeded if only part of the workflow completed.
Example Invocation
/meeting-audio-grounding
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.

