How do I install the Jinko Sdk Setup skill?

Run npx skillmds@latest add novainsilico/jinko-sdk-setup in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Jinko Sdk Setup safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Jinko Sdk Setup?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Jinko Sdk Setup free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under MIT.

Who published Jinko Sdk Setup?

novainsilico (@novainsilico) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Jinko Sdk Setup by novainsilico — Agent Skill

Name: Jinko Sdk Setup
Author: novainsilico

Jinko Sdk Setup

Authenticate and configure access to a Jinkō project via the jinko-sdk. Use this skill whenever the user wants to connect to Jinkō, install the SDK, set up credentials or a .env file, verify API access, fail-fast check that a JINKO_API_KEY and JINKO_PROJECT_ID work, or debug ConfigurationError, AuthenticationError, or AuthorizationError from the SDK. Do not use this skill for creating models, vpops, protocols, output sets, or trials.

novainsilico dcfef2c 4 files · 4.7 KB Updated Sep 17, 2026

File contents

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.

Workflow

SDK VERSION PREREQUISITE: Run the check below. It ships with the SDK and verifies the installed SDK against every neighboring SDK-dependent skill before API access.

Run the deterministic check and follow its success or error message:

python -m jinko.cli.check_jinko_connection

The script:

Loads .env when python-dotenv is installed.
Redacts sensitive values when showing configuration.
Requires both JINKO_API_KEY and JINKO_PROJECT_ID.
Constructs JinkoClient() from environment variables.
Calls client.auth_check() to prove authentication.
Calls client.search(limit=1, show_table=False, show_table_hint=False) to prove minimal read-only project-item access.
Prints minimal output on success.

Use --show-config only when debugging local setup; it prints presence and redacted values, never the full API key.

After Validation

Once the connection check passes, prefer client.search(...) for project exploration because it gives the user an immediate view across project items.

Use a minimal example like:

from jinko import JinkoClient

client = JinkoClient()
client.search(limit=20, columns="compact")

Use search() when the user wants to:

browse what exists in the configured project
find an item by name or free text
orient themselves before choosing a model, protocol, vpop, or trial workflow

The setup script uses a one-item, non-rendered search() only as its project-read check after authentication. Use a larger interactive search() only for exploration after validation succeeds.

Troubleshooting

Run the check again and act on its deterministic diagnostic. Do not replace it with ad hoc checks or ask the user to share secrets.

---name: jinko-sdk-setupdescription: Authenticate and configure access to a Jinkō project via the jinko-sdk. Use this skill whenever the user wants to connect to Jinkō, install the SDK, set up credentials or a .env file, verify API access, fail-fast check that a JINKO_API_KEY and JINKO_PROJECT_ID work, or debug ConfigurationError, AuthenticationError, or AuthorizationError from the SDK. Do not use this skill for creating models, vpops, protocols, output sets, or trials.license: MIT---# Jinkō SDK SetupUse 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.## Workflow> **SDK VERSION PREREQUISITE:** Run the check below. It ships with the SDK and> verifies the installed SDK against every neighboring SDK-dependent skill> before API access.Run the deterministic check and follow its success or error message:```bashpython -m jinko.cli.check_jinko_connection```The script:- Loads `.env` when `python-dotenv` is installed.- Redacts sensitive values when showing configuration.- Requires both `JINKO_API_KEY` and `JINKO_PROJECT_ID`.- Constructs `JinkoClient()` from environment variables.- Calls `client.auth_check()` to prove authentication.- Calls `client.search(limit=1, show_table=False, show_table_hint=False)` to prove minimal read-only project-item access.- Prints minimal output on success.Use `--show-config` only when debugging local setup; it prints presence and redacted values, never the full API key.## After ValidationOnce the connection check passes, prefer `client.search(...)` for project exploration because it gives the user an immediate view across project items.Use a minimal example like:```pythonfrom jinko import JinkoClientclient = JinkoClient()client.search(limit=20, columns="compact")```Use `search()` when the user wants to:- browse what exists in the configured project- find an item by name or free text- orient themselves before choosing a model, protocol, vpop, or trial workflowThe setup script uses a one-item, non-rendered `search()` only as its project-read check after authentication. Use a larger interactive `search()` only for exploration after validation succeeds.## TroubleshootingRun the check again and act on its deterministic diagnostic. Do not replace it with ad hoc checks or ask the user to share secrets.

Frequently asked questions