- Home
- Skills
- Basedhardware
- Omi
- Omi Plugin Development
omi-plugin-development_skill
7.6k
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill basedhardware/omi --skill omi-plugin-development- SKILL.md5.5 KB
Overview
This skill guides developers through building Omi plugins and apps, covering webhook patterns, chat tools, OAuth flows, and prompt-based integrations. It focuses on practical patterns for FastAPI/Express endpoints, real-time transcription, chat tool registration, and secure OAuth setup. The guidance is focused on outcomes: reliable webhooks, reusable chat tools, and safe token handling.
How this skill works
The skill describes two primary plugin types: prompt-based apps that require no server and integration apps that expose webhook endpoints. It provides concrete webhook handlers for memory creation and live transcript segments, examples for registering chat tools, and OAuth flow snippets for common providers. It also outlines manifest configuration and testing approaches to validate behavior before production.
When to use it
- When creating a new Omi plugin or app
- When implementing webhook handlers for memories or transcripts
- When adding agentic chat tools for LangGraph-style agents
- When integrating third-party OAuth providers (Google, Apple, etc.)
- When building prompt-based experiences without a backend
Best practices
- Handle webhook errors and return clear HTTP statuses
- Design webhooks to be idempotent to avoid duplicate processing
- Verify webhook signatures and authenticate incoming requests
- Rate-limit processing paths and protect expensive operations
- Store OAuth tokens securely and rotate credentials when possible
- Document endpoints and test with webhook inspection tools before production
Example use cases
- Prompt-based assistant embedded in a wearable that customizes responses with no server
- Integration app that receives memory-created webhooks and triggers follow-up actions
- Real-time transcription webhook that listens for wake words and fires automations
- Chat tool providing a domain-specific search or data lookup for agentic conversations
- OAuth-enabled app that links user accounts to external providers and syncs data
FAQ
No. Prompt-based apps can run entirely client-side by defining prompts and personalities; no server endpoint is required.
How should I test webhooks before deploying?
Use webhook inspection services or tools like webhook.site to validate payloads, confirm idempotency, and exercise retry scenarios before going live.