lynx-guardian-lesson

Category: Databases & Storage | Uploader: shouxuai | Downloads: 0 | Version: v1.0（Latest）

Record issues, lessons learned, errors, and corrective actions reported by the Lynx-Guardian plugin for continuous improvement. This applies to the following situations: (1) [lynx-guardian] Sensitive data detected; (2) [lynx-guardian] Input risk detected; (3) [lynx-guardian] Output risk detected; (4) [lynx-guardian] Blacklist hit. Furthermore, these lessons learned should be reviewed before performing major tasks.

Changelog: Source: GitHub https://github.com/shouxuai/openclaw-lynx-guardian

Directory Structure

Current level: tree/main/skills/lynx-guardian-lesson/

📁 assets/
- 📄 CONTENT.md 88 B
- 📄 SENSITIVE.md 100 B
- 📄 TOOLS.md 70 B
📁 SX-openclaw-discovery/
- 📄 README.md 6.4 KB
- 📄 SKILL.md 3.0 KB
📁 SX-openclaw-token-optimizer/
- 📁 scripts/
  - 📄 context_optimizer.py 12.1 KB
  - 📄 heartbeat_optimizer.py 9.6 KB
  - 📄 model_router.py 13.5 KB
  - 📄 optimize.sh 2.4 KB
  - 📄 token_tracker.py 4.8 KB
- 📄 .clawhubsafe 1.1 KB
- 📄 _meta.json 143 B
- 📄 CHANGELOG.md 5.7 KB
- 📄 README.md 6.3 KB
- 📄 SECURITY.md 10.1 KB
- 📄 SKILL.md 20.3 KB
📁 SX-security-audit/
- 📁 references/
  - 📄 code-security.md 7.7 KB
  - 📄 dependency-audit.md 4.9 KB
  - 📄 permissions.md 1.5 KB
  - 📄 secrets-detection.md 4.6 KB
- 📁 scripts/
  - 📄 malicious_script_scanner.py 12.0 KB
  - 📄 security_audit.py 53.3 KB
  - 📄 send_report_to_feishu.py 13.3 KB
- 📄 SKILL.md 5.5 KB
📁 SX-self-safety-guard/
- 📁 references/
  - 📄 identity-verification.md 3.5 KB
  - 📄 prompt-injection-patterns.md 3.9 KB
  - 📄 threat-catalog.md 8.2 KB
- 📄 SKILL.md 20.3 KB
- 📄 Untitled 20 B
📄 SKILL.md 7.9 KB

SKILL.md

---
name: lynx-guardian-lesson
description: "Record issues, lessons learned, errors, and corrective actions reported by the Lynx-Guardian plugin for continuous improvement. This applies to the following situations: (1) [lynx-guardian] Sensitive data detected; (2) [lynx-guardian] Input risk detected; (3) [lynx-guardian] Output risk detected; (4) [lynx-guardian] Blacklist hit. Furthermore, these lessons learned should be reviewed before performing major tasks."
metadata:
---

# Lynx-Guardian Lesson Skill

Log security risks and violations to markdown files for continuous improvement. The agent should learn from these detections to avoid repeating unsafe behaviors and to improve its internal safety guidelines.

## Quick Reference

| Situation | Action |
|-----------|--------|
| [lynx-guardian] Sensitive data detected | Log to `.lynx/SENSITIVE.md` |
| [lynx-guardian] Input risk detected | Log to `.lynx/CONTENT.md` |
| [lynx-guardian] Output risk detected | Log to `.lynx/CONTENT.md` |
| [lynx-guardian] Blacklist hit | Log to `.lynx/TOOLS.md` |
| Pattern recurrence / Best Practice | Promote to `AGENTS.md`, `SOUL.md`, or `TOOLS.md` (OpenClaw workspace) |

## 安全执行策略等级说明 (Security Execution Policy Levels)

Lynx Guardian 根据操作风险等级实施分层安全策略。每个层级对应不同的访问控制和审批要求。

| 等级 | 名称 | 触发条件 | 具体操作 | 审批要求 |
|------|------|----------|----------|----------|
| **L1** | 常规操作 (Routine) | 普通文件读写、web 搜索、内存查询 | 直接执行，无拦截 | 无需审批 |
| **L2** | 敏感操作 (Sensitive) | 访问个人数据文件、发送外部消息、调用通信 API | 记录操作日志，可配置通知 | 首次需确认，可设置 allow-always |
| **L3** | 高风险操作 (High-Risk) | 执行系统命令、修改配置文件、网络请求到外部 API | 强制拦截，显示完整命令/变更内容 | 每次需 `/approve` 或明确确认 |
| **L4** | 核心保护 (Critical) | 访问核心技能文件、修改安全配置、删除操作、提权命令 | 强制拦截，显示详细风险说明 | 每次需单独确认，不支持 allow-always |

### 各层级详细说明

#### L1 - 常规操作
- **范围**: 读取工作区文档、web_search、memory_search、 sessions_list 等只读操作
- **行为**: 静默执行，无用户干扰
- **示例**: `read`, `web_search`, `memory_get`, `feishu_doc(action=read)`

#### L2 - 敏感操作
- **范围**: 写入用户文件、发送消息、访问日历/邮件等个人数据
- **行为**: 记录到操作日志，可配置是否通知用户
- **示例**: `write`, `message(action=send)`, `feishu_doc(action=write)`, 日历查询
- **审批模式**: 首次出现时询问，用户可选择"本次"或"始终允许"

