Skip to content

[Feature] Document full skillset lifecycle in ornn-agent-manual-cli (and chrono-ai-service-manual) #1085

@chronoai-shining

Description

@chronoai-shining

Summary

Core skillsets (#969 + follow-on web + search + member viewer + detail work) are shipped and merged to develop. The authoritative agent-facing manuals (skills/ornn-agent-manual-cli/SKILL.md and the unified chrono-ai-service-manual) have no coverage of skillsets yet.

Agents using the NyxID proxy / direct HTTP still only see the skill lifecycle. We must add parallel sections for:

  • Skillset search (/skillset-search)
  • Create skillset + publish new version (with required instructions master prompt)
  • Get detail + versions
  • Permissions / visibility
  • One-call closure (/skillsets/:idOrName/closure) including the top-level instructions
  • Member validation rules, kinds (generic vs consensus-supported)
  • How to use a resolved skillset (the instructions tell the agent the orchestration)

Why this matters

Ornn's primary customer is the AI agent. The manuals + the MCP skill_search surface are how agents discover the contract. Skillsets are the "curated bundle + master prompt" abstraction that directly serves agent composition / consensus use cases.

Scope for v1

  • Add §-level sections in the CLI manual (mirroring the structure and style of the existing skill sections).
  • Update the HTTP manual only if it is not fully deprecated (note says prefer the unified one).
  • Bump the manual's version: in frontmatter.
  • Possibly add a small example skillset or note in the manual.
  • Follow-up PR for any MCP tool additions if the ornn MCP server is in this repo.

Acceptance

  • An agent reading the updated manual can fully searchSkillsets, createSkillset, publishSkillset, getSkillsetClosure, set permissions, and understand the instructions field.
  • No drift from CONVENTIONS.md §2.6 and the live routes.
  • Changeset included.
  • Links back to this issue.

Related

Metadata

Metadata

Labels

apiAPI design & endpointsdxDeveloper experiencephase:4M4 - Platform Powertype:featureNew user-facing capability.webornn-web frontend SPA

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions