Jinkō SDK Setup

Use this skill for SDK setup and credential checks only. Keep the user focused on proving that Python can authenticate against Jinkō and read one project item list before moving to model, vpop, protocol, output-set, or trial workflows.

BE CAREFUL: the right package is jinko-sdk that export a jinko module. jinko is a different package unrelated to the Jinko SDK.

Credentials

Do this before the connection check. A missing .env is expected when a Jinko MCP server is connected. Do not stop to create one.

JinkoClient() reads credentials from the environment. Export both of these for every SDK command:

1. JINKO_PROJECT_ID — the id of the project the user is working in. Always set this. Do not invent one.
2. One credential. Prefer JINKO_SESSION_CODE when the Jinko MCP tool get_session_code is available. Use JINKO_API_KEY only when that tool is not available. When both are set, JINKO_SESSION_CODE is the one to use.

Session code

A session code can be exchanged only once. Call get_session_code immediately before each SDK process, including the connection check and every later command. Do not reuse a code that was already passed to a process.