{{ message }}
Repository navigation
feat(mothership): send workspace skill ids and descriptions in the chat inventory - #9264
Merged
Merged
Conversation
…at inventory The mothership agent now sees workspace skills as a catalog, name, id and description, and loads a matching one with skills get <id>, as Agent Skills clients do; with names alone it could not judge relevance and had to search for an id first. Built-ins carry their builtin-<name> id. The generated protocol copy is synced from the worker contract, where both fields are optional so either side can ship first.
|
Contributor
This branch was previously deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.

Summary
idanddescription, not just its name, built-ins included (builtin-<name>). The mothership agent can then show workspace skills as a catalog (name, id, description) and load a matching one withskills get <id>, the way frontier clients and the Agent Skills spec list name and description and load the body on demand. Before, it saw only names: it couldn't judge relevance, and it needed a search round to find an id.generated/protocol.tsis regenerated from the worker contract. The new fields are optional, so either side can deploy first.Companion: simstudioai/mothership#778
Type of Change
Testing
workspace-inventory.test.tsnow checks skill ids and descriptions, including a built-in and an empty description. It fails before the change; after, 2 pass. CI runs the rest.Checklist