[Fleet Execution] Add Tier 3 Agent CLI Tool Examples

[jules-fleet]

Objective

Create Tier 3 Agent CLI examples that wrap the Stitch SDK into ergonomic tools (stitch-cli, html-to-email) intended for programmatic invocation, complete with schema introspection and --json outputs.

Code-Level Diagnosis

Code path: packages/sdk/examples/
Mechanism: The packages/sdk/examples/ directory lacks dedicated CLI wrappers using --json parameters.
Root cause: Absence of canonical tools optimized for agent frameworks interacting via shell execution instead of SDK integration.

Current Implementation

// Missing Agent CLI examples

Proposed Implementation

Files to modify: Scaffold the Stitch CLI and HTML-to-Email Agent CLI projects, including source code, READMEs, and SKILL.md files.

Integration (Before -> After)

+ 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

Test Scenarios

1. Stitch CLI: Execute bun src/cli.ts generate --json '{"prompt": "A button"}' -> Outputs structured JSON containing screen ID and HTML URL.

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

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

• Source: jules:session:13713548963527251485
• Link: https://jules.google.com/session/13713548963527251485