Question
Closed · Answered

How can I include format validation when asking Buda for a JSON file?

QiangDiao Li

I'd like Buda to deliver a JSON file after organizing some information, so an existing tool of mine can read it. Field names need to stay fixed, numbers should stay numeric rather than become text with units, and missing values should be null.

Besides supplying an example, can I ask it to run checks after generating the file: parsing, required fields, and field types? Would you include those checks in the Skill?

Report
Kelly
Team
· edited

Yes. Beyond an example, have Buda validate after generating, and only hand off the file when checks pass.

(Diagram: agree shape → generate → parse/required/types → deliver only if pass.)

(Local demo: agent session that can run scripts)

Suggested steps

  1. Fix the sample + rules

Provide a minimal JSON sample. State: field names must not change, numbers stay numeric (not "12 USD"), missing values are null, and which keys are required.

  1. Write a real file

Ask for a .json in Drive/cloud storage, not only a chat paste.

  1. Run checks immediately (put this in a Skill)

Parseability, required fields, and types (number/boolean/array). On failure, list the bad fields and rewrite — don’t deliver a broken file.

  1. Package as a Skill for recurring jobs

Sample, required list, type rules, and “rewrite on fail” keep scheduled runs consistent.

How to confirm

  • Your existing tool reads the file with no manual key renames.
  • The check log shows parse / required / type all passed.
  • Deliberately omitting a required field or stringifying a number should block handoff.

Boundaries

  • A sample shows the shape; checks decide whether a bad file may leave.
  • Use null for allowed-missing fields rather than deleting keys (unless your tool allows absent keys).
  • Large payloads stay file + script — don’t rely on eyeballing chat.
Report

Your reply

Sign in to join the discussion. Reading is always open; you only need an account to post.

Sign in