CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

knowledge-org

组织与检索超越扁平文本块的知识时使用——涵盖 RAPTOR/GraphRAG 结构化索引选型、OpenViking 文件系统范式与 L0/L1/L2 按需加载、增量更新 PR 审核流与定期整理、Agentic RAG 与安全边界、上下文感知检索、结构化数据知识发现,以及双层记忆架构。

Quality

81%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

73%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured, knowledge-dense skill body with exemplary workflow sequencing and validation checkpoints in its update/review processes. Its main weaknesses are re-explanations of published concepts Claude already knows and paragraph-length bullets that hurt token efficiency, plus companion-code references that lack concrete entry points.

Suggestions

Trim re-explanations of known concepts to decision-relevant contrasts: keep the 'when to choose RAPTOR vs GraphRAG' and '主要局限' rows of the comparison table but drop the mechanism row, and remove the ReAct loop description from the Agentic RAG bullet since Claude already knows it.

Break the paragraph-length bullets (定期整理三件事, 失效内容与权限隔离, 结构化数据知识发现两阶段) into tight sub-bullets or move the detail into separate reference files so SKILL.md reads as a lean overview.

Make the 配套代码 references actionable by adding one concrete entry command or usage example per directory (e.g., how to run the recall@k/MRR comparison in chapter3/contextual-retrieval/) instead of only describing what each directory contains.

DimensionReasoningScore

Conciseness

The body is dense and substantive, but it re-explains concepts Claude already knows — the RAPTOR/GraphRAG mechanism table ("叶子聚类 + LLM 递归生成父节点摘要"), the ReAct loop ("按 ReAct '思考→行动→观察' 循环"), and the published contextual-retrieval technique — and several bullets are paragraph-length walls that could be tightened (e.g., the 定期整理 bullet). It matches anchor 3: mostly efficient with some unnecessary explanation, not anchor 2 since there is no padding and nearly every sentence carries a decision rule or specific figure.

3 / 5

Actionability

For an instruction-only skill the guidance is concrete: explicit selection criteria ("查询主要是'找到包含某信息的片段'→混合检索足够"), specific thresholds ("每 20 轮", "L0 约 100 tokens"), and a numbered 5-step PR workflow with role separation. It stays at anchor 4 rather than 5 because the companion code directories are referenced by path without entry points or runnable commands, and some guidance remains at the design-decision level.

4 / 5

Workflow Clarity

The incremental-update PR flow is a clear 5-step sequence with explicit validation checkpoints and feedback loops: independent reviewer returning "指向具体证据和行号的可执行意见", "迭代至收敛…超限转人工,不得默认放行", CI gates ("通过后才…重建受影响的分块、摘要和向量索引"), and post-merge replay verification ("回放典型检索问答用例"). The batch operations involved all carry validation, so the destructive/batch cap does not apply; this matches anchor 5.

5 / 5

Progressive Disclosure

Sections are well organized (何时使用/核心原则/实践模式/常见陷阱/配套代码/深度阅读) and references are one level deep and clearly signaled, with each 配套代码 entry describing what its directory contains. It does not reach anchor 5 because all distilled content is inlined in a single ~75-line dense file with no split reference files, and the referenced paths (chapter3/*, book/chapter3.md) are external rather than a structured bundle.

4 / 5

Total

16

/

20

Passed

Description

78%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

A strong description with an explicit use-when clause, specific named technologies, and a well-defined niche. Main gaps are the absence of natural synonym variations (knowledge base, vector retrieval, chunking) and topic-style enumeration rather than concrete action verbs.

DimensionReasoningScore

Specificity

The description enumerates several concrete, named capability areas — "RAPTOR/GraphRAG 结构化索引选型", "L0/L1/L2 按需加载", "增量更新 PR 审核流", "双层记忆架构" — giving specific coverage of the skill's scope. It falls short of anchor 5 because the items are topic nouns rather than concrete actions the skill performs, but it lists far more than the 1–2 items of anchor 3.

4 / 5

Completeness

It has both an explicit when-clause ("组织与检索超越扁平文本块的知识时使用") and a what via the topic enumeration ("涵盖…"). The when is a single general condition without concrete user-mention trigger phrases, matching anchor 4 rather than 5; it is clearly above anchor 3 because the when is explicit, not merely implied.

4 / 5

Trigger Term Quality

It includes natural domain terms users would say ("RAG", "GraphRAG", "Agentic RAG", "检索", "记忆") alongside specific technique names. A few natural terms are missing ("知识库", "向量检索", "分块/chunking") and some jargon users would not say ("OpenViking", "L0/L1/L2"), so it matches anchor 4 rather than the comprehensive synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

The description carves out a clear niche — structured knowledge indexing and memory architecture for RAG systems — anchored by distinct named technologies (RAPTOR, GraphRAG, OpenViking, Agentic RAG). Triggers are distinct and conflict risk with other skills is minimal, matching anchor 5.

5 / 5

Total

17

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

bojieli/ai-agent-book

Path

skills/knowledge-org/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.