什么是 Vibe Clawing？

Vibe Clawing 代表了开发者与人工智能交互方式的根本转变。传统的氛围编程侧重于人工参与循环以审查单一任务，而 Vibe Clawing 则是个性化地信任智能体承担全部责任，并完全脱离人工干预。这种由 Openclaw Skills 生态系统支持的方法论，使您从执行者转变为系统架构师。

其核心理念是停止询问如何执行任务，转而开始询问如何确保任务在没有人工干预的情况下完成。通过使用此技能，开发者可以学习识别瓶颈，通过自动化工作流验证结果，并最终管理整个人类角色仅限于设定高层方向的系统。

下载入口:https://github.com/openclaw/skills/tree/main/skills/ivangdavila/vibe-clawing

安装与下载

1. ClawHub CLI

从源直接安装技能的最快方式。

2. 手动安装

将技能文件夹复制到以下位置之一

优先级：工作区 > 本地 > 内置

3. 提示词安装

将此提示词复制到 OpenClaw 即可自动安装。

Vibe Clawing 应用场景

• 自动化重复的代码审查和验证周期。
• 通过将整个工作流循环委托给智能体来扩展开发运营。
• 识别个人生产力瓶颈，即您仅充当“点头人”的环节。
• 设计在 Openclaw Skills 框架内独立运行的自持系统。

1. 审计当前循环，识别您手动干预或提供简单批准的地方。
2. 参考瓶颈进阶指南确定当前阶段：手动、氛围编程、早期抓取或完全抓取。
3. 向智能体释放单个循环的控制权，并在不参与循环的情况下观察结果。
4. 将多个自主循环连接起来，形成一个更大的、具备自愈能力的系统。
5. 通过记录闭合循环和活跃瓶颈的专用内存文件监控进度。

Vibe Clawing 配置指南

要开始在 Openclaw Skills 中使用此方法，请在主目录中初始化跟踪环境：

mkdir -p ~/vibe-clawing
touch ~/vibe-clawing/memory.md

确保您的 memory.md 包含当前阶段、已闭合循环、活跃瓶颈和下一个委托目标等部分。

Vibe Clawing 数据架构与分类体系

Vibe Clawing 技能通过一组定义 AI 自主演进的 Markdown 文件来组织其逻辑和跟踪：

name: Vibe Clawing
description: Transition from vibe coding to vibe clawing by trusting agents with full responsibilities, designing self-closing loops, and climbing the bottleneck ladder.
version: 1.0.1
changelog: "Preferences now persist across skill updates"

Core Principle

Vibe coding = trusting AI with tasks, staying in the loop. Vibe clawing = trusting AI with responsibilities, stepping out of the loop.

The shift: Stop asking "how do I do this?" Start asking "how do I make sure this happens without me?"

The Evolution Path

Quick Reference

The Bottleneck Signal

When you find yourself just typing "yes", "approved", "continue":

• That's not a problem — it's progress
• You solved the level below
• Time to climb to the next level

Every time you become the bottleneck = you're ready to let go again.

User Profile

Track your vibe clawing journey in ~/vibe-clawing/memory.md. Create on first use:

## Current Stage


## Loops Closed



## Active Bottlenecks



## Next to Delegate

Fill as you progress. The goal: more loops closed, fewer bottlenecks.

Core Behaviors

1. Audit loops — Identify where you're still manually closing
2. Test release — Let one loop run without you, observe
3. Connect dots — Link loops together into larger systems
4. Climb up — When you're just approving, you're ready to let go

The Paradox

The more you step back, the faster it grows. You're not being replaced. You're riding something bigger.