Repository navigation
librarian v0.22.1
A patch release from the first real agent that was given librarian's skill and a plain task ("add this comment to record 42"). It was shown the operations without their arguments, so it guessed: two operation names and one argument name were refused before a request went through. With 0.22.1 the same task takes one request, the right one.
For every agent
capabilitiesnames what each operation takes. Every operation comes withargs, the names of its arguments (team?is one that may be left out), andbody: truewhere it takes one.- A refusal over arguments says what the operation takes:
unknown arguments for 'addComment': record. It takes: id and a body. - An operation written another way is answered with the one that exists:
unknown operation 'add_comment' on 'demo'. Did you mean 'addComment'?Only among the operations that agent is shown anyway: nothing is suggested thatcapabilitieswould not list for it. - A search whose words fit an API but none of its operations lists them all the same.
capabilitieswith a query used to return such an API with an empty list, and the agent started guessing. It now gets the first 20. - The skill (
skills/librarian) tells agents to use the names inargs. A kagent Agent takes it from this release's image by digest:oci: ghcr.io/kultar/librarian@sha256:fd43776773c3a5e8d226e314d57d63e67c1734523e2f92c0062489f7de98dbc6,path: skills/librarian.
Documentation
- README, Big APIs: what
capabilitieslists (the ten best-fitting APIs and 20 operations of each to a query, the first 50 of each API without one) and how large its answer is.
Upgrade
- No configuration changes are needed.
capabilitiesanswers are larger, about 1.3 to 1.8 times. Measured on GitHub's API: 3 KB to a query for an agent that only reads, 7 KB for one that may also ask for writes.- Three refusals say more than before (unknown arguments, a missing required argument, an unknown operation). Whatever matched their whole text has to match their beginning.