One .zip per skill. Inside: SKILL.md with the intent and the frontmatter, and the code that runs in the page.
Settings → Personalize → Skills. This is Cowork's own skill library, shared across every chat.
Click Add and choose the file you just downloaded. Cowork installs it once; no CLAUDE.md, no per-project setup.
The skill stays available in every session. Cowork runs it in your own Chrome, riding the session you are already signed into.
Search Airbnb stays by PLACE NAME (no coordinates needed).
{"location":"string, REQUIRED (place name, e.g. \"San Francisco, CA\" or \"Barcelona, Spain\")","checkin":"YYYY-MM-DD (optional)","checkout":"YYYY-MM-DD (optional)","adults":"int (optional, default 1)","price_min":"int, PER NIGHT USD (optional)","price_max":"int, PER NIGHT USD (optional)","count":"int (optional, default 18, max 50)"}{"count":"int","query":"string (the location searched)","listings":"array of { id, url, name, title, price (stay TOTAL), originalPrice, priceQualifier, rating, reviews, beds, badges, lat, lng, photo }"}Searches stays from a plain place name, Airbnb geocodes it server-side, so no coordinates are needed. Resolves in a single bridge call: it POSTs Airbnb's internal StaysSearch GraphQL query directly, so no search page is opened and the params actually drive the request.
The extractor lives as text in the site's localStorage (key airbnb-search-by-place) and is rebuilt on each call with synchronous eval. It is stored once and then persists across navigation and browser restarts, so on every run except the first it is already there.
Default action: just call (step 1). The call itself reports NEEDS_STORE when the extractor is missing or out of date, only then do you store it (step 2) and call again.
Versioning. The stored extractor is gated by VER (must match the version in the frontmatter above). Both snippets carry VER = "1", keep them in sync with the frontmatter. When evaluate.js changes, bump version and VER in both snippets: the next call sees the mismatch, returns NEEDS_STORE, and re-stores automatically. Storage stays at two keys (airbnb-search-by-place and airbnb-search-by-place:ver), overwritten each store, versions never accumulate.
await (() => {
const KEY = "airbnb-search-by-place", VER = "1";
const s = localStorage.getItem(KEY);
if (!s || localStorage.getItem(KEY + ":ver") !== VER) return 'NEEDS_STORE';
const fn = eval('(' + s + ')');
return fn(document, { location: "San Francisco, CA", checkin: "2026-08-10", checkout: "2026-08-12", adults: 2 });
})()
Returns the matching stays. If it returns the string 'NEEDS_STORE', the extractor is missing or stale in this browser → do step 2 once, then run this exact call again.
Run this snippet verbatim. Never add an await before the eval, only the outer await is allowed.
Any airbnb tab works, the extractor calls the API itself and never reads the open page. Note that airbnb.com redirects to a country domain by IP (airbnb.com.ar, airbnb.co.uk, ...); the extractor uses whatever origin the tab is on, which is required for the request to be same-origin. The locale is pinned to en for the copy only, geocoding is unaffected and resolves the same from any country domain.
NEEDS_STORE; persists until localStorage is cleared)From any airbnb tab, evaluate the following with the bridge, replacing <FN> with the contents of evaluate.js (the ( async (root, params) => { ... } ) function). Keep VER equal to the call snippet's:
(() => {
const KEY = "airbnb-search-by-place", VER = "1";
const fn = (<FN>);
localStorage.setItem(KEY, String(fn));
localStorage.setItem(KEY + ":ver", VER);
return 'stored';
})()
Returns "stored". The extractor passes through the model only here, once. Then go back to step 1.
Airbnb resolves the place name server-side. Ambiguous names resolve to whichever place Airbnb judges most likely, "San Francisco, CA" is verified to return California, but a bare "San Francisco" could land anywhere. Qualify the name (add state/country), and check the returned lat/lng if the place is ambiguous. When you need a guaranteed region, use airbnb-search-area with an explicit bounding box instead.
price is the total for the whole stay, not per night, read priceQualifier (e.g. "for 2 nights") before comparing anything. price_min / price_max, in contrast, filter per night. So a 2-night stay filtered at price_max: 150 correctly returns a $249 total ($124.50/night). Do not "fix" this by widening the filter.
NEEDS_STORE → extractor missing or version-mismatched in this browser; run step 2 once, then retry step 1.missing_params: location is required → pass a place name.tool-broken: HTTP 4xx / PersistedQueryNotFound → the pinned sha256Hash rotated on an Airbnb deploy. Recapture it from the StaysSearch XHR the search page fires, update HASH in evaluate.js, and bump version/VER.request_failed → no airbnb tab, or the call ran cross-origin (see step 1).{ "type": "json", "jsonPath": "count" }