メニュー
Detect Python agent frameworks from code imports and map them to Omnigent executor types. Load when the user has existing agent code to integrate.
デフォルトでは、最初にソースを確認する Prompt が選択されています。直接コマンドに切り替えるか、ローカルコピーをダウンロードすることもできます。
インストールを決める前に、SKILL.md と SkillsMP に表示されている付属ファイルをお読みください。
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
直接コマンドでは確認用 Prompt が省略されます。実行前にソースを確認してください。
npx skills add https://github.com/omnigent-ai/omnigent --skill detect-frameworkコマンドは1行のまま表示されます。コピー前に横へスクロールして全体を確認してください。
ローカルで確認しますか？SkillsMP が現在取得できるファイルをダウンロードできます。
Run the Omnigent server as a Docker compose stack (server + Postgres) on any Docker host — your laptop, a VPS, EC2 by hand, or as the base layer of any container-platform deploy. Invoke when the user wants to build the image, bring up the compose stack, debug the stack on a host they already have, or extend the stack for a new platform.
Spin up a live local Omnigent server and exercise the Antigravity (Gemini) SDK harness end-to-end — build antigravity agents, run real turns, smoke-test, and bug-bash. Load when developing, testing, or debugging the antigravity harness (omnigent/inner/antigravity_executor.py, antigravity_harness.py, omnigent/onboarding/antigravity_auth.py) or its auth / model / tool-bridge behavior.
Verify the Omnigent CLI's setup/onboarding flow, terminal UI/UX, and critical user journeys in a completely isolated, reproducible loop. Drives the real `omnigent` binary through a PTY (pexpect) inside a throwaway OMNIGENT_CONFIG_HOME / OMNIGENT_DATA_DIR sandbox that never touches the user's real ~/.omnigent, captures ANSI-stripped frames for UX inspection, and proves a change is verifiable via a before→fix→after baseline diff. Load when developing or reviewing a CLI setup/onboarding/REPL/picker change (omnigent/cli.py, omnigent/onboarding/*, omnigent/repl/*, scripts/install_oss.sh), reproducing a cold-start/first-run UX bug, or confirming a fix actually lands. Several agents can run it concurrently on separate worktrees.
SOC 職業分類に基づく
SKILL.md を表示中
| name | detect-framework |
| description | Detect Python agent frameworks from code imports and map them to Omnigent executor types. Load when the user has existing agent code to integrate. |
When the user has existing Python code they want to integrate into Omnigent, detect the framework from import statements and recommend the appropriate executor type.
Ask the user for the path to their agent code (or look for Python files in the current directory if filesystem access is enabled).
Scan Python files for import patterns. Check in this priority order:
| Import pattern | Framework | Executor type |
|---|---|---|
import anthropic or from anthropic + agent patterns (e.g. Agent, tool, system prompt setup) | Claude SDK | claude_sdk |
import openai or from openai + agents patterns (e.g. Agent, Runner, function_tool) | OpenAI Agents SDK | agents_sdk |
from langgraph or import langgraph | LangGraph | Not natively supported yet |
from deepagents or import deepagents | DeepAgents | Not natively supported yet |
from langchain or import langchain | LangChain | Not natively supported yet |
from crewai or import crewai | CrewAI | Not natively supported yet |
from autogen or import autogen | AutoGen | Not natively supported yet |
| None of the above | Unknown | Not natively supported yet |
llm (default — no existing code)Generate a standard agent directory:
executor:
type: llm # or omit entirely (llm is the default)
claude_sdkThe user's Claude SDK code runs directly. Generate config that points to their entry module:
executor:
type: claude_sdk
agents_sdkThe user's OpenAI Agents SDK code runs directly:
executor:
type: agents_sdk
If the user's framework is not natively supported, let them know:
llm agent.https://github.com/dbczumar/omnigent/issues/new?title=...&body=...