From a373f8ab40fe4e5c0c10b1dc3a5ee3fa048ff37c Mon Sep 17 00:00:00 2001 From: spm1001 Date: Sat, 18 Oct 2025 17:58:04 +0100 Subject: [PATCH] Clarify CLI vs MCP approach and context benefits --- examples/claude-code-skill/README.md | 11 +++++++++++ 1 file changed, 11 insertions(+) diff --git a/examples/claude-code-skill/README.md b/examples/claude-code-skill/README.md index db19d1e9..f1a5b617 100644 --- a/examples/claude-code-skill/README.md +++ b/examples/claude-code-skill/README.md @@ -122,6 +122,17 @@ You can use both together for the best experience: - Plugin for quick operations - Skill for intelligent workflow decisions +### Why CLI Instead of MCP? + +This skill teaches Claude to use the bd CLI directly (via Bash commands like `bd ready`, `bd create`, etc.) rather than relying on MCP tools. This approach has several benefits: + +- **Lower context usage** - No MCP server prompt loaded into every session, saving tokens +- **Works everywhere** - Only requires bd binary installed, no MCP server setup needed +- **Explicit operations** - All bd commands visible in conversation history for transparency +- **Full functionality** - CLI supports `--json` flag for programmatic parsing just like MCP + +The MCP server is excellent for interactive use, but for autonomous agent workflows where context efficiency matters, direct CLI usage is more practical. The skill provides the guidance Claude needs to use the CLI effectively. + ## Contributing Found ways to improve the skill? Contributions welcome! See [CONTRIBUTING.md](../../CONTRIBUTING.md) for guidelines.