agentleFS
autonomous-aiautonomous-ai/Physical-AI-Operating-System/skills/speaker-recognizer/SKILL.md

speaker-recognizer

Skill552 starsChanged 8 months agoApache-2.0View on GitHub

Self-enroll voices after a clear self-introduction or explicit enrollment request; continue that enrollment, or list, forget, link, and identify voices when requested. Unknown Speaker labels, saved audio, and same-tag history alone do not activate this skill. Handle ordinary requests without identity lookup or a name question.

  • Sends data out

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    When in doubt → see reference/enroll-flows.md.

    line 33
  2. Very specific:

    Telegram audio must be 16 kHz mono WAV: before enroll — convert with ffmpeg -ar 16000 -ac 1.

    line 52
  3. Very specific:

    /speaker/identity (not re-enroll): when only linking Telegram info to an existing mic profile.

    line 53
  4. Distinctive:

    Confirm every enroll: AFTER the API returns ok.

    line 55

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

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

Speaker Recognizer

Each mic transcript is prefixed Speaker - Name: when recognized, or Unknown Speaker: [voice:voice_N] ... (audio save[d] at <path>...) otherwise. The audio path is the WAV of whoever spoke this turn — use it (with paths from prior same-tag turns when needed) to enroll on POST /speaker/enroll.

Self-enrollment only — never enroll one person's voice under another person's name.

Entry gate

Unknown identity is metadata, not an enrollment request. Without a clear self-introduction, an explicit voice enrollment/management request, or a reply continuing a user-initiated enrollment, handle the actual request directly: no speaker API calls, no enrollment reference reads, no name question, and no replacement acknowledgment. Meaningless fragments follow the device's normal silence rules. Same-tag history alone does not start or resume enrollment; a new unrelated request takes priority.

A name counts only when the speaker identifies themselves, not when addressing the agent ("Mike, open Chrome"), mentioning another person, or appearing in metadata. Preserve any substantive request accompanying a self-introduction; enrollment must not replace it.

Decision matrix — after the entry gate

Signals in current turnPrior same-tag turns?Action
Unknown Speaker: + path + name + ≥25 words—Enroll now with current path only.
Unknown Speaker: + path + name + <25 words≥1 prior path same [voice:N]Enroll now with all same-tag paths (oldest→newest).
Unknown Speaker: + path + name + <25 wordsnoneAsk one follow-up: "say your name + ~25–30 words".
Explicit enrollment request + path + NO nameanyAsk for the speaker's own name; request more audio only if needed.
Reply continuing enrollment, still no name or insufficient audiosame enrollmentExplain what is missing once; do not loop or enroll under a guessed name.
Speaker - <Name>:—Already identified — skill not needed.
"who do you know?" / "list voices"—GET /speaker/list.
"forget my voice" / "remove Alex"—POST /speaker/remove.
Telegram voice note + intro—Convert to WAV + enroll with Telegram fields.
Telegram voice note + "who is this?"—POST /speaker/recognize.

When in doubt → see reference/enroll-flows.md. All curl + error handling → reference/api.md.

Quick enroll (mic)

curl -s -X POST http://127.0.0.1:5001/speaker/enroll \
  -H "Content-Type: application/json" \
  -d '{"name": "darren", "wav_paths": ["<path1>", "<path2>"]}'

Confirm AFTER the API returns ok: "Nice to meet you, <Name>!".

Hard rules

  • Self-enrollment only — "this is my friend Bob" → refuse politely; Bob must speak himself.
  • Lowercase normalized name — same name as face-enroll for the same person (/root/local/users/<name>/ is shared).
  • Minimum voice for one-turn enroll: ~25 words (aim 25–30) OR combine with prior same-tag turns to ~5–10s total.
  • Cluster claim is automatic — pass any path inside voice_<N>/ and the server pulls every sibling WAV. One path is enough.
  • Two-turn path mapping — <pathA> = turn BEFORE follow-up, <pathB> = turn AFTER. Never swap.
  • Telegram audio must be 16 kHz mono WAV before enroll — convert with ffmpeg -ar 16000 -ac 1; same folder as source. Skip if already .wav.
  • /speaker/identity (not re-enroll) when only linking Telegram info to an existing mic profile.
  • No unsolicited identity questions — ask only within user-initiated enrollment; combine missing-name and missing-audio guidance in one question. Do not repeatedly interrupt other requests to finish enrollment.
  • Confirm every enroll AFTER the API returns ok.
  • Don't narrate technical details — no "base64", "ffmpeg", "POST /speaker/enroll".
  • Never write files directly — always use the HTTP API.

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.