القائمة
Research and compare destinations with deeper scoring across budget, climate, logistics, activity fit, and seasonal tradeoffs before moving into full trip planning.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | travel-research |
| description | Research and compare destinations with deeper scoring across budget, climate, logistics, activity fit, and seasonal tradeoffs before moving into full trip planning. |
| version | 1.2.0 |
Use this skill when the user is not ready for a full itinerary yet and needs stronger destination research first. The goal is to compare places honestly, surface tradeoffs early, and identify the best fit before handing off into travel-planning or travel-itinerary.
Always judge options against Mick's actual travel preferences:
Focus on what materially separates one option from another:
travel-planningtravel-itineraryDifferent trip types should not weight the scorecard the same way. Apply the preset that matches the trip goal and say which one was used:
| Dimension | Endurance training | Sightseeing | Remote work | Budget recharge |
|---|---|---|---|---|
| Activity fit | 35% | 15% | 10% | 10% |
| Climate | 25% | 15% | 10% | 20% |
| Budget | 15% | 20% | 20% | 35% |
| Logistics / friction | 15% | 25% | 25% | 20% |
| Value for season | 10% | 25% | 35% | 15% |
For mixed-goal trips, blend the two closest presets and note the blend. The weighted score feeds the Overall column; never let a destination win on vibe while losing on every weighted dimension.
Treat prior research as reusable instead of rebuilding it:
When research concludes, end with a handoff block that travel-planning or travel-itinerary can consume directly without re-deriving anything:
SHORTLIST HANDOFF
Pick: [destination] | Window: [dates or month] | Style: [trip style preset]
Why it won: [one line]
Locked assumptions: [origin airport, budget band, solo, private rooms]
Carry-forward facts: [flight range found, daily spend estimate, friction score, must-book items]
Next skill: travel-planning [or travel-itinerary if dates and route are already firm]
For each destination, check:
When relevant, also compare:
Use this structure for substantial comparison requests:
TRIP GOAL:
[What the user is trying to optimize for]
OPTIONS:
- [Destination A]
- [Destination B]
SCORECARD:
| Destination | Budget | Climate | Activity | Logistics | Value | Overall |
|---|---:|---:|---:|---:|---:|---:|
LIVE DATA SNAPSHOT:
| Destination | Flight Pricing | Weather Normals | Crowd Level | Source / Confidence |
|---|---|---|---|---|
| [Destination A] | [Current range or estimate] | [Temp / rain / season note] | [Low / Medium / High] | [Source or assumption] |
| [Destination B] | [Current range or estimate] | [Temp / rain / season note] | [Low / Medium / High] | [Source or assumption] |
TRAVEL FRICTION:
| Destination | Visa / Entry | Flight Routing | In-Country Transport | Friction Score | Notes |
|---|---:|---:|---:|---:|---|
| [Destination A] | [1-5] | [1-5] | [1-5] | [Avg or weighted score] | [Main friction point] |
| [Destination B] | [1-5] | [1-5] | [1-5] | [Avg or weighted score] | [Main friction point] |
DESTINATION NOTES:
[Destination A]
- Best for:
- Watch for:
- Best season:
- Poor season:
- Estimated daily spend:
- Live data confidence:
- Travel friction:
[Destination B]
- Best for:
- Watch for:
- Best season:
- Poor season:
- Estimated daily spend:
RECOMMENDATION:
[Best choice and why]
RUNNER UP:
[Fallback and why]
NEXT STEP:
[Move into travel-planning or request deeper research on one option]
travel-planning once a destination is chosenshared/skill-standard.mdclaude/skills/travel-planning/SKILL.mdclaude/skills/travel-itinerary/SKILL.mdUse this skill when the user needs to decide where to go before planning the trip in detail.
Minimum useful input:
Example prompts:
Use travel-research to compare Madeira, Girona, and Mallorca for a spring cycling trip from BNA.
Research the best October solo trip options for hiking, good weather, and strong USD value.
Compare Japan and Portugal for a two week active trip with good food, easy logistics, and private room lodging.
Extract trip logistics from pasted travel emails, booking confirmations, forwarded messages, reservation notes, or raw itinerary text and generate one polished, self-contained offline HTML itinerary file for sharing with family or other travelers. Trigger when the user asks to turn trip emails into an HTML itinerary, travel handoff page, shareable trip page, family trip summary, booking-reference page, or offline travel document.
Work safely in the Trading repository for Alpaca helpers, backtesting, journaling, scheduling, and related PowerShell modules. Prefer additive changes, preserve existing trading logic unless the user asks otherwise, and default to paper-trading-safe guidance.
Write or draft a blog post for Mick's IT blog at mickitblog.blogspot.com. Trigger when Mick asks for a blog post or wants to document a technical solution, project, or finding in post format. Match Mick's writing style with plain first-person prose, practical focus, honest status notes, code blocks where relevant, and GitHub links when applicable.
Convert a finished blog post into three ready-to-post social media versions in one pass for Facebook, X, and LinkedIn. Always trigger immediately when the user's message starts with "bts". Also trigger on "blog to social", "social posts for this", "promote this post", or when the user pastes or links a blog post and asks to share it, promote it, or turn it into social content.
Answer questions, assist with planning, and help with design decisions for Mick's off-grid shipping container lake home project. Trigger when the user mentions the container home, lake home, Stewart County, LBL, the expansion, solar system, septic permitting, or retirement property.
Retrieve new cryptocurrency listings from the past 7 days and upcoming listings in the next 7 days across major exchanges. Always trigger immediately when the user's message starts with "cl" or says "crypto listings", "new crypto", "new coins", "upcoming listings", or asks what cryptos just launched or are launching soon. Always verify current listings data before responding; never answer from memory.