<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic It's time to treat AI as a peer, not a tool. What if your AI already knew Databricks? in Community Articles</title>
    <link>https://community.databricks.com/t5/community-articles/it-s-time-to-treat-ai-as-a-peer-not-a-tool-what-if-your-ai/m-p/151785#M1105</link>
    <description>&lt;P&gt;&lt;SPAN&gt;We need to stop treating AI as a tool. It's time to treat it as a peer.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;I've been building a library of reusable skills for Claude — structured instructions that let AI agents handle complex, repetitive development workflows on Databricks and Azure AI Foundry.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The goal is simple: stop re-explaining the same context every time, and stop reinventing the wheel.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Instead of building everything from scratch, each skill is designed to compose — pulling in existing work from AI Dev Kit, LangGraph and LangChain skill ecosystems, then extending them with Databricks&amp;nbsp;and Azure-specific context. Load a skill and Claude operates with the same domain knowledge a senior engineer would bring to the table: the right patterns, the right APIs, the right tradeoffs — already&amp;nbsp;loaded.&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;So far the library covers:&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;- Databricks Mosaic AI Agents — Model Serving, LangGraph, LangChain, OpenAI Agent SDK, Deep Agents, Human-in-the-Loop, Supervisor Agents&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;- Azure AI Foundry Agents — SDK v2, Memory, Durable Orchestration, AI Gateway, observability with App Insights.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Each skill is versioned, documented, and installable. The repo also includes an MCP server layer, for ai-dev-kit, so these capabilities can be reused across multiple workflows.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;But beyond the technical side, this project is a statement.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;We spend a lot of energy debating whether AI will replace developers. That's the wrong question. The right question is: are you using AI to multiply what you can build?&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;When I treat Claude as a peer — giving it context, structure, and clear objectives — I move faster, think more clearly, and ship better work. Not because I'm doing less, but because I'm doing more of&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;what actually matters.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The shift isn't about automation. It's about raising the floor of what one engineer can do.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The repo is open. If you're building on Databricks or Azure AI and want to skip the boilerplate, it might be worth a look.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/alessandro9110/databricks-foundry-agent-skills" target="_blank"&gt;https://github.com/alessandro9110/databricks-foundry-agent-skills&lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Tue, 24 Mar 2026 08:54:10 GMT</pubDate>
    <dc:creator>Ale_Armillotta</dc:creator>
    <dc:date>2026-03-24T08:54:10Z</dc:date>
    <item>
      <title>It's time to treat AI as a peer, not a tool. What if your AI already knew Databricks?</title>
      <link>https://community.databricks.com/t5/community-articles/it-s-time-to-treat-ai-as-a-peer-not-a-tool-what-if-your-ai/m-p/151785#M1105</link>
      <description>&lt;P&gt;&lt;SPAN&gt;We need to stop treating AI as a tool. It's time to treat it as a peer.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;I've been building a library of reusable skills for Claude — structured instructions that let AI agents handle complex, repetitive development workflows on Databricks and Azure AI Foundry.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The goal is simple: stop re-explaining the same context every time, and stop reinventing the wheel.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Instead of building everything from scratch, each skill is designed to compose — pulling in existing work from AI Dev Kit, LangGraph and LangChain skill ecosystems, then extending them with Databricks&amp;nbsp;and Azure-specific context. Load a skill and Claude operates with the same domain knowledge a senior engineer would bring to the table: the right patterns, the right APIs, the right tradeoffs — already&amp;nbsp;loaded.&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;So far the library covers:&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;- Databricks Mosaic AI Agents — Model Serving, LangGraph, LangChain, OpenAI Agent SDK, Deep Agents, Human-in-the-Loop, Supervisor Agents&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;- Azure AI Foundry Agents — SDK v2, Memory, Durable Orchestration, AI Gateway, observability with App Insights.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;Each skill is versioned, documented, and installable. The repo also includes an MCP server layer, for ai-dev-kit, so these capabilities can be reused across multiple workflows.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;But beyond the technical side, this project is a statement.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;We spend a lot of energy debating whether AI will replace developers. That's the wrong question. The right question is: are you using AI to multiply what you can build?&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;When I treat Claude as a peer — giving it context, structure, and clear objectives — I move faster, think more clearly, and ship better work. Not because I'm doing less, but because I'm doing more of&lt;/SPAN&gt; &lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;what actually matters.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The shift isn't about automation. It's about raising the floor of what one engineer can do.&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;SPAN&gt;The repo is open. If you're building on Databricks or Azure AI and want to skip the boilerplate, it might be worth a look.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;A href="https://github.com/alessandro9110/databricks-foundry-agent-skills" target="_blank"&gt;https://github.com/alessandro9110/databricks-foundry-agent-skills&lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Tue, 24 Mar 2026 08:54:10 GMT</pubDate>
      <guid>https://community.databricks.com/t5/community-articles/it-s-time-to-treat-ai-as-a-peer-not-a-tool-what-if-your-ai/m-p/151785#M1105</guid>
      <dc:creator>Ale_Armillotta</dc:creator>
      <dc:date>2026-03-24T08:54:10Z</dc:date>
    </item>
  </channel>
</rss>

