Update to Hydrafetch

{
  "description": "Read a public web page the user links to or names, and answer from its actual content. Use when the user shares a URL, asks to summarise, explain or quote a page, or asks what a specific page says.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 214
    }
  ],
  "name": "read-a-web-page",
  "skill_md_contents": "---\nname: read-a-web-page\ndescription: Read a public web page the user links to or names, and answer from its actual content. Use when the user shares a URL, asks to summarise, explain or quote a page, or asks what a specific page says.\n---\n\nUse this skill when the user gives a URL or names a specific page and wants to know what it says.\n\n1. Call `scrape` with the `url`. Set `preferStructure` to true when the page's meaning lives in tables, lists or headings, such as pricing pages, comparison grids, documentation and spec sheets.\n2. Answer from the returned markdown only. Quote or paraphrase what the page says, and link the URL you read.\n3. If the user asked for a format, such as bullets or a table, build it from the page content.\n\nWhen the result is thin or looks wrong:\n\n- If the content is very short, is mostly a cookie notice, or says the page needs JavaScript, say what came back and offer to try again rather than guessing at the rest.\n- If the page returned an error or was refused, tell the user plainly that the page could not be read. Do not fill the gap from memory.\n- If the page redirected somewhere unexpected, mention the final URL.\n\nDo not:\n\n- Invent facts the page does not state, even when they seem likely.\n- Read pages that need the user to be signed in. This tool only reads public pages; say so if the user asks for account or private data.\n- Scrape a whole site when one page answers the question. If the user wants several pages from one site, list them with `map` first and read only the ones that matter.\n\nThe user's explicit instructions take priority over this skill.\n"
}