Using the Skills

Start with the evs-data skill

For the best results, call the evs-data skill by name once, at the start of the session, together with what you plan to do.

/evs-data-tools:evs-data We will be creating EVS data files from this folder.

This works far better in most agents, including Claude Desktop and Codex, than waiting for the skills to load on their own. Once evs-data is loaded, it brings in the skill for each file type or conversion as the work needs it. After that, describe each task in plain language and attach or point to your data.

Work in your project folder

With Claude or Codex, we recommend working in Claude Code or Codex, opened in the folder that holds your project data, rather than in a chat. The agent can then find and read the spreadsheets, PDFs and other data in that folder by itself, and write the EVS files next to them. In a chat you have to drag in each file one at a time.

Example Prompts

  • “Inspect the Excel spreadsheets and PDF files in this folder. What EVS data files can we create from these inputs?”
  • “Make an APDV file from samples.csv for benzene and TCE.”
  • “Make an EVS file from samples.xlsx for benzene and TCE.”
  • “Convert site.geo to a GMF file.”
  • “Validate borings.lsdv before I load it in EVS.”
  • “Turn this lithology log spreadsheet into a PGF file.”
  • “Convert lithology.pgf to LSDV, then to LPDV.”
  • “Build a GEO file from site.pgf. Here is the order of the layers from the top down.”
  • “Build a GEO file from site2.pgf. Attempt to pick the best layer ordering automatically.”
  • “Why does EVS reject this AIDV file?”
  • “Create a conversion report, including all assumptions and decisions made during our data file creation.”

Your agent asks before it guesses

EVS files must be exact, so the skills tell the agent never to assume a value that is not in your data. Expect questions like these before the agent writes a file.

  • Units. If the source data does not state them, the agent asks for coordinate units (meters or feet) and analyte concentration units (such as mg/L, ug/L or ppm). X, Y and Z in one file must use the same unit.
  • Elevation or depth. The agent asks whether Z values are elevations or depths below ground surface, and suggests an answer based on your data, such as a column named SampleDepth or values that increase down a boring.
  • Zero values. In an EVS file 0.0 is a measured value, not a non-detect. When a zero appears in units that EVS log processes, such as mg/kg or ug/L, the agent asks whether to write it as a non-detect or keep 0.0. Zeros in other units, such as pH or temperature, are kept.
  • Anything missing or ambiguous. Boring IDs, analyte names, layer names and other details are confirmed with you rather than assumed.

The agent also keeps your numbers as given and does not round coordinates, depths or values.

Conversions

Some conversions keep all of the data, some lose detail and some need your interpretation, such as turning lithology into geologic layers. The agent tells you which kind of conversion you are asking for, warns you about any data that will be lost and checks the converted file.