cli-a2a
無料Interact with the OmniRoute A2A server from the CLI. Send tasks, inspect skill execution history, and test the JSON-RPC 2.0 agent-to-agent protocol interactively.
日本語の概要は準備中です。原文の説明を表示しています。
Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and install them to the detected tools via OmniRoute's built-in APIs.
インストール方法を見るインストールする前に、エージェントに与えられる指示の中身を確認できます。
Detect installed CLI coding tools (Claude Code, Codex, Cursor, Copilot, Cline and more), search GitHub for matching agent skills, and install them to the detected tools via OmniRoute's built-in APIs.
npm install -g omniroute # or: npx omniroute
omniroute --version
autostartExample:
omniroute autostart
autostart enableExample:
omniroute autostart enable
autostart disableExample:
omniroute autostart disable
autostart toggleExample:
omniroute autostart toggle
autostart statusExample:
omniroute autostart status
configShow or update CLI tool configuration
Example:
omniroute config
config listList all CLI tools and config status
Flags:
--jsonExample:
omniroute config list
config get <tool>Show current config for a tool
Flags:
--jsonExample:
omniroute config get <tool>
config set <tool>Write config for a tool
Flags:
--model <model>--non-interactive--yes--allow-container-writeExample:
omniroute config set <tool>
config validate <tool>Validate config format without writing
Flags:
--model <model>--jsonExample:
omniroute config validate <tool>
config opencodeGenerate OpenCode config (alias for
Flags:
--model <model>--non-interactive--yes--allow-container-writeExample:
omniroute config opencode
config langExample:
omniroute config lang
config getFlags:
--jsonExample:
omniroute config get
config set <code>Flags:
--forceExample:
omniroute config set <code>
config listFlags:
--jsonExample:
omniroute config list
envShow and manage environment variables
Example:
omniroute env
env showShow current environment variables
Flags:
--jsonExample:
omniroute env show
env get <key>Get a single environment variable
Example:
omniroute env get <key>
env set <key> <value>Set an environment variable (current session only)
Example:
omniroute env set <key> <value>
setupFlags:
--password <value>--add-provider--provider <id>--provider-name <name>--api-key <value>--default-model <model>--provider-base-url <url>--test-provider--non-interactive--listExample:
omniroute setup
updateFlags:
--check--apply--changelog--dry-run--no-backup--yesExample:
omniroute update
<!-- skill:custom-start -->
<!-- Preserved curated content from #6294 (skills/cli-skill-collector authored workflow) -->
Discover and install agent skills for your coding CLI tools — all through OmniRoute's built-in APIs.
This skill teaches you how to:
No separate Skill Collector app needed — OmniRoute's own CLI detection + GitHub search handles everything.
Query OmniRoute's CLI tool detection to find which coding agents are installed:
curl -H "Authorization: Bearer $OMNIROUTE_API_KEY" http://localhost:20128/api/skills/collect/detect
This returns:
CLI_TOOL_IDS: claude, codex, cursor, copilot, opencode, cline, kilocode, hermes, hermes-agent, openclaw, droid, continue, qwen, windsurf, devin, antigravity, etc.)Example response:
{
"tools": {
"codex": { "installed": true, "runnable": true, "command": "codex" },
"claude": { "installed": true, "runnable": true, "command": "claude" },
"cursor": { "installed": false, "runnable": false }
},
"installedToolIds": ["codex", "claude"],
"matchedSkills": [
{ "toolId": "codex", "repo": "user/skill-codex-xxx", "score": 0.85, "stars": 120 },
{ "toolId": "claude", "repo": "user/claude-agent-rules", "score": 0.92, "stars": 340 }
],
"totalSkills": 85
}
For each installed tool, the API returns relevant GitHub repos that contain SKILL.md or agent configuration files. Use the score field to prioritize:
| Score | Recommendation |
|---|---|
| 0.80+ | Excellent — well-maintained, high stars, active |
| 0.60+ | Good — relevant with decent quality |
| 0.40+ | Fair — may need review |
| <0.40 | Low quality — skip |
You can also browse manually:
curl -H "Authorization: Bearer $OMNIROUTE_API_KEY" \
"http://localhost:20128/api/github-skills?minStars=3&maxResults=50"
Install a chosen skill to one or more detected tools:
curl -X POST http://localhost:20128/api/skills/collect/install \
-H "Authorization: Bearer $OMNIROUTE_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"repoName": "user/skill-codex-xxx",
"targets": ["codex", "claude"],
"description": "Agent skill for coding workflows"
}'
This plans the installation path for each target tool:
~/.claude/skills/{category}/~/.codex/skills/{category}/~/AppData/Local/hermes/skills/{category}/~/.opencode/skills/{category}/~/.gemini/skills/{category}/The actual file sync (cloning from GitHub and copying SKILL.md) is done by the agent using standard curl + cp commands.
After installing, verify the skill is in place:
# For Codex
ls -la ~/.codex/skills/imported-github/*/SKILL.md
# For Claude Code
ls -la ~/.claude/skills/imported-github/*/SKILL.md
# For Hermes (Windows)
ls -la ~/AppData/Local/hermes/skills/imported-github/*/SKILL.md
Also re-check detection:
curl -H "Authorization: Bearer $OMNIROUTE_API_KEY" http://localhost:20128/api/skills/collect/detect
AUTH_HEADER="Authorization: Bearer $OMNIROUTE_API_KEY"
# 1. Detect
DETECT=$(curl -s -H "$AUTH_HEADER" http://localhost:20128/api/skills/collect/detect)
# 2. Pick top matched skill for first installed tool
TOOL=$(echo "$DETECT" | python3 -c "import sys,json;d=json.load(sys.stdin);print(d['installedToolIds'][0] if d['installedToolIds'] else '')")
SKILL=$(echo "$DETECT" | python3 -c "import sys,json;d=json.load(sys.stdin);ms=d.get('matchedSkills',[]);print(ms[0]['repo'] if ms else '')")
if [ -n "$TOOL" ] && [ -n "$SKILL" ]; then
# 3. Install
curl -s -X POST http://localhost:20128/api/skills/collect/install \
-H "$AUTH_HEADER" \
-H "Content-Type: application/json" \
-d "{\"repoName\": \"$SKILL\", \"targets\": [\"$TOOL\"]}"
echo "Installed $SKILL to $TOOL"
fi
docs/frameworks/SKILLS.md for custom-port setups./api/skills/collect/* and /api/github-skills endpoints require management-scoped authentication the same way every other /api/skills/* route does: a dashboard session, the loopback CLI token, or an API key with the manage scope (requireManagementAuth()). Auth is only bypassed when the server has no login/API-key requirement configured at all.まだレビューはありません。使ってみた感想をお寄せください。
概要と使いどころ
Interact with the OmniRoute A2A server from the CLI. Send tasks, inspect skill execution history, and test the JSON-RPC 2.0 agent-to-agent protocol interactively.
日本語の概要は準備中です。原文の説明を表示しています。
Backup and restore OmniRoute data from the CLI. Trigger incremental snapshots, sync to cloud storage, manage backup schedules, and restore from archive files.
日本語の概要は準備中です。原文の説明を表示しています。
Submit and monitor batch inference jobs from the CLI. Upload and manage files for batch processing, retrieve results, and integrate batch pipelines with CI/CD workflows.
日本語の概要は準備中です。原文の説明を表示しています。
Send chat completions, stream responses, and start an interactive REPL session from the CLI. Supports all OmniRoute providers, combo routing, and system prompt configuration.
日本語の概要は準備中です。原文の説明を表示しています。
Configure and test prompt compression from the CLI. Manage RTK filters, Caveman rules, stacked compression modes, and preview compression output with real prompts.
日本語の概要は準備中です。原文の説明を表示しています。
Manage context engineering configurations, RTK filter sets, and conversation sessions from the CLI. Apply context-relay settings and inspect active context pipelines.
日本語の概要は準備中です。原文の説明を表示しています。