Deliver managed skills by download only - #519
Open
xsh310 wants to merge 1 commit into
Open
Conversation
Managed config skills were delivered two ways at once on launch: registered into the skills MCP connection AND downloaded to disk, so every managed skill double-listed (once as an MCP tool, once as a local /skills file). Deliver them by download only and remove the MCP path. Delete apply_managed_skills and drop the launch-time MCP registration for managed skills; the managed download path is unchanged. The managed_skill_locations state field it maintained is now unused; leave any existing values in place since nothing reads them. Co-authored-by: Isaac <no-reply@databricks.com>
xsh310
marked this pull request as ready for review
September 8, 2026 04:48
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.
What
Managed-config skills are now delivered to agents by download only. This removes the managed→skills-MCP registration path (
apply_managed_skillsand themanaged_skill_locationsstate tracker), keeping the download path (_download_managed_skills/download_managed_skills_on_launch) and the managed-config authoring side (setup skills,skills.names) unchanged.Why
The launch path delivered managed skills two ways at once: registered into the skills MCP connection and downloaded to disk. Download and MCP are an either/or choice, so this double-listed every managed skill — once as a local
/skillsfile and once as an MCP tool with the same description, which confuses the agent.Removing the MCP path directly should be safe: since no workspace should be using managed skills yet.
Notes
This is the base of the per-agent skills-scope stack. With managed skills out of the skills MCP connection, that connection holds only a developer's own
skill add --mcpschemas, so the per-agent work above no longer has to union in or track a global managed set.This pull request and its description were written by Isaac.