[FEATURE] skill metadata - limit tool visibility
Preflight Checklist
- [x] I have searched existing requests and this feature hasn't been requested yet
- [x] This is a single feature request (not multiple features)
Problem Statement
Currently when a user invokes a skill, the workflow from the skill.might trigger tools configured outside of the skill.
In some cases this produces an undesirable result. E.g: the user configured manually ab mcp server and now it has contradicting context
Proposed Solution
Add metadata to the skill with which tools are available/visible to the skill. The current allowed-tools is for auto approval of tools without asking permission.
The use case above is different. Want to be able to specify visibility and not even be asked. By default available tools must be tools self contained in the plugin with the option to extend that list.
Alternative Solutions
_No response_
Priority
High - Significant impact on productivity
Feature Category
CLI commands and flags
Use Case Example
_No response_
Additional Context
_No response_
This issue has 2 comments on GitHub. Read the full discussion on GitHub ↗