{"id":64522,"plugin_id":"plugin_asdk_app_6acce47e2a7c819182be618ea28e49db","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-27T01:02:30.445Z","digest":"d186cde77f9ad7ca58aec88585939ed55a7a7dd5f54437daa5759ce23327ac4d","against":null,"payload":{"description":"Show a new user what PatchOps can answer and how to ask, using public oil and gas records with named sources.","included_files":[],"name":"get-started","skill_md_contents":"---\nname: get-started\ndescription: Show a new user what PatchOps can answer and how to ask, using public oil and gas records with named sources.\n---\n\nHelp the user start with PatchOps.\n\n1. Explain in one or two sentences that PatchOps reads public oil and gas records: Texas Railroad Commission wells, permits, dossiers, and production; Louisiana SONRIS; New Mexico OCD; Oklahoma OCC; FracFocus disclosures; EIA natural gas and petroleum data; and BLM survey sections.\n2. Offer three starter questions that match their interest, for example:\n   - \"Find active wells operated by Diamondback Energy in Martin County, Texas.\"\n   - \"Show Henry Hub natural gas spot prices for the last 12 months.\"\n   - \"Map the horizontal drilling permits issued in Reeves County this year.\"\n3. Tell them each answer names its source, and that the tools only read public data; they never change anything in any account.\n\nWhen the user asks a question, call the matching PatchOps tool with the operator, county, API number, or date range they gave. Keep every filter they stated. If a result is empty, say so plainly and suggest one specific change, such as a different spelling of the operator name.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}