Places
Use browser.search for all place discovery and name/address lookup. Run
places <command> through muse.exec for richer details and photo-based place
detection. Never load or search for a places tool namespace. If a search
comes back empty or weak, refine the browser.search query per the rules
below. Print CLI JSON to stdout for you to read, not to show the user. Use
--help when needed. No sign-in is required.
Common flows
Find places
Use browser.search for standing places people can visit or reference on a
map: restaurants, cafes, bars, hotels, parks, trails, attractions, shops, and
local services. A follow-up like "anything cheaper?" or "Italian instead?"
refines the preceding search.
- Put the complete user intent in
primary_query.query. Include the place
category or venue name, area, radius, and ranking preference in natural
language. For example, search for "best sushi restaurants in San Francisco
within five miles", not just "sushi".
- Preserve "near me" or "nearby" in the query when that is what the user asked so
that device location is used; never invent or guess a location.
- One call covers one area. When the user names multiple cities or
neighborhoods, run a separate call for each and cover each in the answer.
- For category discovery, include the category and area in the query. For a
named venue, include its exact name and enough area context to disambiguate
it.
- For "best," trending, insider, or nuanced requests, use the web evidence and
place results returned together by
browser.search. Ground every named venue
in a returned result.
- When comparable
avg_rating values from places details are available for
every shortlisted place, order them highest first but never print the rating.
Otherwise order by relevance to the user's constraints.
- Avoid showing permanently or temporarily closed places unless specifically
asked for.
- Judge the returned result set rather than following rank blindly. Set aside
wrong-category or wrong-area results. If the set is weak, retry with an exact
venue name, a narrower subtype, or clearer area language.
Get richer details
places details takes numeric place IDs only. It cannot search by name or
address; use browser.search for that.
- Call
places details only when browser.search explicitly returns an all-digit
place_id for that result. Never derive an ID from a venue name or URL.
- Prefer the
browser.search response when it already contains enough detail. Use
places details for richer or fresher hours, prices, photos, reviews, and
offerings.
- If
browser.search returns no numeric ID, retry once with the exact venue
name and area. If that still returns no ID, answer from cited search evidence
without details or a map.
- Batch several IDs into one call when comparing places. Pass
--motivation
with the user's intent so quotes and photos are ranked for it.
places details returns {"<place_id>": {"details": {…, "rating": {"avg_rating", "num_rating"}}}}, keyed by id.
Show places on a map
Before creating a map, run places details for the selected numeric IDs. Create
one map if at least one returned details record has both a numeric place ID and
coordinates. This applies to recommendations, comparisons, named-place
lookups, and other uses where a map could ground the user. See Response
formatting for which places go on it.
Create one local_map widget with widget.create and this payload:
{
"kind": "local_map",
"data": {
"elements": [
{
"kind": "rich_place",
"place_id": "<numeric ID>",
"name": "<name from the same result>",
"coordinate": {
"latitude": 0.0,
"longitude": 0.0
}
}
]
}
}
- Replace the example coordinates with the values from the same keyed
places details record. Use its canonical name. Omit a place whose details
or coordinates are missing; never infer an ID or geocode a name.
- If creation fails, answer in text. Do not retry or build an HTML or image map.
Identify a place from a photo
Use places detect when captured frames and GPS need to resolve which place the
user is at. It returns ranked candidates as {place_id, place_name, confidence}.
Pass a returned ID to places details for more. The optional 4th --location
field is the connected Wi-Fi BSSID; include it verbatim when known to improve
Home/Work matching, and never echo a raw BSSID back to the user.
Response formatting
- Never name a place that did not come back from a tool.
- Match the framing to the ask. When the user wants a recommendation, give them
two to three. When the request is broad, offer a few named results as a
starting point.
- Name two to three places in text from the merged result set. Write each on
its own line in exactly this shape:
**Name**, a sentence or two on why you chose it. Open with one short line framing the answer before the places.
- Send the text as one message. Never add a second message after the map.
- No addresses, raw place IDs, coordinates, star ratings, review counts, or
price levels in text.
- After a recommendation, note there are more options without itemizing; after
a broad answer, offer to narrow to a recommendation.
- Cite factual claims sourced from
browser.search using its normal citation
format.
- Resolve every name you plan to use, closing line included, through
browser.search before creating the map. Never name an unresolved place.
- Build the map from the most relevant places returned that have a place ID
and coordinates. Don't rely solely on named places in your text as an
indication of what places should appear on the map.
- The places you named come first on the map, in the order you named them,
ahead of everything else.
- Create one map per answer. Include the returned
embed_token.
- Never narrate or reference the map. No "I mapped things out for you"; "Take a look at the map", etc.
Limits
- Do not write directions, turn-by-turn steps, maps links, or navigation
controls.
- Do not estimate travel times or distances. Use only values returned by a tool.
1---2name: places-search3title: "Places Search"4description: "Find, compare, and share details on physical places near the user or in a specified area, including restaurants, cafes, bars, hotels, parks, attractions, shops, and businesses with local services. Not for itineraries, choosing a city or region, dated events or showtimes, or directions."5metadata:6 source: https://skillmd.com/skills/win4r/places-search7 includeInPrompt: false8---910# Places1112Use `browser.search` for all place discovery and name/address lookup. Run13`places <command>` through `muse.exec` for richer details and photo-based place14detection. Never load or search for a `places` tool namespace. If a search15comes back empty or weak, refine the `browser.search` query per the rules16below. Print CLI JSON to stdout for you to read, not to show the user. Use17`--help` when needed. No sign-in is required.1819## Common flows2021### Find places2223Use `browser.search` for standing places people can visit or reference on a24map: restaurants, cafes, bars, hotels, parks, trails, attractions, shops, and25local services. A follow-up like "anything cheaper?" or "Italian instead?"26refines the preceding search.2728- Put the complete user intent in `primary_query.query`. Include the place29 category or venue name, area, radius, and ranking preference in natural30 language. For example, search for "best sushi restaurants in San Francisco31 within five miles", not just "sushi".32- Preserve "near me" or "nearby" in the query when that is what the user asked so33 that device location is used; never invent or guess a location.34- One call covers one area. When the user names multiple cities or35 neighborhoods, run a separate call for each and cover each in the answer.36- For category discovery, include the category and area in the query. For a37 named venue, include its exact name and enough area context to disambiguate38 it.39- For "best," trending, insider, or nuanced requests, use the web evidence and40 place results returned together by `browser.search`. Ground every named venue41 in a returned result.42- When comparable `avg_rating` values from `places details` are available for43 every shortlisted place, order them highest first but never print the rating.44 Otherwise order by relevance to the user's constraints.45- Avoid showing permanently or temporarily closed places unless specifically46 asked for.47- Judge the returned result set rather than following rank blindly. Set aside48 wrong-category or wrong-area results. If the set is weak, retry with an exact49 venue name, a narrower subtype, or clearer area language.5051### Get richer details5253- `places details` takes numeric place IDs only. It cannot search by name or54 address; use `browser.search` for that.55- Call `places details` only when `browser.search` explicitly returns an all-digit56 `place_id` for that result. Never derive an ID from a venue name or URL.57- Prefer the `browser.search` response when it already contains enough detail. Use58 `places details` for richer or fresher hours, prices, photos, reviews, and59 offerings.60- If `browser.search` returns no numeric ID, retry once with the exact venue61 name and area. If that still returns no ID, answer from cited search evidence62 without details or a map.63- Batch several IDs into one call when comparing places. Pass `--motivation`64 with the user's intent so quotes and photos are ranked for it.65- `places details` returns `{"<place_id>": {"details": {…, "rating":66 {"avg_rating", "num_rating"}}}}`, keyed by id.6768### Show places on a map6970Before creating a map, run `places details` for the selected numeric IDs. Create71one map if at least one returned details record has both a numeric place ID and72coordinates. This applies to recommendations, comparisons, named-place73lookups, and other uses where a map could ground the user. See Response74formatting for which places go on it.7576Create one `local_map` widget with `widget.create` and this payload:7778```json79{80 "kind": "local_map",81 "data": {82 "elements": [83 {84 "kind": "rich_place",85 "place_id": "<numeric ID>",86 "name": "<name from the same result>",87 "coordinate": {88 "latitude": 0.0,89 "longitude": 0.090 }91 }92 ]93 }94}95```9697- Replace the example coordinates with the values from the same keyed98 `places details` record. Use its canonical name. Omit a place whose details99 or coordinates are missing; never infer an ID or geocode a name.100- If creation fails, answer in text. Do not retry or build an HTML or image map.101102### Identify a place from a photo103104Use `places detect` when captured frames and GPS need to resolve which place the105user is at. It returns ranked candidates as `{place_id, place_name, confidence}`.106Pass a returned ID to `places details` for more. The optional 4th `--location`107field is the connected Wi-Fi BSSID; include it verbatim when known to improve108Home/Work matching, and never echo a raw BSSID back to the user.109110## Response formatting111112- Never name a place that did not come back from a tool.113- Match the framing to the ask. When the user wants a recommendation, give them114 two to three. When the request is broad, offer a few named results as a115 starting point.116- Name two to three places in text from the merged result set. Write each on117 its own line in exactly this shape: `**Name**, a sentence or two on why you118 chose it.` Open with one short line framing the answer before the places.119- Send the text as one message. Never add a second message after the map.120- No addresses, raw place IDs, coordinates, star ratings, review counts, or121 price levels in text.122- After a recommendation, note there are more options without itemizing; after123 a broad answer, offer to narrow to a recommendation.124- Cite factual claims sourced from `browser.search` using its normal citation125 format.126- Resolve every name you plan to use, closing line included, through127 `browser.search` before creating the map. Never name an unresolved place.128- Build the map from the most relevant places returned that have a place ID129 and coordinates. Don't rely solely on named places in your text as an130 indication of what places should appear on the map.131- The places you named come first on the map, in the order you named them,132 ahead of everything else.133- Create one map per answer. Include the returned `embed_token`.134- Never narrate or reference the map. No "I mapped things out for you"; "Take a look at the map", etc.135136## Limits137138- Do not write directions, turn-by-turn steps, maps links, or navigation139 controls.140- Do not estimate travel times or distances. Use only values returned by a tool.