<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Developers Digest - Progressive Disclosure</title>
    <link>https://www.developersdigest.tech/tags/progressive-disclosure</link>
    <description>3 items tagged Progressive Disclosure on Developers Digest - blog posts, tools, guides, and tutorials.</description>
    <language>en</language>
    <lastBuildDate>Thu, 02 Jul 2026 03:38:03 GMT</lastBuildDate>
    <atom:link href="https://www.developersdigest.tech/tags/progressive-disclosure/feed.xml" rel="self" type="application/rss+xml" />
    <image>
      <url>https://avatars.githubusercontent.com/u/124798203?v=4</url>
      <title>Developers Digest - Progressive Disclosure</title>
      <link>https://www.developersdigest.tech/tags/progressive-disclosure</link>
    </image>
    <item>
      <title><![CDATA[One Endpoint, Every Capability: A Reference Architecture for Progressive Disclosure]]></title>
      <link>https://www.developersdigest.tech/blog/one-endpoint-progressive-disclosure</link>
      <guid isPermaLink="true">https://www.developersdigest.tech/blog/one-endpoint-progressive-disclosure</guid>
      <description><![CDATA[Skills, files, memory, and generation do not need four integrations. They need one MCP endpoint with tiered disclosure, one API key that scopes everything to its owner, and one credit balance. The same tools answer to an MCP client, an in-product chat, and a CLI. Here is the whole architecture, and why it is the shape that makes a fleet of agents coherent.]]></description>
      <pubDate>Fri, 03 Jul 2026 00:00:00 GMT</pubDate>
      <category>MCP</category>
      <category>Agent Skills</category>
      <category>AI Agents</category>
      <category>Progressive Disclosure</category>
      <category>Coordinating AI Agents</category>
    </item>
    <item>
      <title><![CDATA[Linked Context: When a Skill Can Point at the Whole Web]]></title>
      <link>https://www.developersdigest.tech/blog/skill-studio-linked-context</link>
      <guid isPermaLink="true">https://www.developersdigest.tech/blog/skill-studio-linked-context</guid>
      <description><![CDATA[The first version of skills-over-MCP served a fixed first-party catalog. Skill Studio extends it two ways: anyone can author skills that ride the same progressive-disclosure endpoint scoped to their own API key, and a skill file can be a link instead of a copy - a URL whose bytes are only fetched at the moment an agent decides it needs them. Progressive disclosure stops at the skill boundary no longer. It runs out to the open web.]]></description>
      <pubDate>Thu, 02 Jul 2026 00:00:00 GMT</pubDate>
      <category>Agent Skills</category>
      <category>MCP</category>
      <category>AI Agents</category>
      <category>Progressive Disclosure</category>
      <category>Coordinating AI Agents</category>
    </item>
    <item>
      <title><![CDATA[Skills Delivered Over MCP: Why Progressive Disclosure Is the Missing Piece of Both Standards]]></title>
      <link>https://www.developersdigest.tech/blog/skills-over-mcp-progressive-disclosure</link>
      <guid isPermaLink="true">https://www.developersdigest.tech/blog/skills-over-mcp-progressive-disclosure</guid>
      <description><![CDATA[SKILL.md solved knowledge packaging with progressive disclosure. MCP solved capability transport but ships flat, context-hungry tool lists. The next shape combines them - an MCP server whose tools are a skill directory, so an agent pays context only for what the task needs. Here is the argument and a working implementation.]]></description>
      <pubDate>Wed, 01 Jul 2026 00:00:00 GMT</pubDate>
      <category>Agent Skills</category>
      <category>MCP</category>
      <category>AI Agents</category>
      <category>Progressive Disclosure</category>
      <category>Coordinating AI Agents</category>
    </item>
  </channel>
</rss>