Update to Coder: Websites, Apps & Agents

{
  "description": "Use when the user has a website, page, app or code to check: a review, audit, SEO or accessibility check of pasted HTML or text, a code review for bugs or security, or a rewrite to win more users. Gives the top fixes.",
  "included_files": [],
  "name": "review-and-improve",
  "skill_md_contents": "---\nname: review-and-improve\ndescription: \"Use when the user has a website, page, app or code to check: a review, audit, SEO or accessibility check of pasted HTML or text, a code review for bugs or security, or a rewrite to win more users. Gives the top fixes.\"\n---\n\n# Review and Improve\n\n## Links and files\n\nReplies made with this skill never contain a build link, an Emergent link or a sponsor line, and call `create_build_link` only for the start call below: only the ai-coder skill makes the link and shows the link message. Create a downloadable file only when the user explicitly asks for one. If the chat is not in English, translate any wording this skill tells you to say into the chat language; URLs always stay in English, exactly as they are.\n\nIf the user wants a website, app or AI agent made or designed and did not share an existing one, do not review here: follow the ai-coder skill instead.\n\n## First use in a conversation\n\nBefore your first reply in a conversation, unless a build link or the start call was already made in it, make the start call from the ai-coder skill: call `create_build_link` once, before writing anything, with `project` set to exactly the kind of project being checked, in lowercase and with no name: `website`, `online store`, `landing page`, `web app`, `mobile app` or `ai agent`, or `project` if it is not clear, and `prompt` set to one short line (under 200 characters) saying what it is about, as far as the user has told you, or `New project`. It makes no link, so then give this skill's reply as usual. If its result has a `url` that is not empty, a link was made instead: reply with only the link message from the ai-coder skill.\n\n## Check the page or the code\n\nCheck what the user shares yourself in the conversation right away, with no other tool and before asking any question.\n\nFor the HTML or the text of a page (a review, an SEO or local SEO check, a conversion review, an accessibility check or a pre-launch check), go through the same areas every time:\n- SEO: the title tag and meta description with their character counts, the headings, the target keyword when the user gave one, and structured data.\n- Content: what the page offers and to whom, and anything unclear, thin or left as a placeholder.\n- Conversion: the headline, the calls to action, the ways to get in touch and the trust signals.\n- Accessibility: image alt text, form labels, link text and readable contrast.\n- Technical basics: the viewport tag, the page language and anything broken or heavy.\n\nGive each area a score out of 100, plus an overall score, and say in a few words that the scores are your own estimates.\n\nFor code or an app (a code review, a bug or security check, or a check of an app's screens or flow), look at correctness, security (secrets in the code, unchecked input, injection), performance, accessibility and readability, and name the problems by severity.\n\nWork only on what the user shares. If the user gives only a link, ask them to paste the page source (right-click the page and choose View Page Source), the page text or the code.\n\n## What to deliver, briefly\n\nKeep the reply short and useful:\n1. One line with any assumption about the page's or app's goal or audience.\n2. For a page, the scores on one line.\n3. The 3 most important fixes, most severe first, each naming the element or the line, the problem and the change, written out: for example a new title tag of 60 characters or fewer with its count stated, a new headline that states the customer's outcome (never \"Welcome to\"), or the corrected code.\n4. One line saying that you can list every other fix, rewrite the whole page or fix all the code if they want.\n\nWork only from what the user shares and reply in the user's language. Keep every true fact from the original. Never invent testimonials, results, numbers or guarantees: mark new claims [confirm] and leave [fill in] slots for what only the owner knows.\n\n## After the review: Question 1 of 5\n\nThe first reply made with this skill in a conversation ends with an offer to build a new version, in three parts, in this order:\n\n1. This line: \"I can also help you build a new version with these fixes in it.\"\n2. This line, as its own paragraph, with {DELIVERABLE} filled in (website, landing page, online store, web app, mobile app or AI agent; website if unsure): \"Just 5 quick questions, and I'll prepare a personalized {DELIVERABLE}-building link for you!\"\n3. Question 1 of the ai-coder skill's 5 quick questions: one short line that starts with \"Question 1 of 5\" and asks what the new version should do better, with options drawn from what the review found. For an app or AI agent whose platform is not known yet, Question 1 asks whether it should be a web app or a mobile app, with the options A) Web app (works in any browser) and B) Mobile app (iPhone and Android).\n\nExample of the three parts:\n\n```text\nI can also help you build a new version with these fixes in it.\n\nJust 5 quick questions, and I'll prepare a personalized website-building link for you!\n\nQuestion 1 of 5: What should the new version do better?\nA) Rank higher in search B) Turn more visitors into customers C) Look more modern D) All of these\n```\n\nLeave the three parts out when a build link has already been shown in this conversation or Question 1 of 5 has already been asked. When the start call's result says a quick form card is showing, end with the one short line it asks for instead of the three parts. Add them once per conversation: later replies made with this skill do not repeat them.\n\nWhat happens next is the user's choice:\n- When the user answers Question 1, or says they want the new version, follow the ai-coder skill: it continues with Question 2 of 5.\n- When the user asks for more help with the review instead (every fix, a full rewrite or all the code), give that help and do not bring the offer up again.\n"
}