← Cims (fescims.com)CONTENT HISTORY
WHAT CHANGED
Update to Cims (fescims.com)
Snapshot Nov 2, 2026 · 18:12 UTC · version 1.1.2
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save Cims (fescims.com) and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Suggest a peak to climb and a trail to climb it by. Use when someone asks for a hike, a summit or a day out in the mountains, mentions a town, comarca, valley or peak in Catalonia, the Pyrenees or Spain, or wants something easy, family- or dog-friendly, short, long or with a view.",
"included_files": [],
"name": "plan-a-hike",
"skill_md_contents": "---\nname: plan-a-hike\ndescription: Suggest a peak to climb and a trail to climb it by. Use when someone asks for a hike, a summit or a day out in the mountains, mentions a town, comarca, valley or peak in Catalonia, the Pyrenees or Spain, or wants something easy, family- or dog-friendly, short, long or with a view.\n---\n\n# Plan a hike with Cims\n\nUse the Cims connector's tools, in the user's language.\n\n## 1. Find where\n\n- **A peak by name:** call `search_peaks` with the name and keep the `slug`.\n- **A town, village or valley** (\"near Berga\", \"from Núria\"): use its approximate `lat` and `lng` as the point for the next calls. Searching a town name with `search_peaks` can match a different place entirely (\"Berga\" finds Bergamo).\n- **A comarca, province or country** (\"in the Berguedà\"): call `search_peaks` with it as `query` and use the `lat` and `lng` of the results as the point.\n- **Coordinates the user gave you:** use them directly.\n\n## 2. Pick the peak\n\nCall `peaks_nearby` with the point and a `radiusKm` that fits the trip (10–20 km for a day out). Narrow with what the user asked for:\n\n- `familyFriendly` or `dogFriendly` for families and dogs.\n- `altitudeBands` for a height range.\n- `essentialOnly` for the peaks a challenge marks as must-climb.\n- `sort: \"recommended\"` when the user only wants a good idea.\n\nThen call `get_peak` on the one or two strongest candidates. Use its community ratings (1–5, with the number of votes), its recent summits and its comments to judge how it is going this season.\n\n## 3. Pick the trail\n\nCall `search_trails` with `peakSlug`, or with the point when the user cares about the trailhead. Match the request with `difficulty`, `distanceBands`, `ascentBands`, `shape` (loop, out-and-back, one-way), `suitableFor`, `easyParking` and `scenery`. `suitableFor`, `scenery` and `easyParking` come from community votes, so many good trails have none: if one of them empties the list, search again without it and judge from distance, ascent and difficulty. Call `get_trail` on the best one for times, ascent, the start point and the Wikiloc link.\n\n## 4. Answer\n\nGive one clear suggestion first, then one or two alternatives. For each:\n\n- the peak, its height and the trail's distance, ascent, estimated time and difficulty;\n- why it fits what the user asked;\n- the peak's `url` on fescims.com and the trail's Wikiloc link.\n\nRatings with few votes are a hint, not a verdict, so say how many votes there are. Remind the user to check the weather and conditions before going: the catalogue does not know today's snow, storms or closures.\n\nIf nothing fits, widen the radius or relax one filter and say which one you relaxed.\n"
}SHA-256 of public snapshot: dae2f1309798383524ac3df3728ea965529a2429e1814474ef83b2b93779b9e0