merchant-skill-generator

# Merchant Skill Generator Turn merchant materials into a maintainable, deployable AI interface. Do not ask the merchant to understand MCP, schemas, command arguments, or build logs. ## Main Workflow 1. Decide whether this is a new Skill or an update to an existing generated repository. 2. Accept the materials already available: conversation text, URLs, images, PDFs, documents, menus, service lists, or repository files. 3. Extract candidate facts with available browsing, image, and document tools. If a tool is unavailable, ask for only the missing blocking material. 4. Select a preset and capability modules. Use `general_local` when no industry preset fits. 5. Present a merchant-readable summary with four groups: confirmed, needs confirmation, optional gaps, and blockers. Preserve sources and uncertainty. 6. Ask exactly one blocking question at a time. 7. Before generation, show the final facts and declaration wording. Wait for explicit merchant or authorized-operator confirmation. 8. Build the internal MerchantSpec, generate or safely update the repository, run validation, and produce the CloudBase upload package. 9. Guide the merchant through the three required CloudBase actions: create the Node.js HTTP service, upload the zip, and copy the public root URL. 10. When the URL is returned, run finalize, remotely verify `/health` and MCP initialize/tools, then return the installable Skill zip, MCP URL, repository URL, and promotion copy. Do not expose internal JSON, tool parameters, raw extracted payloads, or build logs unless the user explicitly asks for technical debugging details. ## Release Gates - Never invent prices, inventory, availability, business hours, promotion validity, or official status. - Public wording may say “资料由商家或授权运营者确认”. It must not claim platform verification. - Base mode has no user account, payment, real order, reservation success, refund, or fulfillment operation. - `build_action_draft` always creates a draft only. - Connected write operations require a real adapter, environment-only credentials, explicit merchant enablement, and passing tests. Do not simulate them. - For an update, preserve unknown files. If a generated file was manually changed, stop and return the conflict report instead of overwriting it. - Do not auto-login to CloudBase, call Tencent Cloud APIs, hold cloud credentials, or deploy on the merchant's behalf. ## Resources - Intake and confirmation: [references/intake-workflow.md](references/intake-workflow.md) - Presets, schema migration, and capabilities: [references/capabilities.md](references/capabilities.md) - Update safety: [references/update-workflow.md](references/update-workflow.md) - CloudBase packaging and finalization: [references/deployment.md](references/deployment.md) - Data, declaration, and transaction boundaries: [references/safety-boundaries.md](references/safety-boundaries.md) - Optional real-time and transaction connector contract: [references/connectors.md](references/connectors.md) ## Commands Create: ```bash npm run generate -- --spec /absolute/path/to/spec.json --out /absolute/path/to/output ``` Update: ```bash npm run generate -- --spec /absolute/path/to/spec.json --update /absolute/path/to/existing-skill ``` Validate before handoff: ```bash npm run validate ``` The final release is blocked until automated validation and isolated forward tests pass.