[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M6MJF9HBW9DFTJFJGKBWM0BE":3,"skill-same:01M6MJF9HBW9DFTJFJGKBWM0BE":73},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":23,"publishedAt":44,"linkOnly":45,"markdownContent":46,"markdownBody":47,"frontMatter":48,"refName":49,"commitSha":50,"skillDirectory":51,"forksCount":52,"repositoryHtmlUrl":53,"repositoryHomepageUrl":54,"ownerHtmlUrl":55,"ownerBlogUrl":56,"ownerDescription":57,"updatedAt":58,"install":59,"resources":72},"01M6MJF9HBW9DFTJFJGKBWM0BE","ask",null,"Answer grounded questions about the codebase (onboarding \u002F Q&A) using the reviewer RAG + code graph. Use when the user asks how the code works, where something lives, or to explain a subsystem (\"where is auth\", \"how does X work\", \"explain the indexing flow\", \"как устроено…\", \"где у нас…\", \"объясни код\"). Requires a built base index + graph (reviewer MCP server). Not for reviewing PRs.","hashgraph-online\u002Fawesome-codex-plugins","hashgraph-online","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F160371962?v=4","01M6CNB6NRJVNNGN14TR01Q6D3","HOL (Hashgraph Online)","01M6JT1HSKKG9V68KQAQGBA7XP",1575,"Apache-2.0","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fask\u002FSKILL.md",[18],{"categoryNo":19,"categoryName":20,"taxonomyType":21,"taxonomyTypeDesc":22},"01JBSEEDCAT000000000000023","Skill与智能体开发","SCENARIO","使用场景",[5,24,25,26,27,28,29,30,31,32,33,34,35,36,37,38,39,40,41,42,43],"reviewer","when","prs","for","q&a","answer","questions","indexing","use","work","MCP","explain","how","flow","server","graph","code","rag","auth","mcp server","2026-11-10 10:12:30",false,"---\nname: ask\ndescription: Answer grounded questions about the codebase (onboarding \u002F Q&A) using the reviewer RAG + code graph. Use when the user asks how the code works, where something lives, or to explain a subsystem (\"where is auth\", \"how does X work\", \"explain the indexing flow\", \"как устроено…\", \"где у нас…\", \"объясни код\"). Requires a built base index + graph (reviewer MCP server). Not for reviewing PRs.\n---\n\n# Ask (codebase Q&A)\n\nAnswer a free-text question about the codebase with a **grounded** response: every claim is\nbacked by a real `path:line` citation, never an invented path. Built on the reviewer MCP server\n(hybrid RAG + code graph). This skill reads and explains; it does NOT modify code or review PRs.\n\n**Always answer the user in Russian** (the project language), regardless of this file's language.\nTool calls, code identifiers, and `path:line` citations stay verbatim.\n\n## Inputs\n\n`$ARGUMENTS` — a free-text question about the code (e.g. \"where is authentication\",\n\"how does index freshness work\", \"explain the retrieval pipeline\").\n\n## Tools\n\n\u003C!-- include: _common\u002Ftool-usage.md -->\nUse the session-less tools above.\n\nPlus the harness file tools (`Read`, `Grep`, `Glob`) to read source from the local clone on disk.\n\n## Pipeline\n\n1. **Resolve repo\u002Fbranch.**\n   - `repo`: `git remote get-url origin` → strip a trailing `.git`, take the last two path\n     segments (`owner\u002Fname`). Pass `\"\"` to let the server use `DEFAULT_REPO` if origin is missing.\n   - `branch`:\n\n\u003C!-- include: _common\u002Fbranch-selection.md -->\n\n   **Freshness check (first code question of the session only).** After resolving repo\u002Fbranch and\n   ONLY on the first code question in this conversation — rely on conversation memory: if you have\n   already checked index freshness earlier in this session, skip this — run\n   `uvx --from rag-reviewer reviewer status \u003Cpath> --branch \u003Cbranch> --json` and read `drift`. If\n   `drift > 0`, emit exactly **one banner line**, in Russian:\n   «⚠ индекс отстаёт на N коммитов, ответ может не учитывать свежие изменения → `rag-reviewer:sync-codebase`».\n   Do NOT block, reindex, ask for confirmation, or call `sync_board` — this is warn-only. Cost ≈ 0\n   Voyage (reads `index_meta` + local git). **Fail-open:** any error → skip the banner silently\n   (Q&A is latency-sensitive).\n\n1.5. **Subsystem prior (cheap, optional).** Call `get_subsystem_summaries(repo, branch, query=\"\u003Cthe user's question>\")`.\n   At scale (summary count above the deploy threshold) this returns the top-k subsystems nearest the\n   question; on small repos it returns all (back-compat). If it returns summaries, use the one matching\n   the question's subsystem as a high-level orientation **before** `search_codebase` — this cuts\n   exploration steps for architectural \u002F \"how does subsystem X work\" questions. The summary is only a\n   prior: every `path:line` you cite in the answer still comes from real code (`search_codebase` \u002F\n   `Read`), never from the summary text.\n   **Fail-open:** empty \u002F unavailable → skip this step and proceed exactly as before.\n\n2. **Search.** Call `search_codebase(repo, \"\u003Cquestion>\", branch=…)`. Parse the\n   `path#fqn (path:start-end)` headers to get candidate symbols (`node_id`) and line ranges.\n   If the result is `(ничего не найдено)`, go to Fallback.\n\n   **Lazy expansion (no user prompt).** If the output ends with a cliff\u002Frails note reporting a\n   high-scoring tail beyond the cut AND the question looks broad, you MAY re-call `search_codebase`\n   once with a higher ceiling (pass `top_k=\u003Cbigger>`), then merge. Do this silently — never pause to\n   ask the user.\n\n3. **Expand (only as needed).** For an architectural \u002F \"how does X work\" question, DEFAULT to\n   skipping the graph tools (`related_symbols` \u002F `callers` \u002F `definition`) — the hybrid search\n   usually suffices; CLAUDE.md \u002F README are cheap priors to consult first. Only when the answer\n   genuinely needs call relationships, for the symbols most relevant to the question, call\n   `related_symbols` \u002F `callers` \u002F `definition` to follow the graph. Do NOT expand everything —\n   only what the answer requires. Stop once you can answer.\n\n4. **Confirm source.** `search_codebase` snippets are line-numbered, so when the returned snippet\n   already shows the exact code you cite, you may cite `path:line` directly from the tool output —\n   a separate `Read` is not required for grounding. Use `Read` only when the snippet was truncated\n   (`[...truncated]`) or you need surrounding context. Never cite a `path:line` not present in any\n   tool output.\n\n5. **Answer (adaptive), in Russian.**\n   - Default (focused question): a direct answer in 2–4 sentences, then an **Evidence** list —\n     each item `path:line` + a one-line \"why this is relevant\".\n   - Broad question (\"explain subsystem X\"): expand into sections — Краткий ответ \u002F Ключевые\n     символы \u002F Поток \u002F Связанные места — each claim still carrying a confirmed `path:line`.\n\n## Grounding contract (hard rule)\n\nCite ONLY paths that were returned by a tool AND confirmed by the tool's line-numbered output or a `Read`. Never invent or guess a\npath or line number. If you cannot ground a statement, say so explicitly instead of fabricating a\ncitation. This is the skill's acceptance criterion.\n\nA line-numbered `search_codebase` snippet that contains the cited code counts as grounding — an\nextra `Read` of the same lines is redundant.\n\n## Fallback (fail-open)\n\nIf the reviewer MCP server is unreachable or returns `(ничего не найдено)` \u002F `(граф недоступен)`\n(Postgres\u002FNeo4j\u002Findex down), degrade gracefully:\n- Use the harness `Grep`\u002F`Glob`\u002F`Read` over the local clone to locate and confirm code.\n- Tell the user (in Russian) that semantic\u002Fgraph search was unavailable and the answer comes from\n  a lexical search, so it may be less complete.\nNever abort — always return the best grounded answer you can.\n\n## Notes\n\n- Precondition: the base index + graph must be built (`reviewer index`). Graph precision depends on\n  the backend: SCIP → `IMPLEMENTS` + accurate `CALLS`; tree-sitter → `CALLS` by name only.\n- Read-only: this skill never edits code and never posts to GitHub. Posting a human-facing review\n  guide to a PR is a separate skill (PRI-119).\n","# Ask (codebase Q&A)\n\nAnswer a free-text question about the codebase with a **grounded** response: every claim is\nbacked by a real `path:line` citation, never an invented path. Built on the reviewer MCP server\n(hybrid RAG + code graph). This skill reads and explains; it does NOT modify code or review PRs.\n\n**Always answer the user in Russian** (the project language), regardless of this file's language.\nTool calls, code identifiers, and `path:line` citations stay verbatim.\n\n## Inputs\n\n`$ARGUMENTS` — a free-text question about the code (e.g. \"where is authentication\",\n\"how does index freshness work\", \"explain the retrieval pipeline\").\n\n## Tools\n\n\u003C!-- include: _common\u002Ftool-usage.md -->\nUse the session-less tools above.\n\nPlus the harness file tools (`Read`, `Grep`, `Glob`) to read source from the local clone on disk.\n\n## Pipeline\n\n1. **Resolve repo\u002Fbranch.**\n   - `repo`: `git remote get-url origin` → strip a trailing `.git`, take the last two path\n     segments (`owner\u002Fname`). Pass `\"\"` to let the server use `DEFAULT_REPO` if origin is missing.\n   - `branch`:\n\n\u003C!-- include: _common\u002Fbranch-selection.md -->\n\n   **Freshness check (first code question of the session only).** After resolving repo\u002Fbranch and\n   ONLY on the first code question in this conversation — rely on conversation memory: if you have\n   already checked index freshness earlier in this session, skip this — run\n   `uvx --from rag-reviewer reviewer status \u003Cpath> --branch \u003Cbranch> --json` and read `drift`. If\n   `drift > 0`, emit exactly **one banner line**, in Russian:\n   «⚠ индекс отстаёт на N коммитов, ответ может не учитывать свежие изменения → `rag-reviewer:sync-codebase`».\n   Do NOT block, reindex, ask for confirmation, or call `sync_board` — this is warn-only. Cost ≈ 0\n   Voyage (reads `index_meta` + local git). **Fail-open:** any error → skip the banner silently\n   (Q&A is latency-sensitive).\n\n1.5. **Subsystem prior (cheap, optional).** Call `get_subsystem_summaries(repo, branch, query=\"\u003Cthe user's question>\")`.\n   At scale (summary count above the deploy threshold) this returns the top-k subsystems nearest the\n   question; on small repos it returns all (back-compat). If it returns summaries, use the one matching\n   the question's subsystem as a high-level orientation **before** `search_codebase` — this cuts\n   exploration steps for architectural \u002F \"how does subsystem X work\" questions. The summary is only a\n   prior: every `path:line` you cite in the answer still comes from real code (`search_codebase` \u002F\n   `Read`), never from the summary text.\n   **Fail-open:** empty \u002F unavailable → skip this step and proceed exactly as before.\n\n2. **Search.** Call `search_codebase(repo, \"\u003Cquestion>\", branch=…)`. Parse the\n   `path#fqn (path:start-end)` headers to get candidate symbols (`node_id`) and line ranges.\n   If the result is `(ничего не найдено)`, go to Fallback.\n\n   **Lazy expansion (no user prompt).** If the output ends with a cliff\u002Frails note reporting a\n   high-scoring tail beyond the cut AND the question looks broad, you MAY re-call `search_codebase`\n   once with a higher ceiling (pass `top_k=\u003Cbigger>`), then merge. Do this silently — never pause to\n   ask the user.\n\n3. **Expand (only as needed).** For an architectural \u002F \"how does X work\" question, DEFAULT to\n   skipping the graph tools (`related_symbols` \u002F `callers` \u002F `definition`) — the hybrid search\n   usually suffices; CLAUDE.md \u002F README are cheap priors to consult first. Only when the answer\n   genuinely needs call relationships, for the symbols most relevant to the question, call\n   `related_symbols` \u002F `callers` \u002F `definition` to follow the graph. Do NOT expand everything —\n   only what the answer requires. Stop once you can answer.\n\n4. **Confirm source.** `search_codebase` snippets are line-numbered, so when the returned snippet\n   already shows the exact code you cite, you may cite `path:line` directly from the tool output —\n   a separate `Read` is not required for grounding. Use `Read` only when the snippet was truncated\n   (`[...truncated]`) or you need surrounding context. Never cite a `path:line` not present in any\n   tool output.\n\n5. **Answer (adaptive), in Russian.**\n   - Default (focused question): a direct answer in 2–4 sentences, then an **Evidence** list —\n     each item `path:line` + a one-line \"why this is relevant\".\n   - Broad question (\"explain subsystem X\"): expand into sections — Краткий ответ \u002F Ключевые\n     символы \u002F Поток \u002F Связанные места — each claim still carrying a confirmed `path:line`.\n\n## Grounding contract (hard rule)\n\nCite ONLY paths that were returned by a tool AND confirmed by the tool's line-numbered output or a `Read`. Never invent or guess a\npath or line number. If you cannot ground a statement, say so explicitly instead of fabricating a\ncitation. This is the skill's acceptance criterion.\n\nA line-numbered `search_codebase` snippet that contains the cited code counts as grounding — an\nextra `Read` of the same lines is redundant.\n\n## Fallback (fail-open)\n\nIf the reviewer MCP server is unreachable or returns `(ничего не найдено)` \u002F `(граф недоступен)`\n(Postgres\u002FNeo4j\u002Findex down), degrade gracefully:\n- Use the harness `Grep`\u002F`Glob`\u002F`Read` over the local clone to locate and confirm code.\n- Tell the user (in Russian) that semantic\u002Fgraph search was unavailable and the answer comes from\n  a lexical search, so it may be less complete.\nNever abort — always return the best grounded answer you can.\n\n## Notes\n\n- Precondition: the base index + graph must be built (`reviewer index`). Graph precision depends on\n  the backend: SCIP → `IMPLEMENTS` + accurate `CALLS`; tree-sitter → `CALLS` by name only.\n- Read-only: this skill never edits code and never posts to GitHub. Posting a human-facing review\n  guide to a PR is a separate skill (PRI-119).\n",{"name":5,"description":7},"main","2b63f856ce19c2a797929cacabd9e0fc936812fa","plugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fask",491,"https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins","https:\u002F\u002Fhol.org\u002Fplugins\u002Fbest-codex-plugins","https:\u002F\u002Fgithub.com\u002Fhashgraph-online","https:\u002F\u002Fhol.org","Open-source standards and developer tools for interoperable AI agents: discovery, identity, communication, payments, privacy and security.","2026-11-14 14:06:13",{"source":8,"skillName":5,"commands":60,"prompt":70,"zipAvailable":71},[61,64,67],{"tool":62,"command":63},"npx","npx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ask",{"tool":65,"command":66},"bunx","bunx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ask",{"tool":68,"command":69},"pnpm","pnpm dlx skills add hashgraph-online\u002Fawesome-codex-plugins --skill ask","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fmimfort\u002Frag_for_git\u002Fplugin\u002Fskills\u002Fask\u002FSKILL.md",true,[],[74,84,92,100,108,116],{"skillNo":75,"name":76,"nameZh":6,"description":77,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":79,"sourceHtmlUrl":80,"categories":81,"keywords":82,"publishedAt":83},"01M7DV332YQMGD8WTRJ9DZQXTB","worktable-review-with-annotations","Create, inspect, reply to, update, or resolve situated Worktable annotations. Use when feedback belongs to a Doc section, block, text range, or HTML Doc, or when the user asks to address existing review feedback and coordinate a requested artifact edit.","MIT","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-review-with-annotations\u002FSKILL.md",[],[],"2026-11-15 14:19:17",{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":88,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":83},"01M7DV2YGHCZVBEB1AHYB6CGHE","worktable-find-and-synthesize-context","Find, assess, and synthesize context from Worktable Docs and Records. Use when the user asks what a workspace contains, wants workspace-backed research, needs current facts reconciled across artifacts, or requests a cited synthesis without changing workspace state.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-find-and-synthesize-context\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":96,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":83},"01M7DV2TQN1H11ME2SAF9MXN7V","worktable-create-or-update-docs","Create, edit, rename, or maintain narrative Worktable Docs. Use for plans, decisions, briefs, notes, research syntheses, and other durable prose when the user requests a new artifact or a safe update to an existing one.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-update-docs\u002FSKILL.md",[],[],{"skillNo":101,"name":102,"nameZh":6,"description":103,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":104,"sourceHtmlUrl":105,"categories":106,"keywords":107,"publishedAt":83},"01M7DV2NE452NEA8TXATKSNAJH","worktable-create-or-manage-records","Organize repeated structured information as durable Worktable Records. Use for research datasets, inventories, directories, pipelines, trackers, and other collections whose items need identity, fields, filtering, links, validation, or individual updates.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-records\u002FSKILL.md",[],[],{"skillNo":109,"name":110,"nameZh":6,"description":111,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":112,"sourceHtmlUrl":113,"categories":114,"keywords":115,"publishedAt":83},"01M7DV2HENRBR2KSCVM064WH0Y","worktable-create-or-manage-interactive-html","Create or improve durable visual and interactive artifacts in Worktable. Use for dashboards, trackers, calculators, mini apps, slide presentations, and other requests that benefit from a polished HTML Doc.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-create-or-manage-interactive-html\u002FSKILL.md",[],[],{"skillNo":117,"name":118,"nameZh":6,"description":119,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":78,"licenseFileUrl":120,"sourceHtmlUrl":121,"categories":122,"keywords":123,"publishedAt":83},"01M7DV2CADR5R7RQFFYPNAGR9Y","worktable-collaborate-threads","Read, answer, and hand off messages through durable Worktable threads with users or other authenticated participants. Use when the user asks to check addressed messages, reply to a participant, continue a thread, request another agent's help, wait briefly for a response, or watch for comments and messages sent to the agent.","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FLICENSE","https:\u002F\u002Fgithub.com\u002Fhashgraph-online\u002Fawesome-codex-plugins\u002Fblob\u002Fmain\u002Fplugins\u002Fworktable\u002Fworktable-plugin\u002Fskills\u002Fworktable-collaborate-threads\u002FSKILL.md",[],[]]