
Azure and Community Guidelines on Choosing Between a Skill or a Sub-Agent
Quick Answer
Azure's Kishorekumar Pattabiraman emphasizes the importance of choosing between skills and sub-agents in AI systems, highlighting four dimensions: iteration model, voice fidelity, human gate placement, and task frequency.
Quick Take
The decision impacts system design, as skills support ongoing conversations while sub-agents handle single prompts independently.
Key Points
- Skills enable ongoing interactions; sub-agents provide final outputs from single prompts.
- Frequency of tasks helps determine whether to use a skill or a sub-agent.
- Sub-agents introduce orchestration complexity and non-determinism in AI workflows.
- Community discussions highlight trade-offs between skills' reusability and sub-agents' context separation.
- Combining skills and sub-agents can lead to more mature AI system designs.
DeepSignal Analysis
What happened
Kishorekumar Pattabiraman from Azure discusses the criteria for selecting between skills and sub-agents in AI systems. He emphasizes the importance of understanding the architecture before choosing a model, as skills support ongoing conversations while sub-agents handle single prompts. Four dimensions are highlighted: iteration model, voice fidelity, human gate placement, and task frequency.
Key evidence
- Pattabiraman states that skills operate within ongoing conversations, allowing for user interaction, while sub-agents complete tasks independently from a single prompt.
- He identifies task frequency as a key factor, noting that one-off tasks favor skills, whereas repeatable tasks are better suited for sub-agents.
- Community discussions reveal that sub-agents maintain a clean context window, while skills consider the entire conversation, indicating different use cases for each approach.
Why it matters
Understanding the distinction between skills and sub-agents is crucial for effective AI system design. The choice impacts how systems interact with users and manage tasks, influencing overall performance and user satisfaction. By clarifying these concepts, teams can better align their AI solutions with specific use cases, ultimately leading to more efficient and maintainable systems.
Source Excerpt
In a recent Azure Architecture blog article, Azure lead engineer Kishorekumar Pattabiraman outlines practical criteria for choosing between skills, sub-agents, and other approaches when building AI sy
Want this in your inbox every morning?
Daily brief at your local 8am — bilingual EN/中文, free.
More from InfoQ AI, ML & Data Engineering
See more →Google Cloud Workbench Notebooks Extension Connects VS Code to Google Cloud's Jupyter Notebooks
The Google Cloud Workbench Notebooks extension for VS Code allows developers to seamlessly connect their local IDE to managed Jupyter notebook environments on Google Cloud, enhancing ML workflow efficiency. This integration eliminates context switching, enabling smooth transitions from local experimentation to high-performance cloud computing.

