percept-speaker-idIdentifies and tracks speakers in multi-person conversations, mapping speaker labels to names and managing voice command authorization levels.
Install via ClawdBot CLI:
clawdbot install jarvis563/percept-speaker-idGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://github.com/GetPercept/perceptAudited Apr 18, 2026 · audit v1.0
Generated Mar 21, 2026
In a household with multiple residents, this skill identifies who is speaking to a voice assistant like Alexa or Google Home, enabling personalized responses and restricting command execution to authorized users such as parents. It ensures only approved individuals can control smart devices or access sensitive information, enhancing security and customization.
During business meetings or conference calls, this skill tracks speakers to generate accurate transcripts with names attached, improving record-keeping and accountability. It can integrate with collaboration tools like Zoom or Teams to automate note-taking and identify participants for follow-up actions.
In healthcare settings such as hospitals or assisted living facilities, this skill distinguishes between patients, staff, and visitors in conversations, logging interactions for medical records and ensuring only authorized personnel can issue voice commands for equipment. It aids in monitoring patient engagement and maintaining privacy compliance.
In educational environments, this skill identifies students and teachers during discussions, enabling automated attendance and participation grading. It can be used in online learning platforms to attribute contributions in virtual classrooms, fostering engagement and providing analytics for educators.
In call centers, this skill maps anonymous caller labels to customer profiles, analyzing conversations for quality assurance and training purposes. It helps identify frequent callers, track agent performance, and ensure only authorized agents access sensitive systems via voice commands.
Offer this skill as part of a cloud-based platform with tiered pricing based on features like speaker count or integration depth. Revenue comes from monthly or annual subscriptions, targeting businesses that need scalable speaker identification for meetings or customer interactions.
License the technology to smart device manufacturers (e.g., smart speakers, conferencing systems) for embedding into their products. Revenue is generated through one-time licensing fees or royalties per unit sold, leveraging partnerships to reach mass-market consumers.
Provide bespoke integration services for organizations needing tailored speaker identification solutions, such as healthcare or security firms. Revenue comes from project-based fees for development, training, and ongoing support, focusing on high-value niche markets.
💬 Integration Tip
Ensure the percept-listen skill is properly configured to feed transcript data, and use the Omi pendant for accurate primary speaker identification to maximize effectiveness.
Scored Apr 19, 2026
Self-hosted auth for TypeScript/Cloudflare Workers with social auth, 2FA, passkeys, organizations, RBAC, and 15+ plugins. Requires Drizzle ORM or Kysely for D1 (no direct adapter). Self-hosted alternative to Clerk/Auth.js. Use when: self-hosting auth on D1, building OAuth provider, multi-tenant SaaS, or troubleshooting D1 adapter errors, session caching, rate limits, Expo crashes, additionalFields bugs.
Clerk integration. Manage Users, Organizations. Use when the user wants to interact with Clerk data.
Clerk auth with API Keys beta (Dec 2025), Next.js 16 proxy.ts (March 2025 CVE context), API version 2025-11-10 breaking changes, clerkMiddleware() options, webhooks, production considerations (GCP outages), and component reference. Prevents 15 documented errors. Use when: API keys for users/orgs, Next.js 16 middleware filename, troubleshooting JWKS/CSRF/JWT/token-type-mismatch errors, webhook verification, user type inconsistencies, or testing with 424242 OTP.
Use when auditing Go code involving authentication flows, RBAC policies, Kubernetes admission webhooks, JWT/OAuth token validation, or privilege escalation i...
Agent verification via ClawX OAuth system. Use when checking agent verification status, embedding verification widgets, or working with agent identity/trust tiers.
Complete Reva wallet management - passwordless authentication, PayID name claiming, multi-chain crypto transfers to PayIDs or wallet addresses, balance track...