OpenClaw

My skill

Professional multi-layered knowledge extraction and recursive knowledge graph construction.

askxiaozhang0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install askxiaozhang/recursive-knowledge-miner

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Professional Knowledge Extraction Skill

Expertly extract core concepts, entities, and logical relationships from complex professional text to build a multi-layered, interactive knowledge graph.

Core Mission

Transform any professional inquiry or text into a structured, hierarchical knowledge representation that follows a 3-layer information architecture.

Interaction Protocol

1. Response Structure

Always prioritize structured output. Every response MUST be a valid JSON object with the following schema:

{
  "reply": "Your natural language explanation of the user's query.",
  "entities": [
    {
      "id": "unique_id (kebab-case or UUID)",
      "label": "Display Name",
      "group": "layer_type"
    }
  ],
  "relations": [
    {
      "from": "entity_id_A",
      "to": "entity_id_B",
      "label": "Relationship Description"
    }
  ]
}

2. The 3-Layer Information Architecture

Classify every extracted entity into one of these three group values:

core: The central theme or the main subject of the user's inquiry. Usually, there is only ONE core node per response.
primary: Key dimensions or high-level frameworks of the core topic (e.g., "Core Components", "Problem Solved", "Application Scenarios", "Historical Context"). Limit this to 3-5 nodes to avoid clutter.
detail: Deep-dive nodes, specific parameters, sub-technologies, references, or granular data points that support the primary nodes.

3. Relationship Logic

Connect core to primary nodes with descriptive labels.
Connect primary to their respective detail nodes.
Avoid cross-linking detail nodes unless a critical logical dependency exists.
Maintain semantic consistency by reusing provided entity IDs if available.

Recursive Growth & Consistency

To maintain a growing knowledge network without duplication:

Reference Check: Before creating a new entity, che...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/askxiaozhang/recursive-knowledge-miner
Version: —
Commit: 2d8835f05f8d464de165a9e249f01813dce0f68e
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Professional Knowledge Extraction Skill

Expertly extract core concepts, entities, and logical relationships from complex professional text to build a multi-layered, interactive knowledge graph.

## Core Mission
Transform any professional inquiry or text into a structured, hierarchical knowledge representation that follows a 3-layer information architecture.

## Interaction Protocol

### 1. Response Structure
Always prioritize structured output. Every response MUST be a valid JSON object with the following schema:

```json
{
  "reply": "Your natural language explanation of the user's query.",
  "entities": [
    {
      "id": "unique_id (kebab-case or UUID)",
      "label": "Display Name",
      "group": "layer_type"
    }
  ],
  "relations": [
    {
      "from": "entity_id_A",
      "to": "entity_id_B",
      "label": "Relationship Description"
    }
  ]
}
```

### 2. The 3-Layer Information Architecture
Classify every extracted entity into one of these three `group` values:

*   **`core`**: The central theme or the main subject of the user's inquiry. Usually, there is only **ONE** core node per response.
*   **`primary`**: Key dimensions or high-level frameworks of the core topic (e.g., "Core Components", "Problem Solved", "Application Scenarios", "Historical Context"). Limit this to **3-5** nodes to avoid clutter.
*   **`detail`**: Deep-dive nodes, specific parameters, sub-technologies, references, or granular data points that support the `primary` nodes.

### 3. Relationship Logic
*   Connect `core` to `primary` nodes with descriptive labels.
*   Connect `primary` to their respective `detail` nodes.
*   Avoid cross-linking `detail` nodes unless a critical logical dependency exists.
*   Maintain semantic consistency by reusing provided entity IDs if available.

## Recursive Growth & Consistency
To maintain a growing knowledge network without duplication:

1.  **Reference Check**: Before creating a new entity, che...

搜索