Update to App Builder

{
  "description": "Writes SEO blog posts for a website: outline, full article, opening hook, headings, title tag, meta description, URL slug and internal-link ideas, in the brand's voice. Use when the user wants an article or blog post for their site.",
  "included_files": [],
  "name": "blog-posts",
  "skill_md_contents": "---\nname: blog-posts\ndescription: \"Writes SEO blog posts for a website: outline, full article, opening hook, headings, title tag, meta description, URL slug and internal-link ideas, in the brand's voice. Use when the user wants an article or blog post for their site.\"\n---\n\n# Blog Post Writer\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## Purpose\n\nWrite blog posts that answer a real search, help the reader and lead them to the business's service: an outline, the full article and the SEO pieces (title tag, meta description, slug, internal links, image idea and alt text), in the brand's voice. For owners, marketers and freelancers who need posts ready to publish.\n\n## Before you start\n\nConfirm or infer four things and state them in one line at the top of the reply:\n\n- Topic and primary keyword: the phrase a searcher would type (\"how often to service a boiler\").\n- Reader: who they are and what they already know.\n- Goal: traffic, trust or leads, and the service page the post should send readers to.\n- Voice: mirror any site copy the user shares; otherwise a friendly expert talking to \"you\".\n\nAsk at most 2 questions, never before checking a pasted draft, only when the answer changes the post (usually which service to promote, or the region for prices and spelling). Write in the user's language.\n\n## Match the search intent\n\n| Query looks like | Write it as |\n|---|---|\n| how to [task] | Numbered steps, what you need, common mistakes |\n| what is [thing] | Definition in the first 2 sentences, then depth and examples |\n| [thing] cost or price | What drives the price; any figure marked [verify] |\n| [A] vs [B] | Comparison table plus \"choose A if, choose B if\" |\n| best [X] for [Y] | Selection criteria, the options, then a recommendation |\n\n## Outline first\n\n- One H1: the article title (it can be warmer and longer than the title tag).\n- 5 to 8 H2s, each noted with the reader question it answers. An H2 that answers no real question gets cut.\n- H3s only for steps or options inside an H2.\n- If the user asked only for an outline, stop there and offer to write the article.\n\n## Writing rules\n\n- Hook intro of 80 words or fewer: name the reader's problem, promise what the post delivers, then begin. Never open with \"In today's world\", \"In today's fast-paced digital landscape\", \"Are you looking for\" or \"In this article we will\".\n  - Weak: \"In today's world, boilers are an essential part of every home.\"\n  - Strong: \"Your boiler is banging and you want to know if it is dangerous. Here is what that noise usually means, what you can safely check yourself and when to call an engineer.\"\n- Default length 900 to 1,400 words unless the user asks otherwise.\n- Paragraphs of 1 to 3 sentences. Open each section with its answer, then explain.\n- Bullets only for truly list-like content (steps, options, checklists); tables for comparisons.\n- A concrete example in every section. Where the owner's own experience would build trust, add a [fill in: a real example from your work] slot.\n- Facts and statistics only if well known; anything else gets [verify]. Never invent studies, quotes, prices or customer stories; business details get [confirm].\n- Health, legal and money topics: note that a qualified professional should review the post.\n- Conclusion: 2 to 3 sentences with the key takeaway, then a CTA linking to the relevant service page with descriptive anchor text. Never \"In conclusion\".\n\n## SEO pieces\n\n- Primary keyword in the title tag, H1, first 100 words, one H2 where natural, the slug and the meta description. Use variants elsewhere; never stuff.\n- Title tag: 60 characters or fewer, keyword near the front, brand at the end if it fits.\n- Meta description: 155 characters or fewer, a clear benefit plus a reason to click.\n- Slug: lowercase words joined by hyphens, 3 to 5 words, no dates (/blog/boiler-service-frequency).\n- Count the characters of the title tag and meta description and state the counts.\n- 3 internal-link suggestions: anchor text, target page, where in the post.\n- 1 image idea with alt text of 125 characters or fewer.\n\n## Improving a pasted draft\n\nWhen the user pastes a draft, run the page checker as described in Check the page above, sending the draft as html if it is HTML, otherwise as text, with page_type blog and the primary keyword as target_keyword. Fix what it reports in priority order, then return the improved post and 3 to 5 bullets on what changed.\n\n## Output format\n\n```text\nAssumptions: [topic | primary keyword | reader | goal]\nChecker (only when a draft was pasted): overall [x]/100 | top issues fixed: [...]\n\nSEO\nTitle tag ([N] characters): [...]\nMeta description ([N] characters): [...]\nSlug: /blog/[...]\n\nOUTLINE\nH1: [...]\nH2: [...] (answers: [...])\n\nARTICLE\n[Full post in Markdown: # H1, hook intro, ## H2 sections, conclusion with CTA]\n\nINTERNAL LINKS\n1. \"[anchor text]\" -> [/page] (in section: [...])\n2. [...]\n3. [...]\n\nIMAGE\nIdea: [...]\nAlt text: [...]\n```\n\n## Quality checks\n\n- The intro is 80 words or fewer and opens with a hook, not a cliche.\n- One H1 and 5 to 8 H2s, each answering a real reader question.\n- 900 to 1,400 words unless the user asked otherwise; paragraphs of 1 to 3 sentences.\n- Keyword placed in title tag, H1, first 100 words, slug and meta, and it reads naturally.\n- Title tag and meta description within limits, with counts shown.\n- No invented facts, statistics, quotes or stories; [verify] and [confirm] used where needed.\n- The conclusion links to the service page; 3 internal links and 1 image idea included.\n- The voice matches the brand and the user's language.\n\n## Next step\n\nOffer to write the next post in the same topic cluster, or website-seo to tune the page it links to.\n"
}