Yandex Kit skills for store management
kit-skills
Yandex's official skill set: catalog, prices, stock, orders, storefront and a weekly checkup for a Yandex Kit store, through Claude Code or Codex
High risk
We rate an entry high when the tool writes to external systems, handles money, production databases or secrets, or runs arbitrary commands. The CLI installs it only with your consent.
Why this level
- Can change prices, stock, orders, promo codes and publish the storefront of a real store
- The store token is passed in chat when the session has no secrets support
Install
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/kit-skillsDetects the agents on your machine, checks the risk and pins the version.
Other ways to install
Run one by one in the Claude Code chat
/plugin marketplace add yandex/kit-skills
/plugin install kit-skills@kit-skillsIn Claude Code, run /plugin marketplace add yandex/kit-skills and /plugin install kit-skills@kit-skills, or clone yandex/kit-skills and run python3 install.py, then ask the agent to connect your Yandex Kit store to set up the token.
Other ways from the author
/plugin marketplace add yandex/kit-skills
/plugin install kit-skills@kit-skillsInstalls all four skills at once; update with /plugin update.
This is third-party code. Review the repository files before installing.
What it does
The plugin installs four skills that work together. yandex-kit-cabinet is the entry point: it sets up the store token and, through the public api.kit.yandex.net API, manages the catalog, prices and stock, orders, promo codes and discounts, collections and webhooks, and also queries the cabinet's built-in assistant for sales analytics and help. kit-store-checkup is read-only and runs a weekly review finding problems: products with no photo, price or dimensions, low stock, stuck orders, duplicate SKUs, then hands fixes to yandex-kit-cabinet. kit-storefront-constructor reads and edits storefront pages and sections in a local draft and publishes the result. kit-custom-sections builds a custom storefront section from a catalog of verified patterns offline, with no token, and prints the commands for kit-storefront-constructor. All skills use only the documented public API, with no browser automation.
Who it is for. For owners and managers of Yandex Kit online stores who want to run their catalog, orders and storefront through an agent instead of the cabinet UI.
Good fit when
- You need to bulk-update prices, stock or product cards in Kit
- You want a weekly store checkup for problems without manually going through the cabinet
- You want to assemble and publish a custom storefront section without hand-coding it
Not a fit when
- Your store is not on Yandex Kit: the skills work only with this builder
- You need features absent from the cabinet's public API: the skills deliberately do not emulate a browser
Example request
Check my Yandex Kit store: which products have no photo or are low on stockLimitations
You need a store API token, one token per store. If the agent runs on a server with no environment or secrets settings, the token has to be passed directly in chat and stays in the conversation history. Python 3 must be installed; there are no other dependencies. Some operations require explicit confirmation under a read-before-write rule before creating, changing or deleting data.
How to disable. In Claude Code, run /plugin uninstall kit-skills; for a manual install, delete the skill folders from ~/.claude/skills/ or ~/.codex/skills/.
Security check
- Can change prices, stock, orders, promo codes and publish the storefront of a real store
- The store token is passed in chat when the session has no secrets support
README in short
The README describes the four skills and their purpose, installation as a Claude plugin via the marketplace or with the install.py installer for Claude Code and Codex, support for Windows, macOS and Linux with Python 3 as the only dependency, and a detailed protocol for obtaining the API token depending on whether the agent runs locally or on a server. It covers two token-entry paths: a local one-time page at 127.0.0.1 or passing it through environment variables and chat.
SKILL.md
---
name: yandex-kit-cabinet
description: >-
Manage a Яндекс.Кит (Yandex KIT) e-com store through the public API
(api.kit.yandex.net) — catalog (категории, товары, продукты), цены и остатки,
заказы, промокоды/скидки/подарки, коллекции, бейджи, вебхуки. Also asks the
store's built-in AI assistant: the data-analyst agent answers questions about
this store's own data and builds arbitrary reports from a prompt, and the
support agent answers how-to questions about the cabinet from the
documentation. Prefers the public API; never scrapes the UI.
user-invocable: true
allowed-tools: Bash(scripts/kit.py:*)
---
# Яндекс.Кит cabinet
Agent guide for managing a Яндекс.Кит e-com store through its public API
(https://api.kit.yandex.net, docs: yandex.ru/dev/kit/ru/). This skill is the
bootstrap entry point of the Yandex Kit Skills project.
## Hard rules (always)
1. Public API first. Use documented public API endpoints. Do not scrape
the web cabinet or automate a browser.
2. Read-before-write. Any create/update/delete against the store requires
reading current state first.FAQ
Does every skill need a token?
No, kit-custom-sections works offline without a token; the other three require the store token.
Where does the token go when the agent runs in the cloud?
Preferably into the session's KIT_TOKEN environment variable; if that is unavailable, the token is passed as text or a file in the chat.
Related
Salesforce's official DX MCP server: work with orgs, metadata, data, users and Apex tests from your agent
YouGile MCP by Indalo
YouGile MCP
Full 65-operation YouGile API coverage with configurable permissions, write confirmation and a shared company rate limit
Bitrix24 portal MCP server
MCP-сервер портала Битрикс24
Bitrix24's official per-portal MCP: an external agent uses OAuth or a token to read and change tasks, deals, meetings and mail
A local-first set of Codex skills and a read-only CLI that turns your own WeChat history into search, digests, follow-ups and opportunity tracking