omni-executor — ai-agents omni-executor, community, ai-agents, ide skills, discord, event-driven, messaging, omnichannel, typescript, whatsapp

v1.0

About this Skill

Perfect for AI Agents needing universal messaging capabilities across various platforms using event-driven architecture. Omni v2 message execution specialist — use for sending messages (text, TTS, media, reactions, stickers, polls), searching messages, batch operations, and testing automations via the omni CLI.

# Core Topics

automagik-dev automagik-dev
[6]
[0]
Updated: 2/26/2026

Killer-Skills Review

Decision support comes first. Repository text comes second.

Reference-Only Page Review Score: 7/11

This page remains useful for operators, but Killer-Skills treats it as reference material instead of a primary organic landing page.

Original recommendation layer Concrete use-case guidance Explicit limitations and caution Locale and body language aligned
Review Score
7/11
Quality Score
47
Canonical Locale
en
Detected Body Locale
en

Perfect for AI Agents needing universal messaging capabilities across various platforms using event-driven architecture. Omni v2 message execution specialist — use for sending messages (text, TTS, media, reactions, stickers, polls), searching messages, batch operations, and testing automations via the omni CLI.

Core Value

Empowers agents to communicate seamlessly with users on any messaging platform, leveraging omni-send and event-driven architecture for efficient message handling, utilizing JSON processing with jq.

Ideal Agent Persona

Perfect for AI Agents needing universal messaging capabilities across various platforms using event-driven architecture.

Capabilities Granted for omni-executor

Sending text messages across platforms
Implementing event-driven messaging workflows
Integrating with omni-instances and omni-config for unified messaging

! Prerequisites & Limits

  • Requires omni CLI installed and configured
  • Deprecation notice: Superseded by atomic skills in plugins/omni/skills/

Why this page is reference-only

  • - The underlying skill quality score is below the review floor.

Source Boundary

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Curated Collection Review

Reviewed In Curated Collections

This section shows how Killer-Skills has already collected, reviewed, and maintained this skill inside first-party curated paths. For operators and crawlers alike, this is a stronger signal than treating the upstream README as the primary story.

After The Review

Decide The Next Action Before You Keep Reading Repository Material

Killer-Skills should not stop at opening repository instructions. It should help you decide whether to install this skill, when to cross-check against trusted collections, and when to move into workflow rollout.

Labs Demo

Browser Sandbox Environment

⚡️ Ready to unleash?

Experience this Agent in a zero-setup browser environment powered by WebContainers. No installation required.

Boot Container Sandbox

FAQ & Installation Steps

These questions and steps mirror the structured data on this page for better search understanding.

? Frequently Asked Questions

What is omni-executor?

Perfect for AI Agents needing universal messaging capabilities across various platforms using event-driven architecture. Omni v2 message execution specialist — use for sending messages (text, TTS, media, reactions, stickers, polls), searching messages, batch operations, and testing automations via the omni CLI.

How do I install omni-executor?

Run the command: npx killer-skills add automagik-dev/omni/omni-executor. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for omni-executor?

Key use cases include: Sending text messages across platforms, Implementing event-driven messaging workflows, Integrating with omni-instances and omni-config for unified messaging.

Which IDEs are compatible with omni-executor?

This skill is compatible with Cursor, Windsurf, VS Code, Trae, Claude Code, OpenClaw, Aider, Codex, OpenCode, Goose, Cline, Roo Code, Kiro, Augment Code, Continue, GitHub Copilot, Sourcegraph Cody, and Amazon Q Developer. Use the Killer-Skills CLI for universal one-command installation.

Are there any limitations for omni-executor?

Requires omni CLI installed and configured. Deprecation notice: Superseded by atomic skills in plugins/omni/skills/.

How To Install

  1. 1. Open your terminal

    Open the terminal or command line in your project directory.

  2. 2. Run the install command

    Run: npx killer-skills add automagik-dev/omni/omni-executor. The CLI will automatically detect your IDE or AI agent and configure the skill.

  3. 3. Start using the skill

    The skill is now active. Your AI agent can use omni-executor immediately in the current project.

