dull-bird/deeporbit · Archived

do.agent

Detect agent CLIs installed on this machine (omp, claude, gemini, codex), let the user pick one for DeepOrbit to hand execution to, and show the current configuration.

First seen Jul 25, 2026

Installation

$ npx skills add dull-bird/deeporbit --skill do.agent

Summary

  • Detect agent CLIs installed on this machine (omp, claude, gemini, codex), let the user pick one for DeepOrbit to hand execution to, and show the current configuration.
  • Use when the user wants to connect/configure an agent CLI, asks which agents are available, mentions ACP/RPC/-p mode handoff, or asks to see the current agent status.

Stronger alternatives

This repository is archived — consider an actively maintained alternative.

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from dull-bird/deeporbit · top by installs.

npx skills add dull-bird/deeporbit

Browse all from dull-bird/deeporbit

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Declared
Cursor Not declared
Codex Declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 5
License LICENSE
Default branch master
Open issues 0
Status Archived

Skill metadata

Parsed from SKILL.md frontmatter.

Declared agents claude-code codex gemini

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 3,075 B
  • docs SUMMARY.md 350 B

History

  1. First seen on skills.sh
  2. First recorded snapshot · 2 installs

SKILL.md

Agent — Local Agent CLI Configuration

DeepOrbit prepares context (prompts, vault state, cron instructions) and hands execution to an agent CLI on the machine. This skill detects what is installed, asks the user to choose, persists the choice in deeporbit.json (agent: section), and reports status.

Modes

Mode Meaning Best for
acp Agent Client Protocol over stdio, streaming dashboard chat, interactive runs
rpc NDJSON RPC (omp only: omp --mode rpc) programmatic pipelines
print one-shot -p / exec cron jobs, batch handoff

Workflow

  1. Detect:

``bash deeporbit --vault . agent detect [--versions] ``

Lists every known agent (omp, claude, gemini, codex), whether it is installed, where, and which modes it supports.

  1. Ask the user which agent to use. Use the runtime's native ask form

(e.g. an interactive question with one option per installed agent). Present name, description, and supported modes. Recommend the agent that supports acp when the user wants the dashboard assistant; print for pure automation. If only one agent is installed, confirm instead of asking.

  1. Configure:

``bash deeporbit --vault . agent configure <name> [--mode acp|rpc|print] ``

Omitting --mode picks the preferred one automatically (acp > rpc > print). The choice is validated (installed + mode supported) and saved to deeporbit.json — it syncs with the vault as a preference; detection always runs live.

  1. Status:

``bash deeporbit --vault . agent status ``

Shows the configured agent, whether it is actually available on this machine (available: false means the config synced to a machine without that CLI — suggest re-configuring), and the full detection table.

Where the configuration is used

  • deeporbit --vault . serve — the dashboard assistant connects through the

configured agent's ACP mode when --agent auto (the default).

  • deeporbit --vault . cron run-due — due-job instructions are meant to be

handed to the configured agent; agent status shows the exact argv.

  • The dashboard's 助手 view has an Agent 配置 panel that calls the same

/api/agent/config endpoints.

Guardrails

  • NEVER configure an agent that detection says is not installed — tell the

user how to install it instead.

  • The agent: section in deeporbit.json is a preference, not machine

state; never treat it as proof the CLI exists — always check available.

  • agent clear removes the configuration; the dashboard then falls back to

auto-detection order (omp → claude → gemini).