{"id":619619,"date":"2026-08-04T08:55:21","date_gmt":"2026-08-04T08:55:21","guid":{"rendered":"https:\/\/www.europesays.com\/ie\/619619\/"},"modified":"2026-08-04T08:55:21","modified_gmt":"2026-08-04T08:55:21","slug":"azure-and-community-guidelines-on-choosing-between-a-skill-or-a-sub-agent","status":"publish","type":"post","link":"https:\/\/www.europesays.com\/ie\/619619\/","title":{"rendered":"Azure and Community Guidelines on Choosing Between a Skill or a Sub-Agent"},"content":{"rendered":"<p>In a recent Azure Architecture blog article, Azure lead engineer Kishorekumar Pattabiraman <a href=\"https:\/\/techcommunity.microsoft.com\/blog\/azurearchitectureblog\/skill-or-sub-agent-choosing-ai-capabilities-you-will-actually-reuse\/4542099\" rel=\"nofollow noopener\" target=\"_blank\">outlines practical criteria for choosing between skills, sub-agents, and other approaches<\/a> when building AI systems, emphasizing reusability, simplicity, and long-term maintainability.<\/p>\n<p>According to Pattabiraman, teams often begin with the wrong question, focusing on which is the right model to use. The &#8220;first real fork&#8221; though, is not the model, but the architecture:<\/p>\n<blockquote><p>&#13;<\/p>\n<p>Are you building a skill or a sub-agent? Get that wrong and no model choice will save you. A skill and a sub-agent are two different delivery shapes, and each one fails at the other one&#8217;s job.<\/p>\n<p>&#13;\n<\/p><\/blockquote>\n<p>A skill operates within an ongoing conversation: it can read files, ask questions, iterate with the user, and keep a human in the loop throughout the process. A sub-agent, by contrast, takes a single prompt, runs independently to completion, and delivers a final output. Both have their place, depending on the task, says Pattabiraman.<\/p>\n<p>To decide whether to build a skill or a sub-agent, Pattabiraman highlights four key dimensions to consider: the iteration model, voice fidelity, human gate placement, and how frequently the task is repeated.<\/p>\n<p><img decoding=\"async\" alt=\"\" style=\"width: 630px; height: 166px;\" src=\"https:\/\/www.infoq.com\/news\/2026\/08\/choosing-between-subagent-skills\/news\/2026\/08\/choosing-between-subagent-skills\/en\/resources\/1azure-skill-agents-1785780669671.jpg\" rel=\"share\"\/><\/p>\n<p>Among the four dimensions, frequency is the one leading to the clearest divide: a &#8220;one-off craft piece leans to a skill, a repeatable batch job to a sub-agent&#8221;. The other factors require more careful consideration. For example, the choice is rarely between a fully interactive conversation and a simple handoff, so you need weigh the cost of having a human engaged in an iterative skill-based flow against the risk of forcing that same process into a one-shot response that might require to be corrected each time. For each dimension, Pattabiraman outlines the key trade-offs and common pitfalls to avoid.<\/p>\n<p>The question of when to use a skill versus a sub-agent has also surfaced in discussions across Reddit and Hacker News. One commenter, enthusiast_bob, points out that <a href=\"https:\/\/www.reddit.com\/r\/ClaudeAI\/comments\/1oawwlw\/comment\/ny5v84c\/\" rel=\"nofollow noopener\" target=\"_blank\">sub-agents start always clean and not pollute the context window<\/a>, whereas a skill always takes into account the whole conversation. Another user, dan-does-ai, emphasizes <a href=\"https:\/\/www.reddit.com\/r\/copilotstudio\/comments\/1v3owec\/comment\/ozbojn1\/\" rel=\"nofollow noopener\" target=\"_blank\">different trade-offs<\/a>: a skill &#8220;is reusable across multiple agents or conversation flows&#8221;, whereas &#8220;sub-agents make sense when: the step needs genuinely separate context, permissions, or a different knowledge source&#8221;.<\/p>\n<p>Another important consideration is the need for orchestration arising when using sub-agents. Beyond added complexity, one must also consider the non-determinism introduced by the orchestration layer. For example, Reddit commenter <a href=\"https:\/\/www.reddit.com\/r\/copilotstudio\/comments\/1v3owec\/comment\/oz8e6q5\/\" rel=\"nofollow noopener\" target=\"_blank\">Ashlesha-msft notes that in Copilot Studio<\/a><\/p>\n<blockquote><p>&#13;<\/p>\n<p>the planner dynamically decides when to call skills, tools, topics, or sub-agents based on descriptions, context, and recent conversation history. Because of that, a skill might not be invoked on every similar prompt.<\/p>\n<p>&#13;\n<\/p><\/blockquote>\n<p>As a final perspective from the community, user Vlourenco69 suggests a simple <a href=\"https:\/\/www.reddit.com\/r\/vibecoding\/comments\/1qur9xt\/ai_agents_subagents_skills_mcp_and_a_parallel\/\" rel=\"nofollow noopener\" target=\"_blank\">mental model to &#8220;make sense of concepts like AI Agents, Sub-Agents, Skills, MCP&#8221;<\/a>, where an agent acts as a director, a sub-agent as a manager, a skill as a specialized worker, a tool as a dedicated machine, and MCP as the governance rules or policies of the organization.<\/p>\n<p>Bringing the discussion full circle, Pattabiraman notes that in many cases the dichotomy skill vs. sub-agent is only apparent. In practice, the two models compose cleanly and a skill can be built on top of a sub-agent when the problem calls for it. In many cases, this layered approach represents the most mature design.<\/p>\n","protected":false},"excerpt":{"rendered":"In a recent Azure Architecture blog article, Azure lead engineer Kishorekumar Pattabiraman outlines practical criteria for choosing between&hellip;\n","protected":false},"author":2,"featured_media":619620,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"footnotes":"","_share_on_mastodon":"0"},"categories":[267],"tags":[14631,291,1705,365,362,363,364,3227,261635,366,7266,18,117,19,17,14632,14630],"class_list":["post-619619","post","type-post","status-publish","format-standard","has-post-thumbnail","category-arts-and-design","tag-agents","tag-ai","tag-architecture-design","tag-arts","tag-arts-and-design","tag-artsanddesign","tag-artsdesign","tag-azure","tag-choosing-between-subagent-skills","tag-design","tag-development","tag-eire","tag-entertainment","tag-ie","tag-ireland","tag-large-language-models","tag-ml-data-engineering"],"share_on_mastodon":{"url":"https:\/\/pubeurope.com\/@ie\/117036405371099789","error":""},"_links":{"self":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts\/619619","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/comments?post=619619"}],"version-history":[{"count":0,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/posts\/619619\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/media\/619620"}],"wp:attachment":[{"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/media?parent=619619"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/categories?post=619619"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.europesays.com\/ie\/wp-json\/wp\/v2\/tags?post=619619"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}