progressive-discovery-skill

Load connected tools progressively and delegate tasks to specialized agents.

356|66|Updated Oct 13, 2025
One-click install
npx skills add https://github.com/zeenie-ai/MachinaOS --skill progressive-discovery-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: progressive-discovery-skill
Source: https://github.com/zeenie-ai/MachinaOS/tree/main/server/skills/autonomous/progressive-discovery-skill
Command: npx skills add https://github.com/zeenie-ai/MachinaOS --skill progressive-discovery-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of wasted tokens and confused context by discovering and loading capabilities progressively instead of upfront.

Core Features & Use Cases

  • Progressive capability loading: starts with minimal context and checks what’s actually connected before taking action.
  • Capability-aware delegation: delegates to specialized agents only when the required tool set isn’t directly connected.
  • Focused execution context: passes only relevant context to reduce noise and improve decision quality.
  • Use Case: When a user asks for battery level, it checks whether an android capability is connected and delegates appropriately rather than loading unrelated tools.

Quick Start

Ask the agent to handle a task like “Check the battery level,” and it will determine which connected capability is needed, use it directly when available, or delegate to the most relevant specialized agent.

Frequently Asked Questions about progressive-discovery-skill

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I reduce LLM token overhead when an agent has many tools connected?

To reduce LLM token overhead, use progressive tool discovery to load capabilities only when needed instead of upfront. This approach checks which tools are actually connected before taking action, avoiding context pollution from enumerating all available tools at once.

What is progressive capability loading in agent orchestration?

Progressive capability loading is a context management technique where an agent starts with minimal context and discovers connected tools dynamically. It routes tasks by checking available capabilities first, delegating to specialized agents only when direct tools are missing.

How do I delegate tasks to specialized agents without wasting context?

Delegate tasks by checking if the required tool set is directly connected to the current agent. If the capability is missing, route the task to a specialized agent while passing only the focused execution context needed, reducing noise and improving decision quality.

Does this approach work for diverse agent capabilities like device control and web access?

Yes, capability-aware delegation works for device control, coding, web access, scheduling, messaging, and travel planning. It applies conditional routing to find the correct direct tool or specialized agent without loading unrelated tools into the context.

When should I avoid loading all tools upfront in an agent workflow?

You should avoid upfront tool enumeration when managing complex agent workflows with diverse capabilities. Loading everything at once causes context pollution and wasted tokens; instead, use conditional delegation to execute with focused context only for the required capability.

What's the best way to route agent tasks based on connected capabilities?

The best way to route agent tasks is through capability checking of connected tools before execution. This method applies conditional delegation to the correct agent and maintains a focused execution context, avoiding the token optimization issues of upfront loading.