Update to trip1

{
  "name": "content-access",
  "description": "Fetch any trip1 content page (travel guides, help articles, hotel pages) as clean markdown by sending Accept, text/markdown. Also includes llms.txt and llms-full.txt indexes.",
  "included_files": [],
  "skill_md_contents": "---\nname: content-access\ndescription: Fetch any trip1 content page (travel guides, help articles, hotel pages) as clean markdown by sending Accept, text/markdown. Also includes llms.txt and llms-full.txt indexes.\n---\n\n# Reading trip1 content as markdown\n\nEvery content page on trip1 is available as clean markdown when requested with the right Accept header. This avoids parsing HTML and strips component chrome.\n\n## Per-page markdown\n\nSend `Accept: text/markdown` to any content URL:\n\n```\ncurl -H \"Accept: text/markdown\" https://trip1.com/travel-guides/spain/barcelona\n```\n\nThe response is lean — headings, prose, and links only.\n\n## Discovery indexes\n\n- `https://trip1.com/llms.txt` — short overview, good for a first pass.\n- `https://trip1.com/llms-full.txt` — longer index with destinations, travel guides (capped at 200 most recent), and help center categories.\n- `https://trip1.com/sitemap.xml` — complete URL set.\n\n## What's indexed\n\n- Travel guides: `https://trip1.com/travel-guides/...`\n- Destination pages: `https://trip1.com/travel-guides/<country>` and `https://trip1.com/travel-guides/<country>/<city>`\n- Hotel pages: `https://trip1.com/hotels/...`\n- Help center: `https://trip1.com/help/<collection>` and `https://trip1.com/help/<collection>/<slug>`\n\n## When to use HTML instead of markdown\n\nIf you need structured data (hotel pricing, availability, booking links), use the MCP tools described in the hotel-booking skill. Markdown pages are for reading — they don't include live pricing.\n"
}