Jinkō Model SDK Workflows

Use this skill for technical model construction and editing through the SDK. Keep the scope on SDK mechanics and model validity, not biological plausibility.

Core Rules

• Prefer editing an existing model over recreating a model from scratch.
• Start a new model only when the user explicitly needs one, using client.create_empty_model().
• Favor high-level component methods; do not build raw model payloads unless the typed SDK surface cannot express the requested edit.
• Favor model.components.batch(version_name=...) for component changes so related edits are committed as one model version.
• Treat a complete model as one with no error-level diagnostics and a successful simple_solve() for relevant outputs.
• Report diagnostics or solve errors clearly and ask whether the user wants them fixed.

Project Folder Hygiene

• Prefer creating models inside a dedicated Jinkō folder instead of the project root. At the start of a workflow, ask for or propose a folder name, for example YYYY-MM-DD-<experiment-name>.
• Reuse an existing exact-match folder when possible: client.folders.get_by_name(name, exact_match_only=True).
• If the folder does not exist, create it only after user confirmation or when a script is run with --apply.
• Resolve one folder object or folder id, then pass folder=folder to SDK creation calls that support it.