Ozon store analytics skill for Codex
Ozon Store Analytics Skill
A read-only Codex skill for Ozon store analytics: impressions, product views, conversion, orders, delivery, cancellations, returns and search ranking
- 2 ★ on the repository
- Last commit
Extended access
Why this level
- Stores an Ozon Seller API key locally and reads store data through it
- Reads the seller's financial and operational metrics, though with no write access
Install
- Works in
- Services
In your terminal, with SkillFoxx CLI
npx skillfoxx add skills/ozon-store-analytics-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.
- Stores an Ozon Seller API key locally and reads store data through it
- Reads the seller's financial and operational metrics, though with no write access
This is third-party code. Review the repository files before installing.
What it does
The skill calls the Ozon Seller API using read-only methods and pulls store and product impressions, product page views, add-to-cart, conversion, orders, revenue, delivery, cancellations, returns and search ranking. Results can be shown in the chat, exported to Excel, or scheduled for a daily run. On first use it asks what to focus on, the date range and output format, then asks for the Ozon Client ID and API key: the keys are verified with one read-only call and stored only in a local .ozon/credentials.json excluded from git.
Who it is for. For Ozon sellers who need regular store analytics without giving the agent any ability to change products, prices or stock.
Good fit when
- You need impressions, conversion and sales analytics for an Ozon store
- You want a daily automated metrics report
- You need to merge SKU variants of one product by model_id
Not a fit when
- You need to change prices, stock or product cards: the skill only reads
- You need the exact official click-through rate: without it the skill marks derived metrics as approximate
- You need a client other than Codex
Example request
Use $ozon-analyze-store and show how my store's conversion and orders changed over the last weekLimitations
The README is in Chinese and needs a read-scope Ozon Seller API key. The skill does not claim an official CTR when Ozon does not return one, and explicitly marks derived metrics as approximate rather than official. Installation is documented only for Codex.
How to disable. Remove the skill from the Codex project skills directory and delete .ozon/credentials.json with the keys.
FAQ
Can the skill change a product or its price?
No, every call uses read-only Seller API methods.
Where are the keys stored?
In a local .ozon/credentials.json file inside the project, excluded from git and never sent anywhere.
Discussion
No questions or reviews yet.
Related
All Ozon toolsOzon seller analytics skill
ozon-seller-skill
A skill with two dozen Python scripts over the Ozon Seller API: stock, turnover, financial reports, product cards and reviews
Ozon selling advisor for Codex
Ozon Expert Skill
A Codex skill with baseline Ozon selling knowledge: automated listing uploads, Ozon-specific keyword optimization and operational diagnostics
Ozon keyword research and listing optimizer
Ozon 搜索词调研与商品卡优化工具
A skill turns a search-query export from the Ozon seller dashboard into an Excel keyword report and a Word title-optimization report
Product Collect for Ozon
Product Collect
A Codex skill reads a product page and assembles facts and Chinese marketing copy for an Ozon listing, inventing nothing
Ozon auto-listing skill
auto-listing-skill
A Codex skill locates the shop's working folder, fills price and category workbooks, builds an image zip, and logs the Ozon auto-listing task
A bundle of four skills for an Ozon seller: product sourcing via a third-party data tool, logistics pricing, auto-listing, and 1688 supplier lookup
README in short
The Chinese README describes a project-level Codex skill that analyzes an Ozon store purely through the read-only Seller API: coverage (impressions, views, conversion, orders, delivery, cancellations, returns, search ranking), output format (chat or Excel), an optional daily run, and a rule against presenting derived metrics as an official CTR.