Update to manpage.ai

{
  "description": "Use when the user needs authoritative or version-specific Linux command, system call, library, file-format, configuration, or administration documentation from manual pages.",
  "included_files": [],
  "name": "linux-manual-reference",
  "skill_md_contents": "---\nname: linux-manual-reference\ndescription: Use when the user needs authoritative or version-specific Linux command, system call, library, file-format, configuration, or administration documentation from manual pages.\n---\n\n# Linux manual reference\n\nUse the manpage.ai tools to ground answers in indexed Linux manual pages and\ntheir exact package provenance.\n\n## Choose a tool\n\n- Use `get_manual` when the user names a command or manual and wants its\n  behavior, syntax, options, files, exit status, or examples explained.\n- Use `search` when the user describes a topic, flag, error, capability, or\n  phrase but does not know the relevant manual name. Use `manual_name` without\n  `query` to find name and alias matches or to page through alternatives.\n- Use `get_targets` before adding a distribution, release, repository, or\n  architecture filter whose exact indexed value is not already known.\n\n## Preserve scope and provenance\n\n- Carry every distribution, release, repository, architecture, package,\n  package-version, section, and locale constraint the user supplies into the\n  tool call. Filters are exact and case-sensitive.\n- Do not silently broaden an explicit scope. If it has no match, say so and\n  offer an available scope or an unfiltered lookup.\n- When scope is omitted, explain any meaningful distro or package selection\n  using the provenance returned by the tool.\n- Treat a returned manual as version-specific evidence, not as a claim that\n  every Linux distribution or software version behaves identically.\n\n## Retrieve efficiently\n\n- Start with a small search result limit and increase it only when needed.\n- When following `next_cursor`, repeat the same search arguments and change\n  only `cursor`.\n- Prefer section `1` for user commands and section `8` for administration only\n  when the user's request or ambiguity makes that distinction relevant.\n- For punctuation-only manual names such as `[`, pass the literal name to\n  `get_manual`.\n\n## Answer clearly\n\nSummarize the relevant manual text instead of reproducing an entire manual.\nName the distribution, release, package, and version when they materially\naffect the answer. Distinguish facts supported by the retrieved manual from\ngeneral guidance or inference.\n"
}