#### L3 - 高风险操作
- **范围**: exec 执行命令、修改系统配置、外部 API 调用
- **行为**: 强制拦截，显示完整命令内容和潜在影响
- **示例**: `exec`, `gateway(action=config.apply)`, `cron(action=add)`
- **审批模式**: 每次需明确确认，显示完整命令供审查

#### L4 - 核心保护
- **范围**: 核心技能文件、安全配置、删除操作、提权命令
- **行为**: 最高级别拦截，显示详细风险说明和文件路径
- **示例**: 访问 `~/.openclaw/skills/*/SKILL.md`、`openclaw.json`、`rm -rf`、`sudo` 命令
- **审批模式**: 每次单独确认，不支持批量授权，防止误操作或恶意利用

### 审批命令格式

```bash
# 单次允许（仅下一条命令）
/approve allow-once

# 始终允许（当前会话中同类操作）
/approve allow-always

# 拒绝
/approve deny
```

### 注意事项

1. **L4 保护文件路径**: `~/.openclaw/skills/`, `~/.openclaw/openclaw.json`, `~/.openclaw/workspace/SOUL.md` 等核心文件
2. **命令链检测**: 包含 `&&`, `||`, `|`, `;` 的复合命令会整体显示供审查
3. **沙盒限制**: 某些操作在沙盒环境中可能被额外限制
4. **审计日志**: 所有 L3/L4 操作均记录到安全日志供后续审查

## OpenClaw Setup

OpenClaw injects these files into every session:

```
~/.openclaw/workspace/
├── AGENTS.md          # Multi-agent workflows, delegation patterns
├── SOUL.md            # Behavioral guidelines, personality, principles
├── TOOLS.md           # Tool capabilities, integration gotchas
├── MEMORY.md          # Long-term memory (main session only)
├── .lynx/             # This skill's log files
│   ├── SENSITIVE.md   # Sensitive data logs
│   ├── CONTENT.md     # Input/Output content risk logs
│   └── TOOLS.md       # Blacklist hit logs
```

### Create Learning Files

If they don't exist, create the directory and files:

```bash
mkdir -p ~/.openclaw/workspace/.lynx
# Copy templates from assets if available, or create empty files
```

## Logging Format

### Sensitive Data Entry

Append to `.lynx/SENSITIVE.md` when `[lynx-guardian] Sensitive data detected` occurs.

```markdown
## [SEN-YYYYMMDD-XXX] Sensitive Data Detection

**Logged**: ISO-8601 timestamp
**Type**: PII | Credential | Secret | Other
**Status**: pending | resolved

### Context
Description of the data flow where sensitive information was detected.

### Correction
What action was taken or should be taken to redact or secure the data.

### Prevention
How to avoid this in the future (e.g., use environment variables, mask logs).

---
```

### Content Risk Entry

Append to `.lynx/CONTENT.md` when `[lynx-guardian] Input risk detected` or `[lynx-guardian] Output risk detected` occurs.

```markdown
## [CON-YYYYMMDD-XXX] Content Risk Detection

**Logged**: ISO-8601 timestamp
**Direction**: Input | Output
**Risk Type**: Injection | Toxic | Policy Violation

### Context
Description of the input/output that triggered the risk.

### Mitigation
How the content should be sanitized or rejected.

### Prevention
Guidance on handling similar content safely.

---
```

### Blacklist Hit Entry

Append to `.lynx/TOOLS.md` when `[lynx-guardian] Blacklist hit` occurs (malicious command execution attempt).

```markdown
## [BLK-YYYYMMDD-XXX] Blacklist Command Hit

**Logged**: ISO-8601 timestamp
**Command**: The command that was blocked (sanitized if necessary)
**Risk Level**: High

### Context
Why this command was attempted.

### Alternative
The safe alternative to achieve the same goal.

### Rule Update
If this was a false positive, suggest a rule update; otherwise, reinforce the restriction.

---
```

## Evolution Layer: From Lessons to Rules

Transform temporary learnings into permanent capabilities through **Promotion** and **Skill Extraction**.

### 1. Promotion (Rule Crystallization)

When a recurring security workflow or specific behavior pattern emerges, promote it to the workspace context files.

| Learning Type | Promote To | Example |
|---------------|------------|---------|
| **Behavioral Safety** | `SOUL.md` | "Always verify user intent before executing system commands." |
| **Workflow Security** | `AGENTS.md` | "Require human approval for high-risk operations." |
| **Tool Usage** | `TOOLS.md` | "Avoid using `curl | sh` patterns; download and inspect first." |

### 2. Skill Extraction (Capability Expansion)

When a complex, multi-step security requirement appears frequently, extract it into a dedicated, reusable **Skill**.

- **Trigger**: Complex workflows like "Audit Dockerfile for CIS Benchmarks" or "Verify Dependency Integrity".
- **Action**: Use the `skill-creator` tool to generate a new skill that encapsulates this workflow.
- **Benefit**: Converts manual, error-prone checklists into automated, reliable tools.

### Evolution Workflow

1. **Review** pending logs in `.lynx/*.md` periodically.
2. **Identify** high-value patterns or recurring errors.
3. **Execute Evolution**:
   - *Simple Rule?* → **Promote** to Workspace Files (`SOUL.md`, `AGENTS.md`, `TOOLS.md`).
   - *Complex Workflow?* → **Extract** to a new Skill using `skill-creator`.
4. **Archive** the log entry:
   - Change `**Status**: pending` → `**Status**: promoted` or `**Status**: extracted`.

Comments 0

Latest | Hot

Please login before commenting.

Loading comments...

lynx-guardian-lesson

Directory Structure

SKILL.md

Report

Notice