cmw-kb

name	cmw-kb
description	CMW Platform v5.0 knowledge: answer from authoritative documentation, not guesses. Use for customers, partners, and employees whenever the user asks about product behavior, administration, configuration, integrations, APIs, troubleshooting, or "what the documentation says"—even if they do not say "knowledge base" or "KB." Source order: (1) local Markdown under docs/ru only when this Git workspace's remotes match the canonical cbap-mkdocs-ru repo (see references/git_remote_allowlist.md); (2) CMW KB MCP tools if configured; (3) official kb.comindware.ru LLM ingestion .md; (4) GitHub raw on branch platform_v5 under docs/ru via raw.githubusercontent.com (bootstrap from toc.md and guides_toc.md, never the GitHub tree UI alone). Respond in the user's language; keep citations aligned with the source text. If nothing authoritative answers the question, say so—do not invent platform facts.
compatibility	Optional tier-1 local tree: only when Git remotes identify the canonical public documentation repository (arterm-sedov/cbap-mkdocs-ru). Optional MCP over HTTP/SSE (public endpoint). Public HTTPS for the ingestion markdown file and for GitHub raw content. No VPN or company-only URL is required for tiers 2–4. Unrelated repositories may contain docs/ru for other products—never treat those as the Platform KB without the remote allowlist match.

CMW Platform v5 knowledge base

Guide agents to efficient, cited answers about CMW Platform v5.0 using a fixed source priority. This skill is for anyone (internal or external): default to public tiers when the workspace is not the canonical docs clone.

When to use

• Questions about how the platform works, how to configure it, documented limits, official integration paths, or troubleshooting steps that should match the product help.
• User language may be English or Russian; answer in the user's language unless they ask otherwise.

When not to use as the primary path

• Generic programming unrelated to the platform (e.g. "implement quicksort")—use normal coding help.
• Undocumented or release-specific behavior: if sources do not cover it, say so instead of speculating.

Source priority (strict order)

1. Local docs/ru — Only if Git remote allowlist passes (see references/git_remote_allowlist.md) and docs/ru/ exists. Search and read .md files with workspace tools (glob, grep, read file).
2. MCP — If KB-related MCP tools are available in this session: read tool schemas first, then call tools (e.g. get_knowledge_base_articles and any siblings exposed by the server). See references/mcp_client_setup.md.
3. Ingestion markdown — Fetch the official single-file ingestion URL from references/urls.md. If the file is large, locate the right section by headings or partial reads; retry once on transient network or 5xx errors.
4. GitHub raw — Use the raw base URL and bootstrap files from references/urls.md. Open specific articles by path under docs/ru/. Do not scrape the GitHub tree HTML as the primary access method.

If tier 1 does not apply, start at tier 2. If MCP is missing or returns nothing useful, continue to 3, then 4.

Tier 1 detail: Git gate before trusting local files

1. Determine whether the workspace root is a Git checkout (git remote -v or read .git/config if available).
2. If no remote matches references/git_remote_allowlist.md, skip tier 1 entirely—even if docs/ru exists (it may belong to another product).
3. If a match exists, prefer searching under docs/ru/**/*.md for the topic, then read the minimal set of files needed.

Tier 2 detail: MCP

• The server is public; do not send secrets in queries.
• Follow the client rule: inspect MCP tool descriptors before invoking tools.
• If the session has no MCP tools from this server, proceed to tier 3 without stalling.

Tier 3 detail: Ingestion URL

• Full URL: listed in references/urls.md.
• Use efficient retrieval: avoid loading the entire document into context when a heading search or ranged read is enough.

Tier 4 detail: GitHub raw

1. Fetch toc.md and/or guides_toc.md (raw URLs in references/urls.md).
2. Follow links or paths to the relevant .../docs/ru/.../*.md file.
3. Construct URLs as: raw.githubusercontent.com/arterm-sedov/cbap-mkdocs-ru/platform_v5/docs/ru/<relative-path>.md

Language and quoting

• Narrative answer: user's language.
• UI labels, button names, menu paths, and direct quotes: preserve source language (Russian in docs/ru and most KB content). When translating UI names, note that the official UI may show Russian strings.

Citations

• For local files: cite file path (and heading or anchor if helpful).
• For MCP: cite article title or ID as returned by the tool, plus any URL if provided.
• For ingestion: cite section heading or stable fragment if present.
• For GitHub raw: cite repository path on branch platform_v5 (e.g. docs/ru/.../article.md).

Honesty rule

If no tier provides an answer, say that authoritative documentation was not found or not reachable, and suggest:

• Enabling the MCP server (references/mcp_client_setup.md), and/or
• Opening the ingestion URL or GitHub raw paths from references/urls.md.

Do not fabricate version-specific behavior, default settings, or support statements.

Conflicts between sources

• If local (tier 1) disagrees with MCP or ingestion, prefer local when the user is clearly editing that canonical repo and the change is intentional work-in-progress; otherwise prefer ingestion/MCP as closer to published help and mention the discrepancy briefly if it matters.

Efficiency tips

• Narrow grep/search before reading large files.
• One MCP list/search call before pulling many full articles.
• For GitHub tier, toc files first—avoid downloading the whole tree.

Reference index

• human-search — external scraping
• references/urls.md — all canonical URLs
• references/git_remote_allowlist.md — when local tier 1 is allowed
• references/mcp_client_setup.md — MCP client setup and troubleshooting