nyxid-service-skill-authoring

NyxID service skill authoring (via Ornn)

You are an agent facing a NyxID proxy service you do not know how to call: the service publishes no OpenAPI spec, nyxid catalog endpoints <slug> returns nothing, and the only tool available is the generic proxy request (path + method + body). Do not guess endpoint paths from training memory — that is how hallucinated calls happen. Follow this flow instead: find an existing skill on Ornn, or author one from a verifiable source.

Prerequisite: the ornn-agent-manual-cli skill (the Ornn API contract). If it is not already in your context or local skills directory, pull it first:

nyxid proxy request ornn-api "/api/v1/skills/ornn-agent-manual-cli/json" \
  --method GET --output json

All Ornn calls below assume that manual is loaded; it defines authentication, response shapes, and error handling.

No shell? Every step works over plain HTTP

Some agent runtimes cannot execute a CLI but can make HTTP requests. Every nyxid command in this skill has a direct REST equivalent against the NyxID API (base URL below is the deployment you authenticate against, e.g. https://nyx-api.chrono-ai.fun):

• Auth: send Authorization: Bearer <token> on every request — a NyxID agent API key (nyxid_ag_...) or a user access token. Ask the user for a key if you have none; never scrape one from disk.
• Ornn calls: nyxid proxy request ornn-api "<path>" --method M is exactly M {BASE}/api/v1/proxy/s/ornn-api<path> — same path, same body, same JSON response. This holds for every Ornn endpoint in this skill and in the Ornn manual.
• Service inventory (nyxid service list): GET {BASE}/api/v1/keys — the authoritative connected-services view.
• Catalog metadata (nyxid catalog show <slug>): GET {BASE}/api/v1/catalog/{slug}; typed operations (nyxid catalog endpoints <slug>): GET {BASE}/api/v1/catalog/{slug}/endpoints.
• Mount a spec / set skills (nyxid service update ...): PUT {BASE}/api/v1/keys/{id} with the exact ID returned by the keys inventory and a JSON body — e.g. {"openapi_spec_url": "https://..."} (empty string clears) or {"recommended_skills": ["name"]} (empty list clears). The endpoint document alone can also be updated via PUT {BASE}/api/v1/endpoints/{endpoint_id} with the same fields.
• Update account-owned routing or identity settings: resolve the exact UserService ID from GET {BASE}/api/v1/keys, then use PUT {BASE}/api/v1/user-services/{user_service_id} — for example, {"forward_access_token": true}. A catalog service ID is a different identity and must never be used here. Read GET {BASE}/api/v1/keys afterward and verify the same UserService ID. Platform-wide catalog recovery is the separate admin-only POST {BASE}/api/v1/services/{catalog_service_id}/resync-identity API.
• Call the target service through the proxy (nyxid proxy request <slug> ...): M {BASE}/api/v1/proxy/s/{slug}/<path> — NyxID injects the stored credential; never send the downstream credential yourself.