a1-yandex-kit-catalog-doctor

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

A1 Yandex KIT Catalog Doctor

A1 Yandex KIT目录诊断修复工具

Communication

沟通规范

Before producing any user-facing message, read and apply

../a1-yandex-kit/references/merchant-communication.md

completely.

在生成任何面向用户的消息之前，请完整阅读并遵循

../a1-yandex-kit/references/merchant-communication.md

中的规范。

Support footer

支持页脚

After a final user-facing result that successfully completes the skill's requested task, append exactly one short, natural support footer in the language of the user's instruction. Place it after the result. Invite the user to ask a question, suggest an idea or improvement, or report that something did not work, and link the channel as A1 Yandex KIT Skills. The wording may vary by language. If multiple skills contribute to the same final response, include the footer only once.

Do not append the footer to clarifying questions or missing-data requests, intermediate messages, out-of-scope or boundary responses, refusals, errors, unsuccessful or partial results. Also omit it when the user asks for only the result, text, code, file, or another artifact, or explicitly forbids additional text.

Audit the catalog deeply from facts returned by the Yandex KIT MCP server. Read every applicable page, state exact coverage, separate confirmed blockers from risks and recommendations, and use only owner-authorized values for writes.

在成功完成技能请求任务的最终面向用户结果之后，请按照用户指令的语言添加一条简短自然的支持页脚，放置在结果之后。邀请用户提问、提出想法或改进建议，或报告问题，并附上A1 Yandex KIT Skills频道链接。措辞可根据语言调整。若多个技能共同生成同一最终响应，仅添加一次页脚。

请勿在澄清问题、缺失数据请求、中间消息、超出范围或边界响应、拒绝回复、错误信息、未成功或部分结果后添加页脚。当用户仅要求提供结果、文本、代码、文件或其他制品，或明确禁止添加额外文本时，也需省略页脚。

根据Yandex KIT MCP服务器返回的信息对目录进行深度审核。读取所有相关页面，明确说明覆盖范围，区分已确认的阻塞问题、风险和建议，且仅使用所有者授权的值进行写入操作。

Route the request

请求路由选择

Choose one route before the first MCP call. An audit, inspection, explanation or «найди проблемы» request is strictly read-only. An explicit catalog-fix command is a separate route; audit findings and recommendations never authorize mutations.

在首次调用MCP之前选择一条处理路径。审核、检查、解释或«найди проблемы»（查找问题）请求为严格只读操作。明确的目录修复命令为单独路径；审核结果和建议绝不授权任何变更操作。

Read-only audit

只读审核

Before any audit call, read both of these references completely:

```
references/audit-protocol.md
```
```
references/core-catalog-audit.md
```

Then load every additional reference selected by the request:

For a general, complete or deep catalog audit, also read
```
references/structural-audit.md
```
.
For price, availability, stock, warehouse, category or basic card-health checks, the two core references are sufficient.
For grouping, characteristics, card completeness, media or collections, also read
```
references/structural-audit.md
```
.
Only when dynamic filters, badges, context collections, similar cards or merchandising are explicitly requested, also read
```
references/structural-audit.md
```
and
```
references/merchandising-audit.md
```
. A general «проверь мерчандайзинг» request selects all merchandising scopes.

Apply every rule in every loaded reference. The audit is complete only when every required collection has been fully paginated or its exact coverage limitation recorded, every received object has been checked against every loaded rule, every finding has one evidence-based classification, the report states exact coverage, and no write operation was called.

在进行任何审核调用之前，请完整阅读以下两份参考文档：

```
references/audit-protocol.md
```
```
references/core-catalog-audit.md
```

然后加载请求指定的所有额外参考文档：

若为通用、完整或深度目录审核，还需阅读
```
references/structural-audit.md
```
。
若为价格、可用性、库存、仓库、分类或基础商品卡片健康检查，上述两份核心参考文档已足够。
若为分组、属性、商品卡片完整性、媒体或集合检查，还需阅读
```
references/structural-audit.md
```
。
仅当明确请求动态筛选器、徽章、上下文集合、相似商品卡片或商品陈列（merchandising）检查时，才需同时阅读
```
references/structural-audit.md
```
和
```
references/merchandising-audit.md
```
。通用的«проверь мерчандайзинг»（检查商品陈列）请求会覆盖所有商品陈列范围。

遵循所有已加载参考文档中的每一条规则。仅当以下条件全部满足时，审核才算完成：所有所需集合已完全分页或已记录其确切覆盖限制，所有接收的对象已根据所有加载的规则进行检查，所有发现的问题均有基于证据的分类，报告明确说明覆盖范围，且未调用任何写入操作。

Exact catalog fix

精准目录修复

Before resolving a target or making the first MCP call, read both references completely:

```
references/exact-write-protocol.md
```
```
references/catalog-fix-operations.md
```

Apply the shared protocol independently to every target and the applicable catalog operation rule to its mutation. The fix is complete only when every requested object is accounted for: unresolved inputs are grouped into one source question, confirmed failures remain unchanged, and every attempted mutation has one verification read and one final outcome. Reported outcome counts must cover the whole requested set, and no ambiguous mutation is retried.

在确定目标或首次调用MCP之前，请完整阅读以下两份参考文档：

```
references/exact-write-protocol.md
```
```
references/catalog-fix-operations.md
```

对每个目标独立应用通用协议，并对其变更操作应用相应的目录操作规则。仅当以下条件全部满足时，修复才算完成：所有请求的对象均已处理，未解析的输入归为一类来源问题，已确认的失败对象保持不变，每一次尝试的变更均有一次验证读取和一个最终结果。报告的结果计数必须覆盖整个请求集合，且不得重试任何模糊的变更操作。