agentleFS
terminator1333terminator1333/claude-listen/CLAUDE.md

claude-listen

CLAUDE.md1 starsChanged 7 months agoMITView on GitHub

A Claude Code skill that transcribes + diarizes audio recordings and produces project-aware meeting notes. The repo is designed to be cloned and symlinked as ~/.claude/skills/listen, which makes it invokable as /listen from any Claude Code session. Two pieces only: The extraction step uses Claude itself — no external LLM call. The script only handles audio. For CUDA torch (after uv sync): This repo is meant to be open-sourced. When editing anything that gets committed:

  • Installs packages
  • In this repositoryOne other file it gives its agents.

The file

We split this CLAUDE.md into the rules it gives an agent

5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No hardcoded personal paths (no /home/<user>/, no /mnt/...

    line 35
  2. Distinctive:

    No personal tokens, emails, or usernames.

    line 36
  3. Distinctive:

    No assumptions about SLURM or any particular compute environment beyond "Python + optional GPU".

    line 37
  4. Very specific:

    When in doubt, run grep -rE '(home/[a-z]+|mnt/|@[a-z]+\.(com|org|edu))' .

    line 38
  5. Very specific:

    Keep pyproject.toml minimal.

    line 44

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
CLAUDE.md

CLAUDE.md

This file provides guidance to Claude Code (claude.ai/code) when working with code in this repository.

What this repo is

A Claude Code skill that transcribes + diarizes audio recordings and produces project-aware meeting notes. The repo is designed to be cloned and symlinked as ~/.claude/skills/listen, which makes it invokable as /listen from any Claude Code session.

Architecture

Two pieces only:

  1. scripts/transcribe.py — standalone Python CLI. Takes --audio and --output-dir. Runs faster-whisper for ASR, pyannote.audio for speaker diarization, maps words to speakers by max time overlap, groups into speaker turns, and emits transcript.md, transcript.json, metadata.json. No Claude-specific logic.
  2. SKILL.md — Claude's playbook. Parses the user's /listen invocation, runs the script via Bash, reads the transcript, consults the project's CLAUDE.md for vocabulary, asks the user to identify speakers, then writes meeting-notes.md.

The extraction step uses Claude itself — no external LLM call. The script only handles audio.

Common commands

uv sync                                           # Install deps.
uv run python scripts/transcribe.py --help        # Show CLI options.
uv run python scripts/transcribe.py --audio <f> --output-dir out/  # Run transcription directly.

For CUDA torch (after uv sync):

uv pip install torch torchaudio --index-url https://download.pytorch.org/whl/cu121

Portability constraint

This repo is meant to be open-sourced. When editing anything that gets committed:

  • No hardcoded personal paths (no /home/<user>/, no /mnt/... mounts, no specific cluster references).
  • No personal tokens, emails, or usernames.
  • No assumptions about SLURM or any particular compute environment beyond "Python + optional GPU".
  • When in doubt, run grep -rE '(home/[a-z]+|mnt/|@[a-z]+\.(com|org|edu))' . and clean up anything it finds in tracked files.

Editing tips

  • The SKILL.md front matter description field determines when Claude auto-invokes the skill. If you change the trigger language, make sure it still mentions /listen and the "audio meeting" use case.
  • scripts/transcribe.py has one job. Resist adding Claude-specific logic there; put playbook-style instructions in SKILL.md instead.
  • Keep pyproject.toml minimal. Every added dep is a potential install failure for users on unusual platforms.

Known gotchas

  • pyannote/speaker-diarization-3.1 requires ToS acceptance on Hugging Face. Without HF_TOKEN + ToS acceptance, diarization will 401. The script surfaces a clear error message for this.
  • ffmpeg must be in PATH. faster-whisper invokes it to decode compressed formats.
  • compute_type="int8" is used on CPU for speed. On GPU, float16 is used. Don't change these without benchmarking.
  • Word-to-speaker assignment uses max time overlap, not boundary snapping. In heavy crosstalk you'll see speaker labels flicker mid-sentence. That's the diarization being imperfect, not a bug in the glue code.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.