{"id":70635,"plugin_id":"plugin_asdk_app_6ae1d1696bd081918cb8e03725560889","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-29T12:08:03.212Z","digest":"59721418ed42d4c4ac031075448c9d9e83df7e82c14ad6c3464757f4bc72bbb8","against":null,"payload":{"description":"Prepare a source-qualified brief of held EIA plant/fuel-facility and DOE NETL/HIFLD transmission-line records near a public research point, distinguishing mapped facilities, generator inventory, source dates and approximate distances from actual availability or site suitability.","included_files":[],"name":"nearby-energy-records","skill_md_contents":"---\nname: nearby-energy-records\ndescription: Prepare a source-qualified brief of held EIA plant/fuel-facility and DOE NETL/HIFLD transmission-line records near a public research point, distinguishing mapped facilities, generator inventory, source dates and approximate distances from actual availability or site suitability.\n---\n\nUse this workflow to research power-plant and fuel-facility records around a user-supplied public research point. Never request a home address, infer a device location, geocode a personal address or solicit a precise personal location. If coordinates are missing, ask for a public city-center reference point or another nonpersonal research scope. State supplied latitude, longitude and radius without expanding them silently.\n\nRead `describe_energy_layers` to establish which held EIA datasets and facility types are actually available, their separate source periods and geometry/field limits. Transmission records come from the separate DOE NETL-hosted HIFLD layer, not EIA. Do not describe unsupported substations, service territories or environmental-enforcement records. These are energy inventory sources, not EPA enforcement records. The preliminary August 2026 generator workbook and map-layer vintages are distinct; never label every layer August 2026 or current.\n\nUse `find_power_plants_near_point` for plant records and `find_fuel_facilities_near_point` for the supported fuel types requested. Preserve the schema's radius and limit bounds; validate latitude/longitude and reject invalid inputs before calling when apparent. Do not silently clip an invalid radius. Choose optional energy-source/facility-type values only from the actual schema/source catalog, preserving published codes rather than guessing labels. State which layers were searched. Do not call every layer or enlarge the radius merely to manufacture matches.\n\nLead with the queried scope and matching-record count, then the displayed examples. Preserve plant/facility identifiers and source-specific names/operator fields exactly; generator counts are not plant counts. Explain when capacity measures originate from generator inventory versus a mapped plant record. Nameplate MW, net summer MW and storage energy MWh must remain separate with missing values intact. Fuel-facility values retain their own source units: storage volumes, daily throughput/processing and annual production quantities are different measures and must not be added together. Report a historical throughput value only when supplied, with its unit and period. Do not infer generation, throughput, emissions, current operating status, ownership or available capacity from the location or name. Plant coordinate exclusion counts apply to the inventory, not just the query circle; disclose missing/conflicting-coordinate exclusions without inventing their locations.\n\nDistances are references to held mapped locations, not surveyed setbacks or authoritative nearest physical features. Respect the returned ordering even where rounded distances tie. Separate returned rows from total matching records and any caps; a bounded search or incomplete layer is not a complete physical inventory. A facility in one source and a nearby corridor in another are not an established connection. Do not combine sources by name or proximity into an unsupported asset identity.\n\nCite each dataset's source URL and vintage, original download date and current held-read time separately. Explain differing periods across sources. Missing descriptions/coordinates/values remain unknown; a successful no-match applies only to that selected held scope. An error, missing asset or unavailable field is not zero infrastructure and does not establish safety or suitability.\n\nEnd with the answer's practical boundary: these records support public infrastructure research, not a property decision, environmental clearance, service availability, interconnection study, financial recommendation or engineering/safety/insurance certification. For authoritative capacity or site decisions, direct the person to the relevant operator or qualified authority without promising acceptance. Keep the response useful with the supported inventory rather than merely listing disclaimers.\n\nWhen electric transmission lines are requested, use `find_transmission_lines_in_area` with the supplied public point/radius or valid noncrossing research box. Do not automatically fetch them for unrelated plant/fuel questions. State the full matched hosted-record count, display limit and returned examples separately. Preserve reported owner/status, voltage kV, voltage class, inferred-voltage flag and unknown values. Negative numeric sentinels are unknown, not zero kV. kV is electrical voltage, not generation/transfer MW, spare capacity or connection availability. NETL credits HIFLD2022, retrieved2023; service edit date and GovBot download/read dates are distinct. Query geometry is generalized at offset0.0005degrees with5decimal serialization; neither establishes source accuracy. Do not join a nearby line to a plant as a connected system or infer who supplies a property. Retain source-specific credits, including OpenStreetMap contributor attribution when supplied. Historical/live outages and restoration estimates are excluded.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}