Module api_skills 

HTTP adapter over zeroclaw_runtime::skills::SkillsService.

Thin handlers — every endpoint translates request shape → SkillsService call → response shape. No filesystem logic, no validation, no error mapping that isn’t already encoded in SkillsService. The dashboard, the CLI (zeroclaw skills add/edit/bundle ...), and the future TUI all reach the same canonical implementation through their respective surface.

Structs

BundleEntry

BundlesResponse

DeleteQuery

SkillCreateBody

SkillEntry

SkillReadResponse

SkillWriteBody

SkillsListResponse

Functions

handle_create_skill

POST /api/skills/bundles/:alias/skills

handle_delete_skill

DELETE /api/skills/bundles/:alias/skills/:name?purge=true

handle_list_bundles

GET /api/skills/bundles

handle_list_skills

GET /api/skills/bundles/:alias/skills

handle_read_skill

GET /api/skills/bundles/:alias/skills/:name

handle_write_skill

PUT /api/skills/bundles/:alias/skills/:name