Update to Glippy GEO

{
  "description": "Check whether a site publishes an llms.txt and draft or improve one in the llmstxt.org format, while being honest that major AI models do not read it yet.",
  "included_files": [],
  "name": "write-llms-txt",
  "skill_md_contents": "---\nname: write-llms-txt\ndescription: Check whether a site publishes an llms.txt and draft or improve one in the llmstxt.org format, while being honest that major AI models do not read it yet.\n---\n\n# Drafting an llms.txt\n\nUse this when the user asks for an llms.txt, wants to know whether theirs is any good, or asks what llms.txt is.\n\n## Set expectations first\n\nllms.txt is an emerging proposal (llmstxt.org): a Markdown file at `/llms.txt` that gives AI tools a short map of a site. Major AI models and answer engines do not read it yet. Say this up front. Glippy gives a small credit in Machine Readability when one exists, and lists a missing one as information, not as a fix to make. It is cheap to publish and may help developer tools and agents that do read it. Do not present it as a ranking factor or a priority fix.\n\n## Check what exists\n\nRun `check_llms_txt` on the domain the user named.\n\n- **Found:** review the contents against the format below and suggest concrete edits: missing summary, broken structure, links without descriptions, links to pages that no longer fit.\n- **Not found:** offer to draft one.\n- **Fetch failure:** say Glippy could not read it, which is not proof that it is missing. Do not retry.\n\n## The format\n\n```\n# Site or company name\n\n> One or two sentences on what the site is and who it is for.\n\nOptional short paragraph with key facts an assistant should know.\n\n## Section name\n\n- [Page title](https://example.com/page): what this page covers, in one line.\n\n## Optional\n\n- [Less important page](https://example.com/other): one line.\n```\n\n- One `#` heading, then a `>` summary, then `##` sections of links.\n- Every link is an absolute URL with a one-line description.\n- Put the pages that matter most first: product or service pages, pricing, documentation, about and contact. The `## Optional` section is for pages an assistant can skip.\n\n## Drafting rules\n\n- Use only pages you know exist: the homepage, links from a Glippy report in this conversation, or pages the user listed. Glippy reads the homepage only, so ask the user for the key page URLs instead of guessing paths like `/pricing` or `/docs`.\n- Mark anything you are unsure of as a placeholder for the user to fill in.\n- The user publishes the file at `https://<their-domain>/llms.txt`. Glippy cannot upload it.\n"
}