CRUD

管理OpenClaw操作按CRUD分类，创建查询无审批，更新编辑删除需返回操作清单并二次确认。

Security Scan

The skill's files and runtime instructions are coherent with its stated purpose (CRUD approval gating); it requires no credentials or installs, but its policy of allowing unrestricted reads may be undesirable in some environments.

Purpose & Capability

The name/description (CRUD approval gating) match the SKILL.md, CLAUDE.md, README and examples. The skill declares no env vars, binaries, or installs, which is reasonable for an instruction-only governance/workflow skill.

Instruction Scope

Instructions are narrowly focused on classifying operations and requiring user confirmation for Create/Update/Edit/Delete. However, the policy explicitly allows Read operations to execute immediately (file reads, directory listing, search) with no approval. That is consistent with the stated design but grants broad read access which could surface sensitive data; the skill gives no guidance on limiting read scope or filtering sensitive files.

Install Mechanism

This is an instruction-only skill with no install spec and no code to fetch or execute. That minimizes installation risk.

Credentials

The skill requests no environment variables, credentials, or special config paths — consistent and proportionate for a policy/approval skill.

Persistence & Privilege

Metadata flags show no 'always' privilege (always: false) and normal autonomous invocation is allowed. The documentation text says the skill is 'automatically injected into sessions,' which is misleading relative to the flags; confirm how your OpenClaw deployment will load/inject the skill before trusting automatic behavior. The skill does not request system-wide privileges or modify other skills.

Assessment

This skill appears to do what it claims: classify operations and require confirmation for writes. Before installing: 1) Be aware that 'Read' operations are allowed without confirmation — in sensitive environments you may prefer a stricter policy or to limit the skill's ability to read certain paths. 2) Verify how your OpenClaw instance loads/injects skills (the docs in the package say it's 'automatically injected' which conflicts with the manifest flags); ensure it won't be auto-enabled in contexts you don't expect. 3) Test in a non-production environment to confirm the confirmation flow works and that action lists accurately list affected files. 4) Use the provided uninstall steps if you need to remove it. 5) Only install from a trusted source; this package has no homepage or verified publisher metadata, so validate the origin if you rely on it in production.

---

name: crud description: CRUD Approval Mode - Categorize OpenClaw operations by CRUD, allow Read freely, require confirmation for Create/Update/Edit/Delete metadata: version: 2.0.0 author: Slava Chan @UyNewNas category: governance tags: [approval, security, crud, workflow]

CRUD Approval Mode Skill

Categorize and manage OpenClaw operations by CRUD (Create/Read/Update/Delete) for fine-grained approval control.

Core Design Philosophy

• Read: Fully unrestricted for maximum efficiency
• Create + Update + Edit + Delete: Add an isolation layer, return action list for secondary confirmation

Category Definitions

Operation Type	Approval Required	Description
Read	❌ No approval	File reading, search queries, directory browsing, etc.
Create	✅ Requires confirmation	File creation, new skill creation, directory creation, etc.
Update/Edit	✅ Requires confirmation	File modification, code editing, config updates, etc.
Delete	✅ Requires confirmation	File deletion, directory deletion, skill deletion, etc.

Workflow

1. No Approval Flow (Read)

User Request → Execute Directly → Return Result

2. Approval Flow (Create/Update/Edit/Delete)

User Request → Analyze Operation → Generate Action List → User Confirmation → Execute Operation → Return Result
                            ↓
                       Display: operation type, affected files, change preview

Action List Format

When confirmation is needed, return the list in the following format:

⚠️ **Operation Confirmation** - [Operation Type]

**Scope:**
- File 1: path/to/file1
- File 2: path/to/file2

**Description:**
[Detailed description of the operation to be performed]

Please reply with one of the following to continue:
- ✅ **Confirm** - Proceed with this operation
- ❌ **Cancel** - Cancel this operation
- 🔄 **Modify** - Modify operation and re-confirm

Use Cases

• Daily development: Quick read operations without approval restrictions
• Critical operations: Confirmation mechanism before all write operations
• Skill development: New skill creation requires confirmation for safety

Configuration

This skill requires no additional configuration files and is automatically injected into sessions.

---

References

• OpenClaw Documentation: https://docs.openclaw.ai/