! Reference-Only Mode

This page remains useful for installation and reference, but Killer-Skills no longer treats it as a primary indexable landing page. Read the review above before relying on the upstream repository instructions.

Upstream Repository Material

The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.

Upstream Source

omni-executor

Install omni-executor, an AI agent skill for AI agent workflows and automation. Review the use cases, limitations, and setup path before rollout.

SKILL.md
Readonly
Upstream Repository Material
The section below is imported from the upstream repository and should be treated as secondary evidence. Use the Killer-Skills review above as the primary layer for fit, risk, and installation decisions.
Supporting Evidence

⚠️ DEPRECATED: Superseded by atomic skills in plugins/omni/skills/. omni-orchestrator → use omni-instances/SKILL.md + omni-config/SKILL.md omni-executor → use omni-send/SKILL.md omni-analytics → use omni-events/SKILL.md

Omni Executor

Prerequisites

  • omni CLI installed and in PATH (omni auth login --api-key sk_xxx --api-url <url>)
  • jq available for JSON processing

Sending Messages

Use omni send with the appropriate flags for each message type:

bash
1# Text 2omni send --to <recipient> --text "Hello!" --instance <id> 3 4# TTS voice note 5omni send --to <recipient> --tts "Voice message" --instance <id> 6 7# Media (image, audio, video, document) 8omni send --to <recipient> --media ./file.jpg --caption "Caption" --instance <id> 9 10# Reaction 11omni send --to <recipient> --reaction "👍" --message <msg-id> --instance <id> 12 13# Sticker 14omni send --to <recipient> --sticker https://example.com/sticker.webp --instance <id> 15 16# Poll (Discord) 17omni send --to <channel-id> --poll "Question?" --options "A,B,C" --instance <id> 18 19# Embed (Discord) 20omni send --to <channel-id> --embed --title "Title" --description "Body" --instance <id>

Instance Resolution

The CLI matches instance IDs intelligently:

  • Full UUID: 00000000-1111-2222-3333-444444444444
  • UUID prefix: c3a4f
  • Exact name: cezar-personal
  • Substring: personal

Searching Messages

bash
1omni messages search "keyword" --since 7d --limit 50 2omni messages search "" --type audio --since 30d --json 3omni messages search "urgent" --chat <chat-id> --since 24h

Filters

FilterDescription
--contentFull-text search
--typetext, audio, image, video
--chatSpecific chat ID
--sinceTime range (7d, 24h, 30min)
--limitMax results

JSON Output and Piping

Every command supports --json for structured output:

bash
1omni send --to <phone> --text "Hi" --json | jq -r '.data.messageId' 2omni instances list --json | jq '.[] | select(.status=="connected")' 3omni chats list --instance <id> --json | jq '.[] | select(.unreadCount > 0)'

Testing Automations

bash
1omni automations test <id> --dry-run 2omni automations logs <id>

Rate Limiting

When sending in loops, add a delay between messages:

bash
1for recipient in "${recipients[@]}"; do 2 omni send --to "$recipient" --text "Hello" --instance <id> --json 3 sleep 1 4done

Error Handling

Check exit codes and capture stderr:

bash
1if ! output=$(omni send --to <phone> --text "Hi" --instance <id> --json 2>&1); then 2 echo "Error: $output" >&2 3 exit 1 4fi

Related Skills

Looking for an alternative to omni-executor or another community skill for your workflow? Explore these related open-source skills.

View All

openclaw-release-maintainer

Logo of openclaw
openclaw

Your own personal AI assistant. Any OS. Any Platform. The lobster way. 🦞

333.8k
0
AI

widget-generator

Logo of f
f

Generate customizable widget plugins for the prompts.chat feed system

149.6k
0
AI

flags

Logo of vercel
vercel

The React Framework

138.4k
0
Browser

pr-review

Logo of pytorch
pytorch

Tensors and Dynamic neural networks in Python with strong GPU acceleration

98.6k
0
Developer