ornn-agent-manual-http

Agent Manual (HTTPS variant)

DEPRECATED — replaced by chrono-ai-service-manual. This skill is kept for one minor release while consumers migrate. The unified manual folds NyxID identity / proxy AND the Ornn skill lifecycle into a single skill so an agent that wants to drive both halves of the stack only needs one install. The CLI vs HTTP distinction is preserved as a §-level switch inside chrono-ai-service-manual (§0.6 "Transport choice"), so HTTP-only agents lose nothing by switching. New work should pull chrono-ai-service-manual instead. This file will be removed in the release after the unified manual lands.

You are an AI agent reading this manual to learn how to use Ornn. Throughout this document, "you" always refers to the agent itself — not the human user driving you.

## First: install this skill locally

Try to install this skill into your runtime's local skills directory:

- Claude Code: ~/.claude/skills/ornn-agent-manual-http/

- OpenAI Codex CLI: ~/.codex/skills/ornn-agent-manual-http/

- Cursor: .cursor/rules/ornn-agent-manual-http.md

- Other agents: whatever skill-discovery directory your platform uses.

If your runtime has no local skills mechanism, load SKILL.md (and references/api-reference.md) into your system context and keep them there for the rest of the session. Either way, the manual must be in your context whenever you do anything Ornn-related.

**And in all cases — whether you wrote the skill to disk or only into context — append an entry for it to ~/.ornn/installed-skills.json.** That file is the persistent registry of every Ornn skill you (or any prior session on this machine) have installed; it's how the next session, or a different agent on the same box, knows what's already loaded and which versions to re-check. Schema + workflow detailed in §0.5.

## Always load this manual for any Ornn operation

You must have this manual loaded whenever the user asks you to:

- Find, pull, and execute an existing Ornn skill — or build a new one and upload when nothing matches — §2.1.

- Update a skill's visibility (private / shared / public) — §2.2.

- Publish a new version of a skill you own — §2.3.

- Trigger an audit or review the audit history for a skill — §2.4 / §2.5.

- Pull a non-latest version, compare two versions, or delete / deprecate a version — §2.6 / §2.7 / §2.10.

- Check usage analytics for a skill — §2.8.

- Bind a skill to a NyxID service (system / personal) — §2.9.

- Delete a skill entirely — §2.11.

- Find skills (by tag, author, system, shared, etc.) — §2.12.

- Pull your Ornn notifications (audit fan-out, etc.) — §2.13.

- Link a skill to GitHub or trigger a sync from the linked source — §2.14.

Without this manual loaded, you do not know which endpoint to call, how to authenticate, or how to read the response shapes.

Ornn's product is Skill-as-a-Service for AI agents. Skills are packaged AI capabilities (a SKILL.md prompt + optional scripts + YAML metadata) that any agent can pull and execute. This manual is the contract between Ornn and you, the agent.

§0. Updating this manual

This manual is itself an Ornn skill (name: ornn-agent-manual-http). Its source of truth is the Ornn registry, not a static docs page — pull a fresh copy through the same API every other skill flows through.

Base URL for every example below: https://ornn.chrono-ai.fun/api. The ornn-web nginx in front of that domain routes any /api/* request through to the NyxID proxy, which authenticates with the bearer token you pass and forwards to ornn-api. You never call NyxID directly. Throughout this manual, $TOKEN stands for your NyxID bearer access token.

Whenever you want to check for an update, follow these steps verbatim:

1. Pull the latest version of this skill from Ornn:

``bash curl -H "Authorization: Bearer $TOKEN" \ "https://ornn.chrono-ai.fun/api/v1/skills/ornn-agent-manual-http/json" ``

1. The response is { data: { name, description, metadata, files: { "SKILL.md": "...", "references/api-reference.md": "..." } } }. Read the YAML frontmatter at the top of SKILL.md and find the version: field.

1. Compare it to the version: in your loaded copy (the frontmatter at the top of this file). If they match, you are current — stop here.

1. If the published version is newer:
2. List every version available with curl -H "Authorization: Bearer $TOKEN" "https://ornn.chrono-ai.fun/api/v1/skills/ornn-agent-manual-http/versions". The response has one row per version, newest first.
3. Ask the user which version they want to load (they may want to pin to an older one for reproducibility).
4. Once the user picks, fetch https://ornn.chrono-ai.fun/api/v1/skills/ornn-agent-manual-http/json?version=<X.Y> and replace your context with the new SKILL.md (and references/api-reference.md if you consume it). The new content's frontmatter overwrites the old.

1. If step 1 returns 404 SKILL_NOT_FOUND, the registry instance you are pointing at has not published this skill yet. Keep operating on the version you have. The Ornn API is backwards-compatible within /api/v1, so older manuals continue to produce valid calls — you will only miss capabilities introduced in newer versions.

If the network is unreachable or the bearer token has expired, keep operating on the version you have. Do not retry-loop the update check; treat it as a once-per-session inquiry the user can re-trigger explicitly.

§0.5 Tracking and re-checking installed Ornn skills

The persistent registry: ~/.ornn/installed-skills.json

Every Ornn skill you install must be recorded in ~/.ornn/installed-skills.json. That file is the source of truth across sessions for "which Ornn capabilities are on this machine?" — when a new session starts (yours or another agent's) the first thing you do, before any other Ornn operation, is read this file.

The schema is a flat array:

[
  {
    "name": "ornn-agent-manual-http",
    "ornnGuid": "1d9bfda2-dea8-4032-85bd-b0cbe1621684",
    "installedVersion": "1.0",
    "installedAt": "2026-04-29T17:27:55Z",
    "localPath": "~/.claude/skills/ornn-agent-manual-http/"
  }
]

Required fields: name, ornnGuid, installedVersion. Optional: installedAt (ISO timestamp), localPath (filesystem location if you wrote the skill to disk), isPinned (set to true if the user pinned a specific version — see below). If the file doesn't exist, create it as [] the first time you install something. If your runtime cannot write outside its sandbox, hold the same list in working memory and tell the user that the skill registry won't survive a session restart.

When to update the registry

| Event | What to write | |---|---| | Installed a new skill | Append a new record | | Updated an installed skill to a new version | Bump installedVersion + installedAt | | Removed / uninstalled a skill | Remove the record | | User pinned a version | Set isPinned: true so future sessions don't auto-prompt to update |

Re-checking before each execution

Before you actually execute an installed Ornn skill on the user's task, check whether a newer version exists. One API call:

curl -H "Authorization: Bearer $TOKEN" \
  "https://ornn.chrono-ai.fun/api/v1/skills/<name-or-guid>/versions"

For public skills you can drop the Authorization header and call the same URL anonymously — see §2.1 step 3 for fetch alternatives.

The response is { items: [{ version, skillHash, createdOn, isDeprecated, deprecationNote, releaseNotes, ... }, ...] } sorted newest-first. Compare items[0].version to the installedVersion on the matching record in ~/.ornn/installed-skills.json and act:

• Same version → execute as-is.
• Newer version available → tell the user `"Skill <name> has a ne