Goal Reference
This issue was generated from .fleet/goals/sdk-examples.md. The worker agent should read this file for full context including verification commands, constraints, and structural guidance.
Objective
Implement Tier 3 Agent CLI tools (stitch-cli, html-to-email) and a Tier 4 MCP Server wrapper (mcp-server) to expose Stitch SDK operations for agents with optimized ergonomics, --json support, and compound API wrapping.
Code-Level Diagnosis
Code path: packages/sdk/examples/
Mechanism: The SDK currently offers basic raw programmatic usage but lacks robust CLI wrappers designed with agent-first ergonomics (e.g., JSON schema introspection, JSON output) and an advanced compound MCP server wrapper.
Root cause: Native capabilities for LLM-driven execution via tailored CLIs and compound MCP tools are missing.
Current Implementation
// Missing agent-first CLIs and advanced MCP wrapper examples
Proposed Implementation
Files to modify: Create directories and implementation files for stitch-cli, html-to-email, and mcp-server. Each requires a SKILL.md for discoverability, actual implementation scripts, and a README.md defining their use cases and prerequisites.
Integration (Before -> After)
+ // Agent CLI examples and compound MCP server wrapping logic incorporated to improve LLM compatibility
Test Scenarios
- CLI structural validation: The
cli.ts implementation utilizes arguments for JSON output and structured execution logic.
- MCP Server syntax check: The MCP wrapper properly composes underlying Stitch capabilities.
Target Files
- packages/sdk/examples/stitch-cli/SKILL.md
- packages/sdk/examples/stitch-cli/src/cli.ts
- packages/sdk/examples/stitch-cli/README.md
- packages/sdk/examples/html-to-email/SKILL.md
- packages/sdk/examples/html-to-email/README.md
- packages/sdk/examples/mcp-server/SKILL.md
- packages/sdk/examples/mcp-server/README.md
- packages/sdk/README.md
Boundary Rules
Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.
Fleet Context
Goal Reference
This issue was generated from
.fleet/goals/sdk-examples.md. The worker agent should read this file for full context including verification commands, constraints, and structural guidance.Objective
Implement Tier 3 Agent CLI tools (
stitch-cli,html-to-email) and a Tier 4 MCP Server wrapper (mcp-server) to expose Stitch SDK operations for agents with optimized ergonomics,--jsonsupport, and compound API wrapping.Code-Level Diagnosis
Code path:
packages/sdk/examples/Mechanism: The SDK currently offers basic raw programmatic usage but lacks robust CLI wrappers designed with agent-first ergonomics (e.g., JSON schema introspection, JSON output) and an advanced compound MCP server wrapper.
Root cause: Native capabilities for LLM-driven execution via tailored CLIs and compound MCP tools are missing.
Current Implementation
// Missing agent-first CLIs and advanced MCP wrapper examplesProposed Implementation
Files to modify: Create directories and implementation files for
stitch-cli,html-to-email, andmcp-server. Each requires aSKILL.mdfor discoverability, actual implementation scripts, and aREADME.mddefining their use cases and prerequisites.Integration (Before -> After)
+ // Agent CLI examples and compound MCP server wrapping logic incorporated to improve LLM compatibilityTest Scenarios
cli.tsimplementation utilizes arguments for JSON output and structured execution logic.Target Files
Boundary Rules
Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.
Fleet Context
jules:session:13642316243044202608