{"id":53303,"plugin_id":"plugin_asdk_app_6ad8e0f3c964819190c360445d44f0fd","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T13:53:00.597Z","digest":"36e181183c129a50e19399dce03fa628dd4824756b36e8a0ca2fefda29279aff","against":null,"payload":{"description":"Connect a PageLantern workspace and verify read access after installing the plugin or when the user asks to get started, reconnect, or troubleshoot authorization. Use monitoring for a concrete monitor task once connected.","included_files":[{"relative_path":"agents/openai.yaml","size_in_bytes":440}],"name":"setup","skill_md_contents":"---\nname: setup\ndescription: Connect a PageLantern workspace and verify read access after installing the plugin or when the user asks to get started, reconnect, or troubleshoot authorization. Use monitoring for a concrete monitor task once connected.\n---\n\n# Set up PageLantern\n\nExplain that PageLantern can inspect monitors, settings/history/uptime, graphs and monitoring locations; read existing client reports; and—with additional authorization—run HTTP checks, create HTTP uptime monitors, and pause or resume scheduled monitoring.\n\n1. Check whether the `pagelantern` tools are available. If they are, call `list_monitors` with `page: 0, size: 5` to verify read access. This is a connection check, not a fresh website check. If the user has already requested a concrete action, continue with the monitoring skill after connecting.\n2. If no connection exists or authentication fails, guide the user through the host's connection flow and PageLantern sign-in/workspace authorization. Account credentials stay in that flow. Never request credentials or tokens in the conversation.\n3. Hosted ChatGPT starts with `monitors:read reports:read`. Native Codex uses its registered `pagelantern-codex` client and may offer the server's broader scopes; use the explicit read-only login instructions in the [package guide](../../README.md) when needed. Older grants do not gain `reports:read` automatically and may need renewed consent. Do not claim installation alone completed OAuth or verified a live deployment.\n4. Confirm only what the tool proves: access to the connected workspace, the returned count/page, and available monitor names/status. If the workspace has no monitors, offer to create one when the user supplies an authorized public URL. Do not create, run, pause, or resume a monitor merely because setup was invoked.\n5. When the requested task concerns reports, verify `list_report_packs` separately; a successful monitor list does not prove report permission. Empty report results are valid and do not authorize generation or delivery. Members/viewers see approved reports only.\n\nFor `403` or `insufficient_scope`, explain which scope is missing and that mutations also require Owner/Admin. Reconnect or approve expanded scopes when supported by the host; otherwise follow the guide for a deliberately elevated connection. Do not repeatedly retry unchanged permissions. For expired access, reconnect. For service failures, report that verification is incomplete without claiming the workspace is empty.\n\nFinish with one useful next action based on the user's request, such as viewing recorded health or inspecting a chosen monitor. The release may still require deployment and host acceptance; follow the package status rather than assuming marketplace availability.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}