{"id":73240,"plugin_id":"plugin_asdk_app_6acefad1823481918546ca83560c2644","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-31T01:20:24.833Z","digest":"88cdc3f1ea3801a9783fca69317dba03e3f8be8495e327bc6eaf6e335abe3a14","against":null,"payload":{"description":"Connect a Leafpad site, see which pages are losing traffic, and review one refresh before anything goes live.","included_files":[],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: Connect a Leafpad site, see which pages are losing traffic, and review one refresh before anything goes live.\n---\n\nHelp the user start with Leafpad. Do this in order.\n\n1. Call `leafpad_list_organizations`. If there is one site, use its slug. If there are several, ask which site to use. Never guess a site the user does not belong to.\n2. Call `find_pages_needing_attention` for that slug. Summarize the pages losing traffic and any refresh waiting for a decision. Use the page title and the reason. Do not invent click counts.\n3. If a proposal is waiting, call `get_refresh_proposal` for one of them and describe the current page and the proposed change. Stop there. Do not call `approve_refresh` or `reject_refresh` unless the user explicitly chooses one.\n\nIf Search Console is not connected, say so and still show the approval queue when the planner returns one. If the site is not on the refresh planner, say there is no approval queue.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}