Add fallback to global tools=[] when skill scripts/ is empty

[rafaelsilvadeandrade-dot]

Problem:

Currently, when an agent uses Skills, the get_skill_script function only searches for scripts inside the skill's scripts/ directory. If the directory is empty or the referenced tool doesn't exist there, the agent simply fails to find anything — there is no fallback to the global tools=[] scope.

This means that if a SKILL.md documents a process that relies on an MCP tool (or any tool registered globally via tools=[]), the agent cannot execute it, because Skills and Tools operate in completely separate scopes.

Expected Behavior:

When get_skill_script finds an empty scripts/ directory (or doesn't find the referenced script), the agent should fallback to searching the global tools=[] registered on the agent.

Flow:

1. Agent reads SKILL.md instructions
2. Agent calls get_skill_script → checks scripts/ folder
3. If scripts/ is empty or script not found → fallback to global tools=[]
4. If a matching tool is found globally → execute it

Why This Matters:

• Skills are great for documenting complex processes in SKILL.md
• MCP tools (via MCPTools) are powerful external tools
• But currently you can't combine both — documenting an MCP process inside a skill is useless because the agent can't reach the global tools scope
• This limits the usefulness of Skills as a process orchestration layer

Possible Implementation:
Override the get_skill_script method in the Skill/Toolkit class to add fallback logic
Or add a configuration flag like fallback_to_global_tools=True on the Skill class