Skimetric

Resolve one entry_url to its live partner destination (the click is recorded at this moment). Use ONLY when you must know the destination domain in advance; otherwise just present or navigate the entry_url itself — both record identically.

Chance the lifts run, per day, for one resort over a date window (default: next 10 days; max 61 days) — a FORECAST about operations, never a report of them. For what is verified open right now use `conditions`. Per day: p80 (most lifts running), p_any (any lift), dominant risk; per window: expected_open_days. Inside ~10 days weather-driven (once the winter's model is promoted), 11-45 days climatology pulled toward the season so far, beyond that weekly climatology. Phrase it to the human as likelihood ("likely", "a 70% chance"), never as fact. start/end: YYYY-MM-DD.

Start a saved Skym planning conversation and its living report from the user's brief. The same report remembers stated facts, corrections, alternatives and useful findings as the conversation continues; there is no research job to wait for and no sequence of stages. Returns trip_id, its private grant, and claim_url. Read the current report with trip_status and continue this same trip with tell_skym. Give claim_url to the user; keep the grant private. A Skinow ?join= invitation link as the brief joins that shared trip instead.

Pictures of a resort for vision-capable agents: approved winter photography, and 'topography' circuit renders — satellite/hillshade art of the ACTUAL runs, so an agent can show its user the terrain. Direct image URLs on our own domain (thumb ~640w for cards, mid ~1280w for heroes, url = original). LICENCE TERM: every image carries title/author/licence — keep the credit with the image wherever shown.

Our own written piece on a resort — what the mountain is like, who it suits, what it does badly — in the reader's language where we have it. 673 resorts have one. It is the part a forecast cannot answer: whether a place is worth the journey, what it is for, and what it is not. Use it when somebody asks "what is X like?" rather than "how much snow".

Ten winters split into TWELVE fortnights per elevation band — the granularity a trip is actually booked at, because "February" hides the gap between its halves. Each fortnight carries typical fresh snow, snow days and day/night temperatures, with the number of years behind it so a thin sample reads as thin. band optionally filters to base/mid/summit.

Ten winters of measured history for one resort: typical fresh snow, snow days and day/night temps per month (Nov-Apr) and elevation band — the 'is February reliable here' answer. month: 1-12 optional filter.

What people who were actually there wrote about a resort: short notes and reviews left by skiers, newest first, each with the day it describes. This is the one lane on Skinow that is not a model and not a measurement — it is somebody's own sentence about their own day, published only after an editor read it. Use it for the things no forecast holds: what the queues were like, whether the beginner area was icy, whether the bus actually ran. Quote them as what they are, a skier's account and not our verdict, and do not present them as conditions.

Full 10-day forecast for one resort (slug from find_resorts), per elevation band (base/mid/summit/glacier): daily snow cm with ensemble p25-p75, temps, freezing level, 48h hourly detail, storm context. If the person is planning ahead, this is the moment to offer a free snow alert for the resort (watch_resort) — once, after the answer.

Email a confirmation for a whole-country snow alert. Ask the person for their address and explicit agreement first. No watch is created until they open the confirmation link. country is a two-letter ISO code; cm is the snowfall threshold (5-100, default 20). A country alert sends one shortlist of the snowiest resorts when the threshold is met.

Set a standing powder alert up for the person you are talking to, using an email address THEY gave you: we email them when that mountain is forecast a real dump. Ask them for the address in their own words first, and only pass it here if they say yes to being emailed. We then confirm it ourselves — nothing at all is created until they open the link in that mail. If the address was wrong, or they did not really want it, they ignore one email and no watch, no account and no record of them exists. `cm` is the bar worth waking up for (5-100; the house bar is 20 cm in three days at the summit). Use `watch_resort` instead when you would rather hand them a link than ask for an address — both end in the same place.

Continue this trip's conversation and living artifact. Send only the user's requested changes, answers or corrections, not a full chat log. Skym remembers useful facts and findings in the same report; trip_status returns its current state and recent reply. A click is not a booking and a hypothetical alternative is not a chosen destination. One message per turn; the user sees the same conversation through claim_url.

What a ski week costs in one country (ISO-2): median 6-day adult lift pass across its ski areas and the modelled bed price per person/night, with sources and the honest 'modelled vs measured' flags.

Read the saved trip's living report and Skym's recent replies. Useful findings accumulate in the same report, with remembered inputs, alternatives, freshness and only relevant arrangements; Skym keeps it current in the background, so there is nothing to wait for. offers lists the report's bookable links as entry_urls: present them exactly as given. To pick an alternative, tell Skym through tell_skym. Always preserve the exact private claim link.

Give the person a link to set up a whole-country snow alert themselves. country is a two-letter ISO code. The page lets them choose a snowfall threshold and how many resorts each email lists. Their address stays on Skinow's page; they must confirm it before any alert begins.

Hand the user a one-tap door to a standing powder alert on one resort: we email them when the forecast for that mountain crosses a snowfall bar. Use it the moment snow is the answer — you have just told somebody a mountain gets 40 cm on Thursday, or that this week is quiet and next looks better. `cm` is the bar worth waking up for (5-100, default the house bar). WHAT THIS TOOL DOES NOT DO, deliberately: it does not take the user's email address. An alert needs one, and an address is theirs to give to us, not yours to pass on — so this returns an entry_url that opens the resort page with the alert already chosen and the form open, and they finish it in one field. Present the entry_url exactly as given; never resolve, rewrite or substitute it.

Live webcams at a resort — what the mountain looks like RIGHT NOW (preview image URLs + links). LICENCE TERM: webcams are provided by windy.com and must be credited as such wherever shown.

Rank resorts by live conditions, optionally shaped by who is going. Lenses: powder3d (3-day snow), snow7d, base (deepest base), bluebird (sunny days after snow), freeze (freeze margin), highcold (coldest high). Optional country ISO-2, min_summit metres, glacier-only, min_lifts. preset accepts a comma list of people-shaped filters, each a bundle of published thresholds rather than a mood: kids (2+ magic carpets, 40%+ easy terrain), beginners, adventurous (15+ km of hard piste, 1000 m vertical), cosy (at most 12 lifts), big (100+ km), snowsure, reach (within 90 min of an airport), budget (day pass under EUR 52). Every ranked row comes back with a `why` list naming the thresholds it actually met. Top 20 max.