feat: discover entity-linked RunbookSet skills and knowledge - #104
Merged
Conversation
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
Add entity-driven RunbookSet Skill and Knowledge discovery to the UnifiedModel Query Service, plus a bundled runner that loads one exact inline Skill and applies policy-controlled inline Knowledge without moving Tool authority into UnifiedModel.
Motivation
Agents should discover capabilities from the EntitySet they are operating on through list_method(), then progressively load only the related RunbookSet content. Skill instructions and Knowledge stay model-driven, while Tool schemas, authorization, confirmation, execution, and read-back remain owned by the caller runtime.
Changes
Test plan
Compatibility
Additive SPL behavior. list_skill remains an alias normalized to list_skills. list_knowledge is canonical only. Response headers, IDs, localization, optional serialization, and method return types align with the existing UModel Assistant contract. No new public REST endpoint or MCP tool is introduced.
Out of scope