wb-api-skill
A Wildberries Seller API reference built on an OpenAPI snapshot the author syncs with the WB portal about monthly
- 2 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- Runs local Python scripts
- Update mode launches a browser and downloads specs from dev.wildberries.ru
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/wb-api-skillDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- Runs local Python scripts
- Update mode launches a browser and downloads specs from dev.wildberries.ru
This is third-party code. Review the repository files before installing.
What it does
The skill keeps a local snapshot of WB OpenAPI specs and a wb.py script to search endpoints and inspect request and response schemas, hosts and auth rules. The script makes no network calls and is not an API client; it gives the agent compact output instead of megabytes of YAML. Before answering, the agent checks the snapshot age and warns if it is older than 30 days. update.py lets you build a fresh snapshot yourself.
Who it is for. For developers of Wildberries integrations who need to rely on current documentation.
Good fit when
- You need a WB endpoint for stocks, orders, supplies or reviews
- You need the request and response schema of a specific method
- You need to generate client code for the Seller API
Not a fit when
- You need a ready client that actually calls the WB API
- You need market analytics rather than API docs
Example request
Which WB endpoint returns seller warehouse stocks and what host does it use?Limitations
Data is current as of the snapshot date. Updating it yourself needs a visible Chrome window and patchright because the WB portal is behind anti-bot protection. WB rate limits come only from operation descriptions.
How to disable. Remove ~/.claude/skills/wb-api or the project .claude/skills/wb-api folder.
FAQ
How do I update the snapshot?
Usually git -C ~/.claude/skills/wb-api pull is enough. Without git, unpack the wb-swagger archive from the latest release over swagger/.
Why is the folder named wb-api?
Claude Code finds the skill by folder name, which must match name in SKILL.md.
Discussion
No questions or reviews yet.
Related
All Wildberries toolsWildberries Seller API skill
Wildberries Seller API - Agent Skill
A Wildberries Seller API reference skill on local Swagger files with search in Russian and English
Official Wildberries Seller API skill
Wildberries API
A skill for the official Wildberries Seller API with local OpenAPI schemas for 286 operations and a guarded api_call helper
Wildberries API skill with 261 methods
wb-api skill
An Agent Skill with a full map of the Wildberries API: 12 modules, 261 methods, reference files and a call script
Wildberries Seller API reference
wb-seller-api-reference
A Claude Code skill with a Wildberries Seller API reference: hosts, rate limits, errors and 18 endpoint families
A conservative CLI and skill for the official Wildberries Seller API: token checks, ping, seller-info and read-only raw requests
A zero-dependency Agent Skill and CLI over the Wildberries API: products, orders, reviews, analytics, multiple stores
README in short
The README describes a reference skill for the Wildberries Seller API with a regularly refreshed spec snapshot. API changes are recorded in releases and CHANGELOG.md. It explains why specs cannot be fetched with plain HTTP and how update.py passes the anti-bot check with patchright, validates files and swaps the snapshot atomically. Offline tests cover the safety logic. Code is MIT; specs belong to Wildberries.
README badge
Original SKILL.md
--- name: wb-api description: Swagger-backed Wildberries seller API reference for WB marketplace integrations. Use when building or debugging code that calls Wildberries/WB seller API endpoints, choosing endpoints, checking request/response schemas, authentication headers, hosts, rate limits, or API capabilities. --- # Wildberries Seller API Локальный снимок OpenAPI-спецификаций в `swagger/*.yaml` — единственный источник истины по этому API. Отвечай по нему, а не по памяти: WB меняет эндпоинты часто, и то, что ты помнишь, скорее всего устарело. ## Порядок работы Помощник требует PyYAML. Если его нет: `python -m pip install -r requirements.txt`. 1. Начинай с компактных запросов к снимку: - обзор разделов: `python scripts/wb.py map` - поиск: `python scripts/wb.py search "<запрос>" --limit 15` - конкретный эндпоинт: `python scripts/wb.py detail <METHOD> <PATH>` - со схемами тела и ответов: `python scripts/wb.py detail <METHOD> <PATH> --schemas` - авторизация, хосты, токены, коды: `python scripts/wb.py protocol` 2. Сырой `swagger/*.yaml` открывай только когда вывода скрипта не хватает: нужны вложенные примеры, значения enum или длинное описание целиком. Целиком файлы не читай — они по 100–350 КБ. 3. Целостность снимка: `python scripts/wb.py validate`. ## Свежесть Перед содержательным ответом по API сверься с `python scripts/wb.py stale`. Снимок старше 30 дней — скажи об этом пользователю прямо: назови дату снимка и предложи `git pull` (снимок в репозитории обновляет мейнтейнер). Если и там несвежо — предложи собрать свой снимок: `python scripts/update.py`. Не делай вид, что данные свежие. ## Правила ответа - Указывай метод, путь, хост, файл-источник (`swagger/NN-name.yaml`), схему авторизации, тип токена и релевантные коды ответов. - Хост бери с самой операции: у WB он разный для разных доменов. Общего хоста нет. - Лимиты запросов WB в машиночитаемом виде не публикует — они описаны текстом внутри `description` конкретной операции. Приводи их оттуда дословно, не выдумывай числа.