Client Finder - Bun + TypeScript Implementation

This document describes the Bun + TypeScript implementation of the client-finder skill.

Overview

The client-finder skill is implemented with Bun + TypeScript, providing:

• Type safety
• Modular structure
• Easier testing
• Robust error handling

Project Structure

client-finder/
├── src/
│   ├── index.ts         # Main entry point and orchestration logic
│   ├── expansion.ts     # Query expansion logic (LLM and rule-based)
│   ├── workflow.ts      # Workflow API calls
│   └── types.ts         # TypeScript type definitions
├── scripts/
│   ├── run.ts           # Bun CLI entry point
│   └── test.ts          # Test suite
├── package.json
├── SKILL.md
└── output_schema.json

Runtime Flow

1. @clawd/auth-runtime reads ~/.yuanwei/auth.json.
2. Start workflow: POST /ecom/cold-outreach/run-flow.
3. If the platform key is missing or rejected, stop with the centralized auth error.
4. Return accepted immediately.

Note: this skill does not pass webhook_url/webhook_token in body. Webhook config is resolved from the bound client by backend.

Run

bun run scripts/run.ts "office machine" "us"

Dry-run:

bun run scripts/run.ts "office machine" "us" --dry-run

Environment

• ~/.yuanwei/auth.json (required for live)
• QUERY_EXPANSION_JSON (optional)

Testing

Run unit-like checks:

bun run test

Notes

• Output must match output_schema.json.
• This skill is async fire-and-return: no local polling/finalize/hook emission.