Edgeone Makers Migration
TencentEdgeOne/edgeone-makers-tools
Migrate existing AI agent projects (LangChain, LangGraph, OpenAI Agents SDK, Claude Agent SDK, CrewAI) to EdgeOne Makers platform conventions.
Reference for the Omnigent agent platform: agent directory layout, config.yaml fields, executor types, harness options, AGENTS.md and skill structure.
$ npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install omnigent-ai/omnigent omnigent-knowledge --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/omnigent-ai/omnigent.git skills-src && mkdir -p .claude/skills && cp -r skills-src/omnigent/onboarding/agent/skills/omnigent-knowledge .claude/skills/omnigent-knowledge && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "omnigent-knowledge" agent skill from https://github.com/omnigent-ai/omnigent/tree/main/omnigent/onboarding/agent/skills/omnigent-knowledge into .claude/skills/omnigent-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnigent-knowledge", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/omnigent-ai/omnigent/tree/main/omnigent/onboarding/agent/skills/omnigent-knowledgeType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install omnigent-ai/omnigent omnigent-knowledge --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/omnigent-ai/omnigent.git skills-src && mkdir -p .agents/skills && cp -r skills-src/omnigent/onboarding/agent/skills/omnigent-knowledge .agents/skills/omnigent-knowledge && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "omnigent-knowledge" agent skill from https://github.com/omnigent-ai/omnigent/tree/main/omnigent/onboarding/agent/skills/omnigent-knowledge into .agents/skills/omnigent-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnigent-knowledge", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install omnigent-ai/omnigent omnigent-knowledge --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/omnigent-ai/omnigent.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/omnigent/onboarding/agent/skills/omnigent-knowledge .cursor/skills/omnigent-knowledge && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "omnigent-knowledge" agent skill from https://github.com/omnigent-ai/omnigent/tree/main/omnigent/onboarding/agent/skills/omnigent-knowledge into .cursor/skills/omnigent-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnigent-knowledge", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/omnigent-ai/omnigent.git --path omnigent/onboarding/agent/skills/omnigent-knowledge--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install omnigent-ai/omnigent omnigent-knowledge --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/omnigent-ai/omnigent.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/omnigent/onboarding/agent/skills/omnigent-knowledge .gemini/skills/omnigent-knowledge && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "omnigent-knowledge" agent skill from https://github.com/omnigent-ai/omnigent/tree/main/omnigent/onboarding/agent/skills/omnigent-knowledge into .gemini/skills/omnigent-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnigent-knowledge", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install omnigent-ai/omnigent omnigent-knowledgeInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/omnigent-ai/omnigent.git skills-src && mkdir -p .github/skills && cp -r skills-src/omnigent/onboarding/agent/skills/omnigent-knowledge .github/skills/omnigent-knowledge && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "omnigent-knowledge" agent skill from https://github.com/omnigent-ai/omnigent/tree/main/omnigent/onboarding/agent/skills/omnigent-knowledge into .github/skills/omnigent-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnigent-knowledge", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install omnigent-ai/omnigent omnigent-knowledge --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/omnigent-ai/omnigent.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/omnigent/onboarding/agent/skills/omnigent-knowledge .opencode/skills/omnigent-knowledge && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "omnigent-knowledge" agent skill from https://github.com/omnigent-ai/omnigent/tree/main/omnigent/onboarding/agent/skills/omnigent-knowledge into .opencode/skills/omnigent-knowledge/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "omnigent-knowledge", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
omnigent-knowledgeReference for the Omnigent agent platform: agent directory layout, config.yaml fields, executor types, harness options, AGENTS.md and skill structure.
Omnigent is described as a server that hosts and runs agents through an OpenResponses-compatible API. Users create agent directories, also called agent images, holding configuration, instructions, skills and tools, and the server loads them and serves them over HTTP. Only `config.yaml` is required, and within it only `spec_version`, which must be 1, is mandatory.
The reference lists three valid executor types. `claude_sdk` and `agents_sdk` run in process and suit simple agents, while `omnigent` starts a subprocess harness named by `config.harness` and suits coding harnesses, shell and file tools, and sub-agents. There is no `llm` executor. Harness values include `claude-native`, `claude-sdk`, `codex-native`, `openai-agents`, `open-responses` and `pi`. For AGENTS.md it advises opening with an identity statement, listing capabilities and constraints, naming skills and sub-agents, and staying focused; the excerpt ends before the skills section.
Read from SKILL.md and the folder at commit 26c8338. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
No scripts in the folder and no shell commands in SKILL.md (its code samples are yaml, markdown, python and bash).
From the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
modelcontextprotocol.iogithub.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
ANTHROPIC_API_KEYGITHUB_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Omnigent Knowledge Base loads about 3.4k tokens when it runs. Until then it costs about 42 tokens; SKILL.md has 994 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from omnigent-ai/omnigent at commit 26c8338, republished under its Apache-2.0 licence (© omnigent-ai). 994 words, ~3,400 tokens.
.claude/skills/omnigent-knowledge/SKILL.md (or your agent's skills folder).Agent plane is a server that hosts, manages, and executes agents via an OpenResponses-compatible API. Users create agent directories (also called agent images) that contain configuration, instructions, skills, and tools. The server loads these directories and serves them via HTTP.
my-agent/
├── config.yaml # REQUIRED — agent spec
├── AGENTS.md # Recommended — instructions/personality
├── skills/ # Optional — load-on-demand skills
│ └── <dir>/ # Free-form; skill name comes from SKILL.md
│ └── SKILL.md
├── tools/ # Optional — packaged tools
│ ├── python/ # Local Python tools (auto-discovered *.py)
│ ├── typescript/ # Local TypeScript tools (auto-discovered *.ts)
│ └── mcp/ # MCP server declarations (*.yaml)
└── agents/ # Optional — sub-agent directories (recursive)
└── <dir>/ # Free-form; sub-agent name comes from config.yaml
├── config.yaml
└── ...The only required file. All fields except spec_version are optional.
spec_version: 1 # REQUIRED, must be 1
name: my-agent # Display name
description: Does X and Y. # One-line summary
# Instructions — path to a file or inline text.
# Default: looks for AGENTS.md in the agent directory.
instructions: AGENTS.md
executor:
# REQUIRED area. type must be one of: claude_sdk | agents_sdk | omnigent.
# There is NO `llm` executor type.
type: claude_sdk # Anthropic Claude SDK, in-process (simplest)
# type: agents_sdk — OpenAI Agents SDK, in-process
# type: omnigent — subprocess harness; requires config.harness below
# Only for type: omnigent — pick the harness that runs the loop.
# One of: claude-native | claude-sdk | codex-native | codex |
# openai-agents | open-responses | pi
# config:
# harness: claude-native
# permission_mode: bypassPermissions # claude-native headless
# yolo: true # codex-native headless
# Model is OPTIONAL — omit to use the configured provider's default.
# Pin one directly on the executor when needed:
# model: anthropic/claude-sonnet-4-20250514 # LiteLLM provider/model
# model: databricks-claude-opus-4-7 # or a serving-endpoint name
# connection: # provider credentials
# api_key: ${ANTHROPIC_API_KEY}
# auth: # or Databricks profile auth
# type: databricks
# profile: oss
timeout: 3600 # Task deadline in seconds (default: 3600)
max_iterations: 1000 # Max LLM calls per task (default: 1000)
# os_env — grant filesystem/shell access (harness agents). Exposes
# sys_os_read / sys_os_write / sys_os_edit / sys_os_shell.
os_env:
type: caller_process
cwd: .
sandbox:
type: none # or linux_bwrap / darwin_seatbelt to sandbox
# guardrails — runtime policy gates (optional).
guardrails:
ask_timeout: 86400 # seconds to wait on an approval prompt
policies:
blast_radius:
type: function
function:
path: omnigent.inner.nessie.policies.blast_radius
interaction:
conversational: true # Maintain turn history (default: true)
modalities:
input: [text, image, file] # default: [text]
output: [text] # default: [text]
tools:
# Sub-agents this agent can spawn (declared names of agents/ sub-agents)
agents:
- researcher
- summarizer
# Built-in tools — string name or dict with config
builtins:
- web_search # auto-detects backend based on model provider
- terminal_run # persistent bash shell scoped to the conversation
- upload_file
- search_conversations
timeout: 60 # Default tool timeout in seconds
params: # Arbitrary key-value (readable by skills/tools)
max_results: 10| Type | When to use | How it works |
|---|---|---|
claude_sdk | New simple agents; existing Claude SDK code | In-process Anthropic Claude SDK; it manages its own loop |
agents_sdk | New simple agents; existing OpenAI Agents SDK code | In-process OpenAI Agents SDK runner |
omnigent | Coding/CLI harnesses, shell + file tools, sub-agents | Spawns a subprocess harness selected by config.harness |
There is no llm executor type — the only valid values are
claude_sdk, agents_sdk, and omnigent. For most new simple agents,
use claude_sdk (or agents_sdk) — in-process, no extra config. Use
omnigent when the agent needs a specific harness, shell/file access, or
sub-agents; it requires a config.harness:
config.harness | What it is |
|---|---|
claude-native (alias claude) | Claude Code — full coding tools, native permissions |
claude-sdk | Claude Agent SDK loop |
codex-native / codex | Codex CLI / harness |
openai-agents | OpenAI Agents harness (any gateway model) |
open-responses | OpenResponses-compatible harness |
pi | Headless multi-model worker (bridged sys_os_* tools) |
Free-form markdown. This becomes the agent-authored portion of the system prompt; Omnigent may append framework-owned lifecycle or metadata instructions at runtime. Best practices:
Each skill lives in skills/<dir>/SKILL.md (the directory name is free-form
and need not match the skill's name):
---
name: deep-research
description: Investigate a topic in depth using web search and source synthesis.
---
When researching a topic:
1. Search broadly first using web search...
2. Cross-reference multiple sources...Rules:
name and description (both required)name must be lowercase and use [a-z0-9-]+; it need not match the
directory name (the directory is where the skill's files load from)Call list_builtin_tools to get the current set of available
built-in tools and their descriptions. Do not rely on a hardcoded
list — new tools may be added at any time.
Tool recommendation guide:
web_search + web_fetchterminal_run + upload_fileterminal_run + upload_file + download_fileweb_search for current info)MCP (Model Context Protocol) lets agents connect to external services —
databases, APIs, Slack, GitHub, etc. Each MCP server is declared as a
YAML file in tools/mcp/:
my-agent/
tools/
mcp/
github.yaml
slack.yamlMCP server config format (tools/mcp/github.yaml):
transport: http
url: https://mcp-server.example.com/sse
headers:
Authorization: Bearer ${GITHUB_TOKEN}transport: must be httpurl: the MCP server's SSE endpoint URLheaders: optional auth headers (use ${ENV_VAR} for secrets)When to recommend MCP:
Finding MCP servers: Use web_search (if available) or web_fetch
to search for available MCP servers. Good starting points:
<service-name> MCP server" (e.g. "Slack MCP server",
"Postgres MCP server")If the user mentions a specific service they want to connect to,
use web_search or web_fetch to find if an MCP server exists
for it and how to configure it.
What to tell the user: MCP servers are external processes that expose tools via HTTP. The user needs to run the MCP server separately (or use a hosted one) and provide the URL in the config.
Python files in tools/python/ are auto-discovered. Each
@tool-decorated module-level function in those files becomes a
separate tool — one file may export many tools. The decorator
derives the JSON schema from the function's type hints and
Google-style docstring.
# tools/python/my_tools.py
from omnigent.tools import tool
@tool
def my_tool(text: str, count: int = 1) -> str:
"""
Repeat the text count times.
Args:
text: The text to repeat.
count: Number of repetitions (default 1).
"""
return text * countAuthoring rules:
Any and object produce permissive schemas
with no validation.def and async def are supported. Sync def bodies are
wrapped in asyncio.to_thread automatically so they don't
block the event loop.BaseModel arguments are first-class — they get
expanded into the schema correctly with full validation.When to recommend local tools: When the user needs custom logic that isn't covered by builtins or MCP servers.
spec_version: 1
name: my-assistant
description: A helpful assistant.
executor:
type: claude_sdk
instructions: |
You are a helpful assistant. Answer questions clearly and concisely.This is the simplest valid agent — a name, an executor, and instructions. No model is pinned, so it uses the configured provider's default. No skills, no tools, no sub-agents.
spec_version: 1
name: researcher
description: A research agent that searches the web and synthesizes findings.
executor:
type: agents_sdk
tools:
builtins:
- web_search
- upload_file
interaction:
modalities:
input: [text, file]
output: [text]
instructions: AGENTS.mdAn agent can spawn child agents to delegate tasks. Sub-agents are
full agents with their own config.yaml, living in the agents/
directory:
my-agent/
config.yaml
AGENTS.md
agents/
researcher/
config.yaml # sub-agent spec — declares name: researcher
fact-check-worker/
config.yaml # declares name: fact-checker (dir may differ)The parent's config.yaml lists sub-agent names under tools.agents:
tools:
agents:
- researcher
- fact-checker
builtins:
- web_searchEach name must be the declared name of a sub-agent under agents/; the
directory it lives in may differ. The parent must use
executor.type: omnigent — that's what provides the spawn tools. Each
sub-agent is a full agent and may use any executor (claude_sdk,
agents_sdk, or omnigent).
Each sub-agent has its own complete config.yaml:
# agents/researcher/config.yaml
spec_version: 1
name: researcher
description: Sub-agent that searches the web for information.
executor:
type: claude_sdk
tools:
builtins:
- web_search
- web_fetch
instructions: |
You are a researcher. When given a topic, search the web
and return a summary with sources.The parent agent gets sys_session_send (singular), check_task,
and sys_cancel_task tools automatically when sub-agents are
declared. The parent's AGENTS.md should reference them:
You have two sub-agents you can delegate to:
- **researcher** — searches the web for information
- **fact-checker** — verifies claims with evidence
Call `sys_session_send(type="<name>", input="<task>")` to
dispatch one. Emit multiple `sys_session_send` tool calls in the
same response to run sub-agents in parallel. Each result auto-
delivers as a system message when ready — `check_task` polls,
`sys_cancel_task` aborts.For simple agents, sub-agents are overkill. Only suggest them when the user describes a workflow with distinct steps or roles.
Once the agent directory is created:
# Start the server with the agent pre-registered
ap server --agent ./my-agent/
# Or deploy to a running server
ap deploy ./my-agent/ --server http://localhost:6767© omnigent-ai, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in omnigent/onboarding/agent/skills/omnigent-knowledge of omnigent-ai/omnigent.
Open the folder on GitHubat commit 26c8338
Omnigent Knowledge Base next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Omnigent Knowledge Base this skillomnigent-ai/omnigent | 11k | — | ~3.4k | Automated safety check: Pass | Apache-2.0 | |
| Edgeone Makers MigrationTencentEdgeOne/edgeone-makers-tools | 1.9k | 1 repos | ~4.1k | Automated safety check: Pass | MIT | |
| Edgeone Makers AgentsTencentEdgeOne/edgeone-makers-tools | 1.9k | 1 repos | ~5.8k | Automated safety check: Notes | MIT | |
| Create Agentprassanna-ravishankar/repowire | 264 | — | ~388 | Automated safety check: Pass | None | |
| Forge Agent Creatortailcallhq/forgecode | 7.6k | — | ~7.3k | Automated safety check: Pass | Apache-2.0 | |
| Harness Step1 Create Agents Mdsimbajigege/book2skills | 184 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
TencentEdgeOne/edgeone-makers-tools
Migrate existing AI agent projects (LangChain, LangGraph, OpenAI Agents SDK, Claude Agent SDK, CrewAI) to EdgeOne Makers platform conventions.
TencentEdgeOne/edgeone-makers-tools
This skill guides building AI agent endpoints on EdgeOne Makers — five framework routes (DeepAgents, LangGraph, CrewAI, OpenAI Agents SDK, Claude Agent SDK), platform-injected context.store /…
prassanna-ravishankar/repowire
A skill your agent uses when creating, updating, or explaining a standing Repowire agent folder, worker folder, durable-job executor context, or reusable agent-specific AGENTS.md guidance.
tailcallhq/forgecode
Guides creating and editing custom agents for the code-forge application as Markdown files with YAML frontmatter in the project's .forge/agents folder.
simbajigege/book2skills
Harness Engineering 第一阶段:扫描现有项目,生成 AGENTS.md(目录文件)和完整的 docs/ 知识库结构。
mem0ai/mem0
Adds persistent memory to AI apps with the Mem0 Python and TypeScript SDKs: store, search, update and delete user memories, with framework integrations.
omnigent-ai/omnigent
Brings up the Omnigent server and Postgres as a Docker compose stack on any Docker host, and covers the Dockerfile's runtime and host build targets for extending it to a new platform.
omnigent-ai/omnigent
Scans Python agent code for framework imports and recommends the matching Omnigent executor type, or says when the framework is not natively supported yet.
omnigent-ai/omnigent
Runs the Omnigent load test with real hosts and multi-turn sessions against a mocked LLM, then explains the latency results from summary.md.
omnigent-ai/omnigent
Spins up an isolated Omnigent server, runner and mock model to prove a user-facing behavior or bug fix with recorded evidence instead of reasoning from code.
omnigent-ai/omnigent
Spins up a local Omnigent server and exercises the Antigravity (Gemini) SDK harness end to end: building agents, running real turns, smoke tests and bug-bashing.
omnigent-ai/omnigent
Gives patterns for generating a minimal, valid Omnigent agent directory: the config.yaml fields, the right executor type, and the files each agent needs.
Works with
Categories
Reference for the Omnigent agent platform: agent directory layout, config.yaml fields, executor types, harness options, AGENTS.md and skill structure. Omnigent is described as a server that hosts and runs agents through an OpenResponses-compatible API. Users create agent directories, also called agent images, holding configuration, instructions, skills and tools, and the server loads them and serves them over HTTP.
Omnigent Knowledge Base fits situations like: writing a config.yaml for a new Omnigent agent; choosing between the claude_sdk, agents_sdk and omnigent executors; looking up how an Omnigent agent directory is laid out.
Run `npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a claude-code`. Or copy the skill folder (omnigent/onboarding/agent/skills/omnigent-knowledge in omnigent-ai/omnigent) into .claude/skills/omnigent-knowledge in your project. Claude Code loads it when a task matches its description.
Run `npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a codex`. Or copy the skill folder (omnigent/onboarding/agent/skills/omnigent-knowledge in omnigent-ai/omnigent) into .agents/skills/omnigent-knowledge in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add omnigent-ai/omnigent --skill omnigent-knowledge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/omnigent-knowledge, .gemini/skills/omnigent-knowledge, .github/skills/omnigent-knowledge and .opencode/skills/omnigent-knowledge in your project.
Going by SKILL.md and its folder, Omnigent Knowledge Base needs credentials named ANTHROPIC_API_KEY and GITHUB_TOKEN.
SKILL.md names 2 domains. As links in the text: modelcontextprotocol.io and github.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Omnigent Knowledge Base is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 3.4k tokens (SKILL.md is roughly 14k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Omnigent Knowledge Base: Edgeone Makers Migration (TencentEdgeOne/edgeone-makers-tools, 1.9k stars), Edgeone Makers Agents (TencentEdgeOne/edgeone-makers-tools, 1.9k stars), Create Agent (prassanna-ravishankar/repowire, 264 stars) and Forge Agent Creator (tailcallhq/forgecode, 7.6k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
omnigent-ai (a GitHub organization) maintains it in omnigent-ai/omnigent, which has 10,661 GitHub stars. The repository holds 19 skills in this directory. The repository was last updated on October 8, 2026.
Source: omnigent-ai/omnigent on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.