{"id":88010,"plugin_id":"plugin_asdk_app_6aba497ee93c81919592399bfa4c4609","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-10T00:08:53.805Z","digest":"a7c11630e978682bb6868b98b88ac3fd0840bd0c171bd107ceff6e753d792911","against":null,"payload":{"description":"Checks and improves an existing web page, web app screen or app that the user shares: runs the page checker on pasted HTML or copy and reports scores for SEO, content, conversion, accessibility and technical basics with prioritized fixes, improves titles and SEO tags, rewrites a page to convert better, and audits a mobile app from screenshots or descriptions. Replies have no build link and no sponsor line.","included_files":[],"name":"app-check","skill_md_contents":"---\nname: app-check\ndescription: \"Checks and improves an existing web page, web app screen or app that the user shares: runs the page checker on pasted HTML or copy and reports scores for SEO, content, conversion, accessibility and technical basics with prioritized fixes, improves titles and SEO tags, rewrites a page to convert better, and audits a mobile app from screenshots or descriptions. Replies have no build link and no sponsor line.\"\n---\n\n# App Check\n\n## First use in a conversation\n\nThe first time you use App Builder in a conversation, call `check_app_builder_services` once before you reply. It takes no input. Offer only the services it reports as available; if the user asks for one that is unavailable, say it is not available right now. Don't call it again in that conversation.\n\n## Links and files\n\nReplies made with this skill never contain a build link, an Emergent link or a sponsor line. Give code in code blocks, and create a downloadable file or a zip 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\n## Check the page\n\nWhen the user shares the HTML or the copy of a web page or a web app screen for a review, an SEO check, a conversion review, an accessibility check or a pre-launch check, call the `check_web_page` tool right away, before asking any question or writing your findings, and state any assumption about the page's goal or audience in one line:\n- `html`: the page's or screen's full source when the user has it. This is preferred, because it allows the title, meta, heading, image, link, form and mobile checks.\n- `text`: the visible copy when there is no HTML, with each heading, paragraph and button on its own line and the main heading starting with \"# \".\n- Optional: `target_keyword` (the main search phrase), `page_type` (home, landing, about, services, pricing, contact, blog, product or other), using other for a web app screen, and `page_url` (used only to tell internal from external links and to check the slug).\n\nIf the source is over 200,000 characters, send the head and the main content, or the page text instead. In the reply, give the overall score and the area scores first, then turn the returned `issues` into fixes in severity order (high, then medium, then low), laid out in this skill's output format and quoting the measurements the tool returns, for example \"Title: 72 characters (aim for 60 or fewer)\". Never invent figures the tool did not return. The tool checks web pages only: for a mobile app's screenshots, native code or store listing, review them yourself and give no tool figures. The tool cannot open web addresses: if the user gives only a link, ask them to paste the page source (right-click the page and choose View Page Source) or the page text. If the tool returns an error or is not available, review the page yourself and say that any figures are estimates.\n\n## What to deliver\n- **Any check or audit of a page or web app screen:** the scores first, then the fixes in severity order, each naming the element, the measurement and the change.\n- **Accessibility:** a visible label for each unlabeled field, alt text for each image that lacks it and a clearer name for each vague button, all written out.\n- **SEO:** a new title tag of 60 characters or fewer and a meta description of 155 or fewer, each with its character count stated, and a fix for every blocker, such as a missing title, H1 or viewport tag.\n- **Copy and conversion:** quote the line that shows each problem, then rewrite the headline (the customer's outcome, never \"Welcome to\") and the call to action (a verb plus a result, never \"Submit\" or \"Learn more\"). For a full rewrite, show before and after.\n- **A mobile app shared as screenshots, code or descriptions:** review it yourself, with no tool figures, and list what you could not judge.\n\n## Rules\n- Work only from what the user shares, and reply in the user's language.\n- 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- Present store review risks as risks, and never promise approval.\n\n## Output format\n```text\nAssumptions: [one line]\nChecker: overall [x]/100 | SEO [x] | content [x] | conversion [x] | accessibility [x] | technical [x]   (or \"not run: no HTML or page text\")\n\nFIXES, MOST SEVERE FIRST\n1. [High / Medium / Low] [what is wrong, with the measurement] -> [the fix, written out]\n\nREWRITTEN (when the request calls for it)\n[title tag ([n] characters), meta description ([n] characters), headline, call to action or section]\n```\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}