{
  "id": 97774,
  "title": "Azure and Community Guidelines on Choosing Between a Skill or a Sub-Agent",
  "url": "https://urgent.news/2026/08/03/azure-and-community-guidelines-on-choosing-between-a-skill-or-a-sub",
  "topic": "tech",
  "section": "Tech",
  "published": "2026-08-03T19:00:00.000Z",
  "source": {
    "name": "InfoQ",
    "slug": "infoq",
    "url": "https://www.infoq.com/news/2026/08/choosing-between-subagent-skills/"
  },
  "original_language": "en",
  "account": "In a recent Azure Architecture blog post, Kishorekumar Pattabiraman, an Azure lead engineer, discusses the factors to consider when deciding between implementing a skill or a sub-agent for building AI systems. Pattabiraman emphasizes the importance of reusability, simplicity, and long-term maintainability in the decision-making process.\n\nThe fundamental distinction between a skill and a sub-agent lies in their architecture: a skill operates within an ongoing conversation, while a sub-agent performs a single task independently and provides a final output. Pattabiraman notes that both have their place, depending on the specific task at hand.\n\nTo determine the appropriate choice, Pattabiraman highlights four key dimensions to evaluate: iteration model, voice fidelity, human gate placement, and the frequency of task repetition. The frequency of task repetition emerges as the key differentiator, with one-off tasks favoring a skill-based approach and repeatable batch jobs aligning better with a sub-agent.\n\nOther factors, such as the level of human involvement and the complexity of orchestration, require further consideration. Pattabiraman outlines the trade-offs and potential pitfalls associated with each dimension, providing valuable insights for architects and developers in the AI space.",
  "summary": "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 systems, emphasizing reusability, simplicity, and long-term maintainability. By Sergio De Simone",
  "key_points": [],
  "editors_take": null,
  "illustration": null,
  "coverage": {
    "outlets": 1,
    "also_reported_by": []
  },
  "ai_generated": true,
  "disclaimer": "Summaries, key points and the editor’s take are written by software from other outlets’ reporting and may contain errors — always check the linked original."
}