Expand description
Skill shapes.
These are the one corner of the contract that speaks camelCase — the console’s skills schemas predate the snake_case convention the rest of tapes uses. The models carry snake_case field names with the wire spelling attached, so a Rust call site reads like Rust and the bytes stay the document’s.
Structs§
- Create
Skill Request - The POST /v1/skills body for an authored-from- scratch skill — only a name is required; the rest default to an empty private draft.
- Generate
Skill Request - The POST /v1/skills/generate body. It mirrors the console’s GenerateSkillInput: the client nominates source sessions plus optional hints, and the server is authoritative on the skill body.
- Generate
Skill Request Hint - The optional authoring hints on a generate request.
- Publish
Skill Request - The POST /v1/skills/:slug/versions body.
- Session
Skills Response - The envelope for the skills attributed to one session.
- Skill
Counts - The tab counts for the current search: all matching, authored by the caller (mine), and everyone else’s (team = all - mine).
- Skill
Response - The unified Skill shape the console expects (camelCase).
- Skill
Version Response - One immutable published snapshot.
- Skill
Versions Response - The full version history for one skill, newest first.
- Skills
List Response - The paginated list envelope: one keyset page plus the opaque next_cursor (mirroring /v1/sessions) and the per-tab counts for the active search.
- Update
Skill Request - The PUT /v1/skills/:slug body — all fields optional; only present fields are applied onto the existing record.