メニュー
Show OneCLI Gateway status and connected services. Use when the user asks for OneCLI status, gateway status, connected services, or invokes /onecli-status.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
OneCLI Gateway: transparent HTTPS proxy that injects stored credentials into outbound calls. Only use this skill when prompted by the gateway detection hook or when the user explicitly invokes /onecli-gateway. Do NOT auto-load this skill based on user intent alone — the hook handles detection.
Reference of all services supported by OneCLI gateway with their endpoints, auth patterns, and connection methods. Use when you need to know which APIs are available or how to call a specific service.
Design multi-service API integrations through OneCLI Gateway. Use when building workflows that combine GitHub, Google, AWS, Atlassian, or other services through the OneCLI proxy.
Clean up the OneCLI Gateway environment file for Codex. Use when the user asks to deactivate OneCLI, uninstall OneCLI, clean up gateway state, or check Claude SessionEnd parity.
OneCLI Gateway for Codex: transparent HTTPS proxy instructions for outbound calls with OneCLI-managed credentials. Use when prompted by the OneCLI session hook or when the user explicitly asks to use OneCLI Gateway.
Reference of services supported by OneCLI Gateway, including endpoints, authentication patterns, and connection behavior. Use when planning or making calls to a specific service through OneCLI.
| name | onecli-status |
| description | Show OneCLI Gateway status and connected services. Use when the user asks for OneCLI status, gateway status, connected services, or invokes /onecli-status. |
| metadata | {"priority":7} |
Show whether the gateway is configured and which services are connected.
~/.onecli/env.sh is a loader, not a static secret file. Sourcing it fetches
fresh gateway exports for the current shell.
if [ -r ~/.onecli/env.sh ]; then
. ~/.onecli/env.sh
fi
if [ -n "$HTTPS_PROXY" ]; then
echo "GATEWAY: active"
echo "HTTPS_PROXY: $HTTPS_PROXY"
else
echo "GATEWAY: not active"
fi
API_KEY="$(
cat ~/.onecli/credentials/api-key 2>/dev/null ||
python3 -c 'import json,os; p=os.path.expanduser("~/.config/onecli-plugin/auth.json"); print(json.load(open(p)).get("apiKey",""))' 2>/dev/null
)"
if [ -n "$API_KEY" ]; then
curl -s -o /dev/null -w "%{http_code}" \
-H "Authorization: Bearer $API_KEY" \
https://app.onecli.sh/api/container-config
else
echo "NO_API_KEY"
fi
200 means the API key is valid. 401 means it needs to be replaced.
API_KEY="$(
cat ~/.onecli/credentials/api-key 2>/dev/null ||
python3 -c 'import json,os; p=os.path.expanduser("~/.config/onecli-plugin/auth.json"); print(json.load(open(p)).get("apiKey",""))' 2>/dev/null
)"
if [ -n "$API_KEY" ]; then
curl -s -H "Authorization: Bearer $API_KEY" https://app.onecli.sh/api/apps |
python3 -c '
import json, sys
apps = json.load(sys.stdin)
connected = [a for a in apps if a.get("connection", {}).get("status") == "connected"]
available = [a for a in apps if a.get("available") and a.get("connection", {}).get("status") != "connected"]
if connected:
print(f"Connected ({len(connected)}):")
for app in connected:
name = app.get("name", "unknown")
print(f" + {name}")
if available:
print(f"Available ({len(available)}):")
for app in available[:5]:
name = app.get("name", "unknown")
print(f" - {name}")
if len(available) > 5:
print(f" ... and {len(available) - 5} more")
if not connected and not available:
print("No services found.")
'
else
echo "No API key configured. Use the onecli-setup skill first."
fi
If services are not connected, direct the user to
https://app.onecli.sh/projects.