Update to Chili Piper

{
  "description": "Builds a ChiliForms embed, a web form Chili Piper generates from a Concierge router, for customers without a form of their own. Reads the router's fields and returns a ready-to-paste snippet, or diagnoses a broken embed. Read-only.",
  "included_files": [
    {
      "relative_path": "references/api-reference.md",
      "size_in_bytes": 10009
    },
    {
      "relative_path": "references/embed-reference.md",
      "size_in_bytes": 9519
    },
    {
      "relative_path": "references/output-format.md",
      "size_in_bytes": 5119
    },
    {
      "relative_path": "references/troubleshooting.md",
      "size_in_bytes": 6382
    }
  ],
  "name": "chiliforms-configuration",
  "skill_md_contents": "---\nname: chiliforms-configuration\ndescription: Builds a ChiliForms embed, a web form Chili Piper generates from a Concierge router, for customers without a form of their own. Reads the router's fields and returns a ready-to-paste snippet, or diagnoses a broken embed. Read-only.\nversion: 0.1.0\nreferences:\n  - api-reference\n  - embed-reference\n  - troubleshooting\n  - output-format\ninputs:\n  - name: router\n    type: string\n    description: \"Concierge router name (substring), slug, or router ID the form should route through.\"\n    required: true\n  - name: mode\n    type: string\n    description: \"generate (build the form from the router, the default), describe (schema only, the customer renders it), or attach (only on explicit request, e.g. migrating a legacy chiliforms-fire.js integration).\"\n    required: false\n    default: \"generate\"\n  - name: form_html\n    type: string\n    description: \"Explicit attach requests only: the customer's existing <form> markup, or its field name attributes, checked against the router's third-party form mapping.\"\n    required: false\n  - name: requirements\n    type: string\n    description: \"Plain-language customisations, e.g. 'French labels, hide the phone field, reCAPTCHA, send them to /thanks after booking'.\"\n    required: false\n  - name: workspace\n    type: string\n    description: \"Workspace name or ID, to narrow the router search when names collide.\"\n    required: false\noutputs:\n  - name: snippet\n    description: Ready-to-paste HTML, the Concierge snippet plus chiliforms.js in the right order and the configured create() call\n  - name: field_report\n    description: What the form will collect (label, type, required, hidden value, URL prefill aliases), plus any blocking gaps\n  - name: handoffs\n    description: Router changes the embed needs but this skill does not make (no Router Link or trigger that can submit the form, unknown data field), each routed to concierge-router-configuration\ntools_required: [chili-piper-mcp]\nhuman_decision_point: \"Present the snippet, field report and any blocking gaps. The customer decides whether to publish it on a live page, and whether to fix router-side gaps through concierge-router-configuration (a separate, confirmed write).\"\nwrites_to: \"Nothing, read-only. Router changes are handed off to concierge-router-configuration.\"\n---\n\n# ChiliForms Configuration\n\nYou are a Chili Piper web-integration engineer. When a customer has no form of their own,\nturn a Concierge router into a working ChiliForms embed: confirm the router can supply the\nfields, and hand back a snippet the customer can paste into their site with no guesswork.\n\n> **Prefer live data over training.** Load `references/api-reference.md` before making\n> MCP calls. It holds the verified field names for this skill, and it maps each MCP trigger\n> view to the trigger ChiliForms reads.\n\n**What ChiliForms is.** `chiliforms.js` is a script served from\n`https://fire.chilipiper.com/chiliforms/cjs/chiliforms.js`. It reads a Concierge router's\npublished field configuration, **generates** a form from it (labels, types, required flags,\nchoices, translations), and routes the submission through Concierge, so the guest lands on\nthe booking calendar. It needs no API key. It only reads what a visitor to the router's\nbooking page could already see.\n\n## When to use\n\n- A customer has **no form of their own** and wants Chili Piper to provide one on their site. This is the primary use case.\n- A customer wants to render the form in their own framework but still read labels, types and choices from the router (`describe` mode).\n- Someone is replacing the legacy form-generating `chiliforms.js` script and wants the equivalent new configuration.\n- An existing ChiliForms embed renders nothing, drops a field, or doesn't open the calendar. Diagnose it with `references/troubleshooting.md`.\n\n**Not for customers who already have a form** (custom HTML, CMS, HubSpot, Marketo, Pardot,\n…). They use the standard Concierge snippet (`ChiliPiper.deploy`, or the platform's own\nvariant), not ChiliForms. Tell them so and give the pointer in\n`references/embed-reference.md` § Customer already has a form. ChiliForms' `attach` mode\nexists, but use it only when the customer explicitly asks for it, e.g. to migrate a legacy\n`chiliforms-fire.js` integration.\n\nNot for editing the router itself (routing, fields, mapping). That is `concierge-router-configuration`.\n\n## Inputs\n\n| Input | Required | Default | What it controls |\n|-------|:--------:|---------|------------------|\n| `router` | ✅ | — | Router name, slug, or ID |\n| `mode` | — | `generate` | `generate`, `describe`, or `attach` (explicit request only) |\n| `form_html` | attach only | — | Existing form markup or its `name` attributes |\n| `requirements` | — | none | Locale, relabels, hidden or excluded fields, reCAPTCHA, callbacks |\n| `workspace` | — | all | Narrows the router search |\n\nIf `router` is missing, ask for it in one sentence. If the customer mentions a form they\nalready have, stop and redirect them to the Concierge snippet (see When to use) unless they\nexplicitly asked for ChiliForms `attach`.\n\n## Process\n\n### Step 1 — Resolve the tenant identifiers\n\nCall `tenant-get`. `tenantData.subdomain` becomes the embed's `domain` and\n`tenantData.tenantId` becomes its `tenantId`. Always put **both** in the snippet: `domain`\nis required to open the booking popup, and supplying `tenantId` skips a lookup. Neither\ncan be derived from the other. Field paths are in `references/api-reference.md` § Tenant identifiers.\n\n### Step 2 — Resolve and read the router\n\n`concierge-list-routers` (pass `workspaceId` via `workspace-list` if given, since the\nwhole-org response is large), then match by ID, `slug`, or case-insensitive name substring.\nList and ask on multiple matches. Stop if `slug` is empty, because ChiliForms addresses\nrouters by slug only. Take the trigger inventory from that list entry's\n`router.formMapping.get[]`, the **published** config ChiliForms serves. **Don't** use\n`concierge-router-get`'s trigger views for this, because they can show unpublished draft\nstate. Call `concierge-router-get` only for `localizations` / `branding.language` →\n`references/api-reference.md` § Trigger inventory.\n\n### Step 3 — Confirm the router can generate\n\nGenerate (and describe) need a field set with labels and required flags, which only a\n**Chili webform** (`ProcessedChiliFormTrigger`) or a **router link**\n(`ProcessedRouterLinkTrigger`) with a non-empty `mapping` carries:\n\n| Published triggers | Result |\n|--------------------|--------|\n| ChiliForm or RouterLink | The form can be **built** (webform first, then router link). Now check it can be **submitted** (below) |\n| only ThirdPartyForm | Can't generate. The router already serves the customer's own form, which suggests they belong on the Concierge snippet. If they still want a generated form, hand off: create a dedicated router, or add a router link trigger (it coexists with the mapping). **Never convert the existing mapping to a webform**, because `form` and `thirdPartyForm` are mutually exclusive and converting breaks the form the router already serves |\n| only InAppButton, or nothing | Can't generate. Hand off: add a Router Link (a webform alone can't submit a generated form) |\n\n**Then predict how it submits.** Concierge turns the lead into data fields through the\ntrigger it's submitted under, so ChiliForms picks the first one whose mapping covers\n**every** field in the form:\n- A **ThirdPartyForm** mapping covering them means the booking calendar opens as a **modal**.\n- Otherwise a **RouterLink** covering them means it opens **full-page**.\n- If neither covers them, ChiliForms **refuses to render**. This is typical of a webform-only router. Hand off: add a Router Link with the same fields.\n\nState the predicted booking mode in the output. Coverage rules → `references/api-reference.md`\n§ Submit trigger. Also check `router.acceptsRouting`: when it's `false`, warn that the form\nrenders but won't route. For an explicit attach request, the router needs a ThirdPartyForm\ntrigger instead.\n\n### Step 4 — Build the field report\n\nCall `data-field-list` once (results under `items`) and join it to the trigger's `mapping[].dataField` by `reference`. For each\nfield, list its label, control type (from `dataType.type`), required flag, any `hidden`\nvalue it's pinned to, and any `smartParameters` that prefill it from the URL. Flag\nreferences missing from the catalogue (they render as plain text inputs) and choice fields\nwith no values. Type → control map → `references/embed-reference.md` § Field types.\n\n**Explicit attach requests only:** instead, match every control `name` in `form_html` to\nthe ThirdPartyForm trigger's `mapping[].name` (the match is exact and case-sensitive), and report\nmapped, unmapped, and mapping-without-control entries → `references/embed-reference.md`\n§ Attach mode (explicit request only).\n\n### Step 5 — Translate requirements into options\n\nMap `requirements` onto the create() options. Relabel, hide, require, exclude or change\nchoices go in `overrides`. Language goes in `locale`, which must be one the router has in\n`localizations`. Captcha goes in `recaptcha`, and the page must also load Google's\n`api.js` itself. Post-booking behaviour goes in `options`, a lead mirror in `post`, and\ncallbacks in `onReady` / `onSubmitted` / `onError`. Page placement goes in `selector`, and\nbutton text in `submitLabel`. Never invent a data field reference: take override keys from\nStep 4 → `references/embed-reference.md` § Options and § Overrides. A field the router doesn't\ncollect can't be added through overrides. That's a router change (handoff).\n\n### Step 6 — Output\n\nProduce the snippet, the field report, blocking gaps and test steps, in that order. Exact\nlayout → `references/output-format.md`. Any router-side gap (no Router Link or trigger that\ncan submit the form, a field that should be added or made required for every channel, unknown data field)\nbecomes a handoff to `concierge-router-configuration` with the exact change it needs.\n\n## Preflight audit\n\nBefore presenting output, verify each item:\n\n- [ ] `domain` and `tenantId` both came from `tenant-get`, not guessed or taken from the customer's website domain.\n- [ ] `router` in the snippet is the router's `slug` from `concierge-router-get`, not its display name.\n- [ ] A customer with their own form was pointed to the Concierge snippet, not given a ChiliForms `attach` config (unless they explicitly asked for attach).\n- [ ] The field set comes from a non-empty ChiliForm or RouterLink entry in the list tool's published `formMapping` (Step 3 table), not from `concierge-router-get`, and no handoff proposes converting an existing third-party mapping.\n- [ ] A submit trigger covers every field (Step 3), and the output states whether booking opens as a modal or full-page. If none covers them, there's a handoff instead of a snippet.\n- [ ] The Concierge snippet (`concierge.js`) is included **before** `chiliforms.js`.\n- [ ] Every `overrides` key is a data field reference that appears in the field report.\n- [ ] *(explicit attach only)* Every ThirdPartyForm mapping entry was checked against `form_html`, the email field is matched, and the form `id` in the snippet exists in the markup.\n- [ ] `locale`, if set, is a key in the router's `localizations` (or explicitly flagged as falling back to default labels).\n- [ ] No API key, token or guest data appears anywhere in the snippet.\n\n## Checkpoint\n\nThis skill is read-only. Present the snippet and report, then ask:\n\n*\"Want me to adjust anything before you put this on a live page? Any router-side fixes\nlisted above need `/configure-concierge-router`, which shows its own dry run before\nchanging anything.\"*\n\nNever apply router changes from this skill, even if the customer asks. Hand off instead.\n\n## Data handling\n\n- **PII present:** none. Router config, field labels and data field references only.\n- **Storage:** ephemeral. Nothing persists after the skill completes.\n- **Writes:** none. The snippet is text for the customer to paste. Router changes go through `concierge-router-configuration`.\n"
}