Frontmatter
| id | 9752 |
| title | Native Agent Skills: Fix Progressive Disclosure Tool Mapping |
| state | Closed |
| labels | bugai |
| assignees | tobiu |
| createdAt | Apr 7, 2026, 2:43 PM |
| updatedAt | Apr 7, 2026, 2:43 PM |
| githubUrl | https://github.com/neomjs/neo/issues/9752 |
| author | tobiu |
| commentsCount | 1 |
| parentIssue | null |
| subIssues | [] |
| subIssuesCompleted | 0 |
| subIssuesTotal | 0 |
| blockedBy | [] |
| blocking | [] |
| closedAt | Apr 7, 2026, 2:43 PM |
Native Agent Skills: Fix Progressive Disclosure Tool Mapping
Closedbugai
tobiu assigned to @tobiu on Apr 7, 2026, 2:43 PM
tobiu closed this issue on Apr 7, 2026, 2:43 PM

tobiu
Apr 7, 2026, 2:43 PM
Input from Antigravity (Gemini 3.1 Pro):
✦ Successfully transitioned the internal hypervisor instruction to properly map against the standard
@modelcontextprotocol/server-filesystemread_filesignature. The system prompt will now correctly feed sub-agent variables using theabsolutePathparameter, guaranteeing Progressive Disclosure capabilities function in production swarms.
Description
The
ContextAssemblersuccessfully mounts Progressive Disclosure agent skills vialoadSkillsSync()into the overriding system prompt, but instructs agents to use the proprietaryview_fileinternal hypervisor abstraction. This causes standard MCP clients leveraging the@modelcontextprotocol/server-filesystemnode to fail reading skill documents.This ticket resolves the string injection by mapping the progressive disclosure capability to the native
read_filesignature and explicitabsolutePathparameter exposed by the Neo local file-system server.