speaker-recognizer

Enroll and manage voice identities via HTTP API with mic and Telegram inputs.

10|2|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/autonomous-ai/autonomous-lamp --skill speaker-recognizer
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: speaker-recognizer
Source: https://github.com/autonomous-ai/autonomous-lamp/tree/main/lamp/resources/openclaw-skills/speaker-recognizer
Command: npx skills add https://github.com/autonomous-ai/autonomous-lamp --skill speaker-recognizer

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables self-enrollment of a speaker's voice for a structured enrollment workflow and voice recognition management via an HTTP API, supporting both mic-based and Telegram-based inputs.

Core Features & Use Cases

  • Self-enrollment only; mic-based enrollment with multiple turns and a tag-based cluster system to build embeddings.
  • Telegram enrollment and voice recognition flows; list and manage voices via API.
  • Flow control: handles unknown speaker turns, enrollment decision matrix, and identity linking to Telegram.

Quick Start

Enroll a speaker by providing a name and a WAV sample to the enroll API.

Frequently Asked Questions about speaker-recognizer

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I enroll a voice identity for speaker recognition using an API?

To enroll a voice identity for speaker recognition, you provide a speaker name and a WAV audio sample to the enrollment HTTP API. The system uses a multi-turn, tag-based cluster system to build robust voice embeddings.

Can I use Telegram for voice enrollment and speaker recognition?

Yes, Telegram supports both voice enrollment and speaker recognition flows. The API-centric workflow links voice identities directly to Telegram inputs, handling unknown speaker turns and identity management.

How does multi-turn voice enrollment build embeddings for unknown speakers?

Multi-turn voice enrollment builds embeddings by processing successive audio inputs through a cluster-tagging system. When an unknown speaker is detected, the enrollment decision matrix triggers additional audio capture turns to construct a robust voice identity.

What is the best way to manage voice identities after enrolling a speaker?

The best way to manage voice identities is through the provided HTTP API. It supports listing enrolled voices, handling identity linking, and processing enrollment decision matrices for ongoing speaker recognition management.

Do I need a microphone to self-enroll a voice identity, or can I use audio files?

You do not strictly need a microphone; the system supports both mic-based and Telegram-based enrollment. You can self-enroll by providing a name and a WAV sample to the API, which is processed through the reference flows.

What limitations exist when self-enrolling voice identities via an HTTP API?

A limitation of this self-enrollment system is that it requires structured, multi-turn audio inputs to build accurate embeddings. Single short audio clips may not satisfy the cluster-tagging requirements for a robust voice identity.