citilink-connector — Claude Code skill: search and install
The citilink-connector Claude Code skill searches Citilink and reads product pages. It activates for requests about Citilink products or prices.
MIT ★ 203 updated 2026-10-19
npx skills add Vladimir-Human/ru-marketplace-mcp --skill citilink-connector -a claude-codeWhat citilink-connector does
The skill searches Citilink and extracts product names, current and previous prices, and availability from product pages. It reads the rendered DOM instead of decoding gRPC-web. Use citilink_search(query) for search results and citilink_card(product_url) for a product page.
It requires the operator’s Chrome connected over CDP and must run from that machine; Citilink returns HTTP 429 from datacenter addresses. If Qrator presents a challenge, pass it in the scraping Chrome and retry. A missing usable price is returned as null, not zero.
To install for Claude Code, run npx skills add Vladimir-Human/ru-marketplace-mcp --skill citilink-connector -a claude-code. The skill file is at ~/.claude/skills/citilink-connector/SKILL.md.
What it helps with
- search Citilink for a product by text
- read a product’s current price and availability
- retrieve a product’s previous price
- inspect a Citilink product page
Example prompts for the agent
- Find a Lenovo laptop on Citilink.
- Read the current and previous prices from this Citilink product page.
- Check whether this Citilink product is available.
How to install citilink-connector
1Skills CLI (Vercel)
npx skills add Vladimir-Human/ru-marketplace-mcp --skill citilink-connector -a claude-code2Manually: put the files in place
~/.claude/skills/citilink-connector/SKILL.mdCopy the whole skill folder; for one project use .claude/skills/citilink-connector/
1Skills CLI (Vercel)
npx skills add Vladimir-Human/ru-marketplace-mcp --skill citilink-connector -a codex2Manually: put the files in place
.agents/skills/citilink-connector/SKILL.mdFor all projects use ~/.agents/skills/
1Skills CLI (Vercel)
npx skills add Vladimir-Human/ru-marketplace-mcp --skill citilink-connector -a cursor2Manually: put the files in place
.cursor/skills/citilink-connector/SKILL.mdCursor also reads .agents/skills/ and .claude/skills/
1GitHub CLI
gh skill install Vladimir-Human/ru-marketplace-mcp skills/citilink-connector2Manually: put the files in place
.github/skills/citilink-connector/SKILL.md1Skills CLI (Vercel)
npx skills add Vladimir-Human/ru-marketplace-mcp --skill citilink-connector -a gemini-cli2Platform CLI
gemini skills install https://github.com/Vladimir-Human/ru-marketplace-mcp --path skills/citilink-connectorManually: put the files in place
.devin/skills/citilink-connector/SKILL.mdThe legacy .windsurf/skills/ path still works
Skills CLI (Vercel)
npx skills add Vladimir-Human/ru-marketplace-mcp --skill citilink-connector -a opencodeClaude.ai
Zip the folder and upload it in Settings → Capabilities → Skills
Step by step, with commands for each platform: How to install skills in Claude Code: five ways
Questions about citilink-connector
How do I install citilink-connector in Claude Code?
Run npx skills add Vladimir-Human/ru-marketplace-mcp --skill citilink-connector -a claude-code. The installed skill file is at ~/.claude/skills/citilink-connector/SKILL.md.
What does citilink-connector do?
It searches Citilink and reads product names, prices, and availability from product pages. The extraction uses the rendered DOM in Chrome over CDP.
What does citilink-connector need to run?
It needs the operator’s Chrome connected over CDP and must run from that machine. If Qrator shows a challenge, pass it in that Chrome before retrying.
Source text
SKILL.md · MIT
--- name: citilink-connector description: Use this skill when the operator needs Citilink electronics data — search or a product card. Trigger on "ситилинк", "citilink", "ситилинк цена". Always needs the operator's Chrome over CDP (Qrator rate block + gRPC-web). Skip for non-Citilink tasks. --- # Citilink Connector Reads Citilink inside the operator's Chrome over CDP. The whole domain answers HTTP 429 (stricter than DNS), and its data transport is gRPC-web — a binary protobuf protocol that is not worth reversing. A real Chrome passes Qrator and renders the pages, so the connector reads the DOM instead. ## When to use - Search Citilink by text - One product's price, old price, availability ## Tools available - `citilink_search(query)` — tiles from the rendered search page - `citilink_card(product_url)` — one card. The URL carries `/product/<slug>/`, where the slug ends in a numeric id: `/product/noutbuk-lenovo-2169270/`. **Not an MCP tool:** `citilink_selfcheck()` is a tri-state canary. It is CLI-only — `marketplace-mcp doctor` runs every connector's canary at once. ## Why the price used to come back null Citilink renders the currency glyph in a **separate element** from the digits: ```html <span data-meta-price="59990"><span>59 990</span><span>₽</span></span> ``` The old extractor filtered text lines for `руб|₽` and so never saw a line carrying both. Title parsed, price did not — on every product. ## Read the data-meta attributes, not the class names Citilink's class names are build-hashed (`app-catalog-51bw0j-…`) and change with every deploy, so they are useless as selectors. The site publishes a stable `data-meta-*` contract for its own analytics, and that is what the extractor keys on: | attribute | holds | |---|---| | `data-meta-name="Snippet__title"` | the product name anchor | | `data-meta-name="Snippet__price"` | the current price (glyph in a child span) | | `data-meta-name="Snippet__old-price"` | the strikethrough price, no glyph | | `data-meta-price="59990"` | the exact amount, machine-readable | `data-meta-price` needs no parsing and cannot be confused with an instalment or a badge, so it is preferred; the display strings are the fallback. If prices start coming back null, check whether those attributes still exist before touching anything else — a class-name change is expected and harmless, a `data-meta-*` change is the real drift. ## Numbers in a tile that are not the price A tile also carries `- 10%` (discount badge), `в 1356 пунктов` (delivery points), `(от 8 дней)` (delivery estimate), a rating and an opinion count. Only a number attached to the currency glyph is treated as the price. Also note the **first product anchor in a tile is an empty overlay link** — it has no text, so the title comes from the `Snippet__title` anchor. ## Gotchas - gRPC-web is deliberately not reversed: DOM extraction is the maintainable route. - A green `citilink_selfcheck` proves the page rendered and the extractor returned a shape. It does not prove the numbers are right — for that, open the product page in the same Chrome and compare. - From a datacenter address the domain answers 429, so nothing can be verified there. This connector only means anything from the operator's own machine. - A Qrator page that loads with HTTP 200 answers `challenge_required`: open citilink.ru in the scraping Chrome, pass the check, retry. It is never cached and never returned as a product. - A missing price is `null`, never `0`: `price_rub: null` means Citilink had no usable price for the tile — treat it as no data, never as a free item. ## DSH activation In DeepSeek Harness the default profile mounts `compare-mcp`, which exposes exactly 4 tools: `compare_prices`, `compare_sources`, `compare_verify_offer` and `compare_browser_snapshot`. The middle `decision-mcp` profile adds `decision_inspect` (5 tools). This connector's own tools and `marketplace_sources` need `RU_MARKETPLACE_MCP_FULL=1` and a profile restart; do not call them in the default mode.
© Vladimir-Human · MIT · Vladimir-Human/ru-marketplace-mcp