Update to Reuily

{
  "description": "Create, revise, publish, share or unpublish a Reuily form, survey, questionnaire or quiz (feedback, NPS, registration, RSVP, intake, application, lead screening, booking, consent with signature) using the Reuily tools.",
  "included_files": [],
  "name": "build-reuily-form",
  "skill_md_contents": "---\nname: build-reuily-form\ndescription: Create, revise, publish, share or unpublish a Reuily form, survey, questionnaire or quiz (feedback, NPS, registration, RSVP, intake, application, lead screening, booking, consent with signature) using the Reuily tools.\n---\n\n# Build a Reuily form\n\nReuily forms are conversational: usually one question per page, with optional\nbranching between pages. Use this workflow whenever the user wants a real,\nshareable form rather than a list of questions in chat.\n\n## Create\n\n1. If the request is vague, ask at most one or two clarifying questions (who\n   fills it in, what decision the answers support). Otherwise just build it.\n2. If the user mentions a common use case and wants a head start, you may call\n   `list_templates` and offer a match; use `create_form_from_template` only if\n   they pick one.\n3. Otherwise call `create_form`:\n   - `request`: the user's request in their own words, including every question,\n     option, branch and style they asked for. Reuily checks the form covers it.\n   - `form`: the complete design, following the page catalog and rules in the\n     tool description. Use the matching page template per question (nps for\n     recommendation, rating for stars, contact-info for grouped contact fields).\n   - **Quiz:** set `formKind: \"quiz\"` and give every scored question its\n     `quizAnswers` (option values). Add `settings.quiz.passPercent` only when\n     the user named a pass mark, and keep the pass mark in `request`: Reuily\n     drops one the request doesn't mention. Reuily adds pass and fail endings\n     for a pass mark; for the user's own copy, put thank-you pages after the\n     default one with `quizEnding` `{kind: \"passed\"}` or `{kind: \"failed\"}`,\n     or `{kind: \"range\", min, max}` for a score band.\n   - **Lead screening:** set `formKind: \"lead\"` and ask 4–6 qualifying choice\n     or number questions on what separates good customers (need, budget,\n     timeline, fit, authority), then name, email and phone if a call follows.\n     Tag each qualifying question (Reuily refuses a lead form with fewer than\n     3 tagged, or with most choice and number questions neither tagged nor\n     `leadSkip`; when the user listed the questions, theirs are enough. A lead\n     form of only the contact fields the user listed is saved as a plain form):\n     `leadTags` `{optionValue: \"good\" | \"no_fit\"}` on choices, leaving answers that are neither untagged (neutral: they rule\n     nobody out but don't count toward hot). On numbers or\n     ratings use `leadRule`: `goodMin` when more is better or `goodMax` when\n     fewer is better, and `noFitMax` or `noFitMin` for numbers that rule\n     someone out. One `no_fit` answer rules a person out whatever else they\n     answer, so keep it for real deal-breakers; doubt, early research or a\n     shared decision is never one, and Reuily clears such tags unless the\n     request rules those people out. Set `leadMustHave: true` on at\n     most one question whose good answer a hot lead needs (such as a required\n     budget), and `leadSkip: true` on choice or number questions that don't\n     affect the lead. Set `settings.lead.picky` (`relaxed`, `normal`, `picky`)\n     only when the user says how strict to be, and `settings.lead.stopEarly`\n     or `bookingHotOnly` only if asked (say so in `request`: Reuily drops an\n     early stop the request doesn't mention). For a different message or link\n     per fit, put thank-you pages after the default one with `leadEnding`\n     (`hot`, `warm`, `no_fit`); don't route to them, Reuily picks the ending\n     from the lead's level.\n   - **Look:** `themeSelection.presetId` picks a gallery theme that fits the\n     form. If the user gives brand colours or asks to recolour something\n     (\"green buttons\"), keep a fitting preset and add `colors` with `#RRGGBB`\n     values for just those parts: `formBgColor`, `textColor`, `headingColor`,\n     `fieldLabelColor`, `descriptionColor`, `buttonColor`, `buttonTextColor`,\n     `inputBgColor`, `inputBorderColor`, `cardBgColor`. Never guess brand\n     colours.\n   - **Logo and images:** `logo: {url, placement, size}` shows a logo on every\n     page (placement `top-start`, `top-center`, `top-end` or a `bottom-`\n     corner; size `small`, `medium`, `large`). A page takes\n     `branding: {backgroundImage, layout, backgroundSize}` for a cover or\n     background, and questions and choice options take `imageUrl`. Use only\n     HTTPS image links the user gave you or that you found, such as the logo\n     on their website; Reuily refuses links that aren't images.\n   - **Kiosk mode:** when the form runs on one shared screen used by person\n     after person (a tablet at a booth, front desk or event check in), set\n     `settings.kioskMode: true`. After each response the form starts over at\n     its first page. If the result says kiosk mode isn't available on the\n     plan, tell the user the form works as normal; don't suggest upgrading.\n4. If the tool returns validation problems, fix exactly those and call it again.\n5. Reply with a short outline of the form and the `edit_url`. Mention any\n   `automatic_fixes` that change what the user asked for.\n\nThe form is saved as an unpublished draft. Do not publish it in the same turn\nunless the user explicitly asked for it to go live.\n\n## Revise\n\n- For a draft created in this conversation, call `get_form`, edit its `form`\n  object, and send the whole result to `update_draft_form`, keeping each\n  ending's `leadEnding` or `quizEnding`, and the `logo`. Include\n  `themeSelection` or `colors` only if the user asked for a different look;\n  `get_form` returns the current theme and colours in `style`. To hide the\n  logo, send `logo: {show: false}`.\n- `update_draft_form` refuses published forms and forms with responses so\n  collected answers stay consistent. In that case explain why and give the\n  `edit_url` so the user can change it in the Reuily builder.\n\n## Publish or unpublish\n\n- Call `publish_form` only after the user clearly asks to publish, share or go\n  live. Then give them the `public_url`.\n- If `publish_form` says a lead form has questions that aren't tagged, name\n  them. Tag them, or set `leadSkip` on ones that don't affect the lead, with\n  `update_draft_form`. Only if the user agrees their answers shouldn't count,\n  call `publish_form` again with `allow_untagged: true`.\n- If they will share it in several places, offer one link per place so Reuily\n  can report where responses came from: append `utm_source` (for example\n  `instagram`, `newsletter`), optionally `utm_campaign` and `utm_medium`, or\n  `ref` for a person or partner, to the `public_url`, e.g.\n  `<public_url>?utm_source=instagram&utm_campaign=spring`. Use lowercase,\n  hyphenated values and never put personal data in a link.\n- `unpublish_form` stops new responses and keeps existing ones.\n- For a readable link like `reuily.com/@team/spring-survey`, use `set_form_link`\n  when the user asks for a custom link. If the form already had a custom link,\n  say the old one will stop working. If it says custom links aren't available\n  on the plan, tell the user the form keeps its standard link; don't suggest\n  upgrading.\n- `update_form_settings` changes kiosk mode (`kiosk_mode`, and\n  `kiosk_restart_seconds` from 5 to 20), whether the form accepts responses,\n  its closing date (`closes_at`), response limit (`submission_limit`) and the\n  message people see once it's closed. It works on published forms too.\n  Confirm before closing a form or setting a limit, since both stop new\n  responses. `get_form` shows the current settings.\n- Integrations (Google Sheets, Slack, Discord, webhooks) and notification settings are set up\n  in the Reuily app from the form's `edit_url`; they aren't available here.\n\n## Rules\n\n- Never invent form IDs, links or content: get them from tool results.\n- Do not ask for or accept passwords, payment card numbers or government IDs as\n  form questions unless the user insists and understands the sensitivity.\n- If a tool says the user's role or plan does not allow an action, say so\n  plainly. Do not try other tools to get around it.\n"
}