Upstage Studio Toolkit

Customer-facing tooling for working with an Upstage AI Studio document-processing Agent — running documents at scale, editing and versioning your schema, and scoring extraction accuracy. Everything here is self-contained Python 3.8+ (standard library only) and ships in two forms for two audiences.

Two delivery paths

Path	For	What's in it
skill/upstage-studio/	Technical / AI-native users (drive it with Claude, Codex, etc.)	The Claude skill: API reference, schema-editing and scoring guides, a minimal run_agent.py example, the score.py accuracy scorer, worked examples, and the batch CLI as its at-scale engine.
gui/	Non-technical users who'd rather click than code	The batch CLI plus a local web GUI (upstage_batch_gui.py) — browse to a folder, click Run, watch progress, browse results.

Both are packaged as standalone zips by build.sh (see below).

Single source of truth (no fork/fracture)

The batch CLI, core/upstage_batch.py, is the one canonical copy. Both delivery paths use it, but neither keeps its own edited version — build.sh stamps the canonical file into each artifact at build time. So:

• Edit only core/upstage_batch.py. The copies in skill/.../scripts/ and gui/ are build outputs (git-ignored) and get overwritten on every build.
• Each delivered zip is still fully self-contained — customers never need to assemble anything.

core/upstage_batch.py          ← edit here (the only source)
skill/upstage-studio/          ← the skill (run_agent.py + score.py are skill-owned)
gui/upstage_batch_gui.py       ← the web GUI
build.sh                       ← assembles dist/upstage-studio.zip + dist/upstage-batch-gui.zip

Build & deliver

./build.sh
# → dist/upstage-studio.zip       (send to technical users)
# → dist/upstage-batch-gui.zip    (send to non-technical users)

Security & privacy posture

• No secrets or customer data in this repo. .gitignore blocks logs, run outputs, results/, *.rtf, and anything key-shaped. Keep API keys and real document outputs out of the tree entirely.
• The GUI serves only loopback requests (validates the Host header), fetches no third-party assets, and passes the API key to the batch process via the environment rather than the command line.
• API keys are read from UPSTAGE_API_KEY (or --key), never hard-coded.

License

MIT — see LICENSE.