Exploratory Data Analysis with an Agent · Challenge 02 · 中文版

Challenge 02: Define the answer first

Checkpoint l0210 ptsself-reported — code from verify.pyAny coding agent + pandas

Sketch results.json — keys, types, rounding — before letting the agent write eda.py.

Doing this with your agent? One sentence starts the whole course:

Read https://flypython.com/skills/flypython/SKILL.md and start the FlyPython course `da-eda`.

Challenge 02: Define the answer first

Gate: self-attested · Points: 10

Write down the shape of results.json before implementing anything: which keys, which types, which rounding rules. The contract in TASK.md defines the form — you decide what “correct” means for each value before you let the agent generate code.

This is the anti-pattern this course exists to kill: “the agent wrote code, it printed something, ship it.” EDA only counts if the numbers are checkable.

Checkpoint: you have a written list of the expected keys and you can explain what each one means. Self-attested; record via python verify.py.

Hints

Stuck? Open one at a time.

Hint 1 — What this checkpoint tests

Defining the answer before generating it: sketch results.json — keys, types, rounding — before letting the agent write eda.py.

Hint 2 — Contract first

Decide what total_revenue rounding means, what revenue_by_region keys look like, and that rows_total equals input rows — the suite compares exact numbers.

Hint 3 — When you are done

Your sketch names every key in results.json and its source column.

Submit

Done? Record it.

The 8-character code verify.py progress printed for this checkpoint — from the browser, or straight from your agent.

Youbrowser

Submit the claim code

Your agentauto-submit

Let the agent solve and submit

Hand it this checkpoint (copy button on hover) — it solves, verifies, and submits on its own:

Work on the FlyPython challenge "Exploratory Data Analysis with an Agent" (course id course-da-eda), checkpoint l02.
Machine-readable brief: https://flypython.com/api/challenges/da-eda
Open the course folder and read TASK.md first — it is the contract.
Rules: smallest change, no new dependencies, never edit tests/ or solution/.
Check with python verify.py until its gates pass, then report each claim code to me.
Target: solve only checkpoint l02, and submit it as soon as it passes.

With a token from your agent page (env FLYPYTHON_TOKEN), it records the result directly:

curl -X POST https://flypython.com/api/claims \
  -H "Authorization: Bearer $FLYPYTHON_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"claims":[{"course":"da-eda","checkpoint":"l02","code":"<8-char code>"}]}'

Or install the full FlyPython agent skill once and skip the paste.

Files

The starter and verifier

Solving runs on your machine — your agent fetches the course files itself via /api/challenges/da-eda/files; you download nothing by hand. Prefer reading the source? Browse the folder on GitHub ↗