@cursor/bdk 0.2.16 → 0.2.18

package/dist/docs/assets/{building-with-agents.md.Bi9CQ-bR.js → building-with-agents.md.FZXrY8Nk.js}

@@ -1,4 +1,4 @@
-import{_ as t,c as a,o as n,a3 as i}from"./chunks/framework.BNw1pucY.js";const u=JSON.parse('{"title":"Build with a coding agent","description":"Delegate BDK creation, capability work, verification, and measured improvement to a coding agent.","frontmatter":{"title":"Build with a coding agent","description":"Delegate BDK creation, capability work, verification, and measured improvement to a coding agent."},"headers":[],"relativePath":"building-with-agents.md","filePath":"building-with-agents.md"}'),o={name:"building-with-agents.md"};function s(r,e,l,c,d,p){return n(),a("div",null,[...e[0]||(e[0]=[i(`<h1 id="build-with-a-coding-agent" tabindex="-1">Build with a coding agent <a class="header-anchor" href="#build-with-a-coding-agent" aria-label="Permalink to &quot;Build with a coding agent&quot;">​</a></h1><p>Grok Bot Development Kit (BDK) projects live in files and expose structured CLI commands, so a coding agent can create the project, exercise its tools, run a real turn, and inspect the result. You approve the plan and side effects while the coding agent owns the implementation loop.</p><p>This page covers a coding agent working inside a checkout. To let a running agent propose changes to its own source, use the separate <a href="./guides/improve.html">self-improvement extension</a>.</p><h2 id="create-an-agent-from-a-goal" tabindex="-1">Create an agent from a goal <a class="header-anchor" href="#create-an-agent-from-a-goal" aria-label="Permalink to &quot;Create an agent from a goal&quot;">​</a></h2><p>Give the coding agent a purpose and the surfaces people will use. The <code>create-agent</code> skill asks only for missing decisions, shows a file plan, then scaffolds and verifies a small first version.</p><blockquote><p>Use the BDK create-agent skill to build a PR triage agent reachable through GitHub. It should summarize failed checks, post one review comment per pull request, and include one smoke eval.</p></blockquote><p>Ask it to read <a href="./../skills/create-agent/SKILL.html"><code>skills/create-agent/SKILL.md</code></a>. The first version should stay narrow: instructions, one or two tools, the chosen channels or connections, and a smoke eval.</p><h2 id="add-one-capability" tabindex="-1">Add one capability <a class="header-anchor" href="#add-one-capability" aria-label="Permalink to &quot;Add one capability&quot;">​</a></h2><p>For an existing project, name the user-visible outcome and point the coding agent at the matching procedure. It should inspect the current agent first, make the smallest change, then exercise the new path.</p><p>Examples:</p><blockquote><p>Add Slack mentions and DMs to this agent. Follow the setup-slack skill, keep replies in the source thread, and verify one local mention.</p></blockquote><blockquote><p>Connect the private inventory MCP server with host OAuth. Keep its write tools behind a narrow server-tool wrapper.</p></blockquote><blockquote><p>Add a GitHub ready-for-review trigger and replay PR 42 before posting anything live.</p></blockquote><p>The companion skills live under <code>skills/</code>: <a href="./../skills/setup-slack/SKILL.html">Slack</a>, <a href="./../skills/mcp-auth/SKILL.html">MCP OAuth</a>, and <a href="./../skills/github/SKILL.html">GitHub</a>. Use the capability guide for the reader experience and the skill for the coding procedure.</p><h2 id="verify-tools-before-tuning-the-prompt" tabindex="-1">Verify tools before tuning the prompt <a class="header-anchor" href="#verify-tools-before-tuning-the-prompt" aria-label="Permalink to &quot;Verify tools before tuning the prompt&quot;">​</a></h2><p>Start with discovery, then call deterministic server tools without a model turn. If a tool returns the wrong evidence, fix the tool before changing instructions.</p><div class="language-text vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">text</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span>bdk validate --dir .</span></span>
+import{_ as t,c as a,o as n,a3 as i}from"./chunks/framework.BNw1pucY.js";const u=JSON.parse('{"title":"Build with a coding agent","description":"Delegate BDK creation, capability work, verification, and measured improvement to a coding agent.","frontmatter":{"title":"Build with a coding agent","description":"Delegate BDK creation, capability work, verification, and measured improvement to a coding agent."},"headers":[],"relativePath":"building-with-agents.md","filePath":"building-with-agents.md"}'),o={name:"building-with-agents.md"};function s(r,e,l,c,d,p){return n(),a("div",null,[...e[0]||(e[0]=[i(`<h1 id="build-with-a-coding-agent" tabindex="-1">Build with a coding agent <a class="header-anchor" href="#build-with-a-coding-agent" aria-label="Permalink to &quot;Build with a coding agent&quot;">​</a></h1><p>Bot Development Kit (BDK) projects live in files and expose structured CLI commands. A coding agent can create the project, exercise its tools, run a real turn, and inspect the result. You approve the plan and side effects while the coding agent owns the edit-and-test loop.</p><p>This page covers a coding agent working inside a checkout. To let a running agent propose changes to its own source, use the separate <a href="./guides/improve.html">self-improvement extension</a>.</p><h2 id="create-an-agent-from-a-goal" tabindex="-1">Create an agent from a goal <a class="header-anchor" href="#create-an-agent-from-a-goal" aria-label="Permalink to &quot;Create an agent from a goal&quot;">​</a></h2><p>Give the coding agent a purpose and the surfaces people will use. The <code>create-agent</code> skill asks only for missing decisions, shows a file plan, then scaffolds and verifies a small first version.</p><blockquote><p>Use the BDK create-agent skill to build a PR triage agent reachable through GitHub. It should summarize failed checks, post one review comment per pull request, and include one smoke eval.</p></blockquote><p>Ask it to read <a href="./../skills/create-agent/SKILL.html"><code>skills/create-agent/SKILL.md</code></a>. The first version should stay narrow: instructions, one or two tools, the chosen channels or connections, and a smoke eval.</p><h2 id="add-one-capability" tabindex="-1">Add one capability <a class="header-anchor" href="#add-one-capability" aria-label="Permalink to &quot;Add one capability&quot;">​</a></h2><p>For an existing project, name the user-visible outcome and point the coding agent at the matching procedure. It should inspect the current agent first, make the smallest change, then exercise the new path.</p><p>Examples:</p><blockquote><p>Add Slack mentions and DMs to this agent. Follow the setup-slack skill, keep replies in the source thread, and verify one local mention.</p></blockquote><blockquote><p>Connect the private inventory MCP server with host OAuth. Keep its write tools behind a narrow server-tool wrapper.</p></blockquote><blockquote><p>Add a GitHub ready-for-review trigger and replay PR 42 before posting anything live.</p></blockquote><p>The companion skills live under <code>skills/</code>: <a href="./../skills/setup-slack/SKILL.html">Slack</a>, <a href="./../skills/mcp-auth/SKILL.html">MCP OAuth</a>, and <a href="./../skills/github/SKILL.html">GitHub</a>. Use the capability guide for the reader experience and the skill for the coding procedure.</p><h2 id="verify-tools-before-tuning-the-prompt" tabindex="-1">Verify tools before tuning the prompt <a class="header-anchor" href="#verify-tools-before-tuning-the-prompt" aria-label="Permalink to &quot;Verify tools before tuning the prompt&quot;">​</a></h2><p>Start with discovery, then call deterministic server tools without a model turn. If a tool returns the wrong evidence, fix the tool before changing instructions.</p><div class="language-text vp-adaptive-theme"><button title="Copy Code" class="copy"></button><span class="lang">text</span><pre class="shiki shiki-themes github-light github-dark vp-code" tabindex="0"><code><span class="line"><span>bdk validate --dir .</span></span>
 <span class="line"><span>bdk info --dir . --json</span></span>
 <span class="line"><span></span></span>
 <span class="line"><span>bdk call inspect_pr --dir . \\</span></span>