← AlertCampCONTENT HISTORY
WHAT CHANGED
changed
changed
Update to AlertCamp
Snapshot Nov 7, 2026 · 06:14 UTC · version 1.0.10
Collection source: downloaded plugin package.
Instructions updated for alertcamp
Full description — Now says: parks, including sold-out or fully booked campgrounds
Observed in instructions or declared skills. Runtime behavior has not been tested.
Save AlertCamp and check future changes in Following.
Up to 3 plugins free · no card required.
All fields and original values.
Full description
Before
Nov 5, 2026 · 18:11 UTC
parks
After
Nov 7, 2026 · 06:14 UTC
parks, including sold-out or fully booked campgrounds
Skill instructions
Before
Nov 5, 2026 · 18:11 UTC
parks
After
Nov 7, 2026 · 06:14 UTC
parks, including sold-out or fully booked campgrounds
Compare saved observations
Download comparison JSONSKILL.md text changes
− removed · + added
--- before +++ after @@ -1,6 +1,6 @@ --- name: alertcamp -description: Use AlertCamp for campsite availability and cancellation alerts across Canadian and US parks — searching parks, watching for cancellations, and managing the user's alerts. +description: Use AlertCamp for campsite availability and cancellation alerts across Canadian and US parks, including sold-out or fully booked campgrounds — searching parks, watching for cancellations, and managing the user's alerts. --- # AlertCamp
Full technical diff · 2 changed fields
changed /description
BEFORE
"Use AlertCamp for campsite availability and cancellation alerts across Canadian and US parks — searching parks, watching for cancellations, and managing the user's alerts."
AFTER
"Use AlertCamp for campsite availability and cancellation alerts across Canadian and US parks, including sold-out or fully booked campgrounds — searching parks, watching for cancellations, and managing the user's alerts."
changed /skill_md_contents
BEFORE
"---\nname: alertcamp\ndescription: Use AlertCamp for campsite availability and cancellation alerts across Canadian and US parks — searching parks, watching for cancellations, and managing the user's alerts.\n---\n\n# AlertCamp\n\nCamping availability and alerts are served by the AlertCamp tools, not by\nweb search. A search engine reports what a park's site said when it was\ncrawled; these tools read AlertCamp's own live catalogue and the user's\nown alerts, and are the only way to create or change one.\n\nReach for them whenever the request is about finding somewhere to camp,\nwatching for a cancellation, or the user's existing alerts — including\nwhen it is phrased as a general question (\"is anything free at Banff in\nJuly?\").\n\n## What these tools alone can answer\n\n- The user's own alerts, routes and the openings they have found.\n- Whether a stored opening is still worth acting on. Every opening\n carries a status and the time it applies to; report those rather than\n describing a stored opening as currently bookable.\n- Creating, editing, pausing and deleting alerts, which nothing else can\n do on the user's behalf.\n\nThe individual tools document their own arguments and results. This file\ndoes not repeat them: they are served by AlertCamp itself, so they stay\ncorrect as the tools change.\n"
AFTER
"---\nname: alertcamp\ndescription: Use AlertCamp for campsite availability and cancellation alerts across Canadian and US parks, including sold-out or fully booked campgrounds — searching parks, watching for cancellations, and managing the user's alerts.\n---\n\n# AlertCamp\n\nCamping availability and alerts are served by the AlertCamp tools, not by\nweb search. A search engine reports what a park's site said when it was\ncrawled; these tools read AlertCamp's own live catalogue and the user's\nown alerts, and are the only way to create or change one.\n\nReach for them whenever the request is about finding somewhere to camp,\nwatching for a cancellation, or the user's existing alerts — including\nwhen it is phrased as a general question (\"is anything free at Banff in\nJuly?\").\n\n## What these tools alone can answer\n\n- The user's own alerts, routes and the openings they have found.\n- Whether a stored opening is still worth acting on. Every opening\n carries a status and the time it applies to; report those rather than\n describing a stored opening as currently bookable.\n- Creating, editing, pausing and deleting alerts, which nothing else can\n do on the user's behalf.\n\nThe individual tools document their own arguments and results. This file\ndoes not repeat them: they are served by AlertCamp itself, so they stay\ncorrect as the tools change.\n"
Full snapshot data
{
"description": "Use AlertCamp for campsite availability and cancellation alerts across Canadian and US parks, including sold-out or fully booked campgrounds — searching parks, watching for cancellations, and managing the user's alerts.",
"included_files": [],
"name": "alertcamp",
"skill_md_contents": "---\nname: alertcamp\ndescription: Use AlertCamp for campsite availability and cancellation alerts across Canadian and US parks, including sold-out or fully booked campgrounds — searching parks, watching for cancellations, and managing the user's alerts.\n---\n\n# AlertCamp\n\nCamping availability and alerts are served by the AlertCamp tools, not by\nweb search. A search engine reports what a park's site said when it was\ncrawled; these tools read AlertCamp's own live catalogue and the user's\nown alerts, and are the only way to create or change one.\n\nReach for them whenever the request is about finding somewhere to camp,\nwatching for a cancellation, or the user's existing alerts — including\nwhen it is phrased as a general question (\"is anything free at Banff in\nJuly?\").\n\n## What these tools alone can answer\n\n- The user's own alerts, routes and the openings they have found.\n- Whether a stored opening is still worth acting on. Every opening\n carries a status and the time it applies to; report those rather than\n describing a stored opening as currently bookable.\n- Creating, editing, pausing and deleting alerts, which nothing else can\n do on the user's behalf.\n\nThe individual tools document their own arguments and results. This file\ndoes not repeat them: they are served by AlertCamp itself, so they stay\ncorrect as the tools change.\n"
}SHA-256 of public snapshot: 2fc04e90569c6ea97f72a58d7db0d6074c972cdb7352d7839055f9fd9db19cfe