omni-docs — community omni-docs, omni-embed-demo, community, ide skills, Claude Code, Cursor, Windsurf

v1.0.0

About this Skill

Perfect for AI Agents needing comprehensive Omni platform documentation and embedding SDK expertise. A secure, TypeScript-based demo app showcasing Omni’s embedding SDK. Features server-side signed URL generation, robust error handling, and best practices for environment variable management. Includes

Hawkfry-Group Hawkfry-Group
[3]
[0]
Updated: 4/9/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
23
Canonical Locale
en
Detected Body Locale
en

Perfect for AI Agents needing comprehensive Omni platform documentation and embedding SDK expertise. A secure, TypeScript-based demo app showcasing Omni’s embedding SDK. Features server-side signed URL generation, robust error handling, and best practices for environment variable management. Includes

Core Value

Empowers agents to provide accurate and up-to-date information on Omni's features, including server-side signed URL generation, robust error handling, and environment variable management, using official documentation and TypeScript-based demo apps.

Ideal Agent Persona

Perfect for AI Agents needing comprehensive Omni platform documentation and embedding SDK expertise.

Capabilities Granted for omni-docs

Resolving general Omni documentation questions
Routing embed-specific requests to the embed skill
Providing clear setup and deployment instructions for the demo app

! Prerequisites & Limits

  • Requires access to official Omni documentation
  • Limited to TypeScript-based demo app
  • Explicitly routes embed-specific requests to the embed skill

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.

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-docs?

Perfect for AI Agents needing comprehensive Omni platform documentation and embedding SDK expertise. A secure, TypeScript-based demo app showcasing Omni’s embedding SDK. Features server-side signed URL generation, robust error handling, and best practices for environment variable management. Includes

How do I install omni-docs?

Run the command: npx killer-skills add Hawkfry-Group/omni-embed-demo/omni-docs. It works with Cursor, Windsurf, VS Code, Claude Code, and 19+ other IDEs.

What are the use cases for omni-docs?

Key use cases include: Resolving general Omni documentation questions, Routing embed-specific requests to the embed skill, Providing clear setup and deployment instructions for the demo app.

Which IDEs are compatible with omni-docs?

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-docs?

Requires access to official Omni documentation. Limited to TypeScript-based demo app. Explicitly routes embed-specific requests to the embed skill.

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 Hawkfry-Group/omni-embed-demo/omni-docs. 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-docs 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-docs

Install omni-docs, an AI agent skill for AI agent workflows and automation. Works with Claude Code, Cursor, and Windsurf with one-command setup.

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

Omni Docs

Use this skill for general Omni documentation questions. It covers the broader platform and explicitly routes embed-specific requests to the embed skill.

Quick Start

  • Browse https://docs.omni.co for official Omni documentation.
  • Read references/routing.md to pick the right section quickly.
  • If the request is primarily about embedding, switch to $omni-embed-docs.
  • If the request is about this demo repository, cross-check local code after reading the docs.

Workflow

  1. Decide whether the request is about modeling, API, AI and MCP, administration, connections, or embedding.
  2. For embedding, use $omni-embed-docs instead of handling it as a generic docs question.
  3. Open the most relevant official page from references/routing.md.
  4. Follow adjacent pages only if the first page is insufficient.
  5. Answer concisely with source links.

Rules

  • Prefer official Omni docs over memory for product behavior.
  • Prefer embed docs over REST API docs for embed questions.
  • Keep repo-specific explanations grounded in local code, and label them as inferences when they are not explicitly documented.
  • Cite the official docs you used.

Reference Map

  • Read references/routing.md for topic-to-URL mappings across the Omni docs.

Related Skills

Looking for an alternative to omni-docs 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