jhins-trip-planner

Generates source-verified trip itineraries, travel guides, and refactored itinerary pages with budget and safety checks.

1|Updated Apr 19, 2026
One-click install
npx skills add https://github.com/jhinzzz/jhins-travel-guide-skills --skill jhins-trip-planner-jhinzzz
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: jhins-trip-planner
Source: https://github.com/jhinzzz/jhins-travel-guide-skills/tree/main/skills/jhins-trip-planner
Command: npx skills add https://github.com/jhinzzz/jhins-travel-guide-skills --skill jhins-trip-planner-jhinzzz

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) and assets (resource) components.

What problem does it solve? Planning a trip requires verifying dozens of volatile facts — restaurant operating status, hotel rates, transport schedules, visa rules, attraction booking windows — and AI assistants often fabricate these details from training data. This Skill enforces a strict evidence standard so every price, schedule, and venue in a travel plan is traceable to a real source with a research date, or explicitly degraded to a labeled fallback. ## Core Features & Use Cases - Three output modes: planning-only advice, full guide-redesign (markdown + HTML deliverables), and existing-page refactor that preserves all user-supplied content while reorganizing it. - Domain rule packs: dedicated references for dining verification, hotel tiering with hardware-freshness signals, round-trip transport, budget category splits with FX timing, attractions booking lead times, local specialties, safety and emergency info, and trip prep (visa, payment, SIM, insurance, etiquette). - Anti-fabrication pipeline: knowledge-layer classification, parallel batch verification sliced by geography, login-wall channel ladders, timeout degradation to search advisory cards, and a mechanical HTML validator plus a final-check assertion list. - Use Case: Ask it to plan a 5-day family trip to Tokyo over Spring Festival with a budget — it produces a day-by-day guide with verified restaurants, hotel shortlists, transport cards, a pre-trip recheck block, and a full safety section, each fact cited with source and date. ## Quick Start Ask the assistant to plan a trip with your destination, dates, party, and budget, for example: plan a 5-day Tokyo trip for two over Golden Week with a 50000 CNY budget and a focus on dining.

Frequently Asked Questions about jhins-trip-planner

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I plan a trip with verified restaurant and hotel recommendations?

Provide your destination, dates, party composition, and budget, and the planner verifies every restaurant's operating status and every hotel's rate against live web sources before including them. Each recommendation carries a source and research date, and unverifiable items degrade to labeled search advisory cards instead of fabricated names.

What is the difference between planning-only and guide-redesign output modes?

Planning-only produces conversational advice or a markdown outline with critical flags, while guide-redesign produces full markdown plus HTML deliverables with complete checklists, transport cards, hotel shortlists, and safety sections. The skill asks for confirmation before switching from advice into file generation.

Can it reorganize my existing travel notes into a guide?

Yes, the existing-page-refactor mode inventories your notes, bookings, and saved venues first, then re-maps them into a structured guide without deleting any facts. It confirms before replacing an existing page structure and diffs any embedded trip-data block to ensure nothing is lost.

Does it handle international trip preparation like visas and payments?

Yes, international trips trigger a trip-prep checklist covering visa and transit-visa status, payment methods, SIM or eSIM, insurance, local etiquette, and religious or festival date overlaps. Greater-China crossings are correctly described as permits rather than visas.

What happens when web verification fails or hits a login wall?

A login wall on one platform is not treated as failure; the skill climbs a channel ladder including search aggregators before degrading. Only after exhausting channels does it output a search advisory card with platform, keywords, and filters, and it never falls back to training-data names for restaurants.

When does it use parallel sub-agents for verification?

When the combined verification list reaches five or more items, or the trip spans two or more cities, it fans out one sub-agent per geographic slice in a single itinerary-wide batch. Each sub-agent returns structured rows for every venue in its slice, and the main conversation synthesizes the results.