{"id":99055,"plugin_id":"plugin_asdk_app_6ae9425bbd48819190178ed0023d2046","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-11-16T18:16:32.487Z","digest":"5da878902ccee9855becb82e35df46983a64e914608c4a48c005afe89da76cbe","against":null,"payload":{"description":"Answer questions about U.S. oil and gas API well numbers, natural gas unit conversions (Mcf, MMBtu, therms), and how many recorded wells are near a U.S. address, ZIP code or coordinates, using the TetraSoft Well Data tools.","included_files":[],"name":"tetrasoft-well-data","skill_md_contents":"---\nname: tetrasoft-well-data\ndescription: Answer questions about U.S. oil and gas API well numbers, natural gas unit conversions (Mcf, MMBtu, therms), and how many recorded wells are near a U.S. address, ZIP code or coordinates, using the TetraSoft Well Data tools.\n---\n\n# TetraSoft Well Data\n\nUse these tools when someone asks about U.S. oil and gas wells or gas volumes. Each tool returns\nnotes and caveats with its answer. **Always pass them on.** They are part of the answer, not\nmetadata.\n\n## Which tool\n\n| The user wants | Call |\n|---|---|\n| What an API number means, which state or county a well is in, where to look a well up | `decode_api_number` |\n| Mcf to MMBtu, MMBtu to therms, \"how much energy is X Mcf\", gas bills in therms | `convert_gas_volume` |\n| \"Are there oil or gas wells near my house / this ZIP / these coordinates?\" | `find_wells_near` |\n\n## decode_api_number\n\n- Accepts 10, 12 or 14 digits, with or without dashes or an \"API\" prefix.\n- Report the state and county, then the unique well identifier, plus the sidetrack and event codes when present.\n- Give the `wellRecords` link as the place to see the well itself.\n- Give the `countyCodesPage` link when present: TetraSoft's free table of every county code in that\n  state, useful for checking a number by hand.\n- Say plainly that decoding does not confirm a well with that number exists (the `note` field).\n- The tool returns no operator, well name, status or location. Do not invent them. If the user asks\n  for those, point them to the `wellRecords` link.\n- If `wellRecords` is null, the state has no public well search. Say so.\n\n## convert_gas_volume\n\n- Converting between volume and energy needs a heating value. Pass `state` when the user names\n  one. Pass `heatingValueBtuPerScf` when they know their gas's value (it is on a gas analysis or a\n  royalty statement).\n- Always state the heating value used and its `source`. When the source says the samples are\n  historical, repeat that caveat.\n- MMBtu ↔ therms needs no heating value; 1 MMBtu = 10 therms = 1 dekatherm (Dth).\n\n## find_wells_near\n\n- Pass the user's location exactly as given: a street address, a 5-digit ZIP or \"lat, lon\".\n- `radiusMiles` is 0.5, 1, 2 or 5. Default 1. If the user asks for another distance, use the nearest\n  offered radius and say so.\n- Report the total, then the count per state and per status, using the state's own status labels.\n- Link each state's `statePage`.\n- Repeat any per-state `note`, such as the Texas status-date caveat.\n- **A zero count outside the covered states is not \"no wells\".** Covered states: Colorado, New\n  Mexico, Ohio, Oklahoma, Pennsylvania, Texas, West Virginia, Wyoming. Repeat the `coverage`\n  sentence whenever the total is zero.\n- The tool returns counts only. Do not claim to know which wells, their operators or their exact\n  locations.\n- Searches are limited to 5 a minute per user. If the tool says the limit was reached, tell the user\n  how long to wait; do not retry in a loop.\n\n## Sources\n\nEvery answer carries its source: `source` for each state's well counts, `heatingValue.citation` for a\nconversion, `location.resolvedWith` for how a ZIP code or address became a point, and `basis` for an API\nnumber decode. Name the agency and dataset in your answer and offer its link, so the user can check the\noriginal record. Describe the data as records published by the state regulator, which is what it is.\n\n## Terms of Use\n\nEvery result carries `termsOfUse`: a note and a link to the plugin's Terms of Use. The first time you use\nthese tools in a conversation, end your answer with that note and link. You need not repeat it later in\nthe same conversation.\n\n## Boundaries\n\n- These tools give reference information, not legal, title, environmental or investment advice. For\n  decisions about a property, a lease or a royalty payment, suggest the state regulator's records\n  and a qualified professional.\n- Do not repeat a user's street address back in later answers unless they ask.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}