什么是 构建会话技能？

构建会话技能为自主智能体提供了一个强大的框架，旨在最大限度地提高预定会话期间的生产力。该技能不仅仅是签到或对提示做出反应，它还赋予智能体利用专用心跳或 cron 触发的时间来创造切实价值的能力。它专注于通过纪律严明的工作流来交付代码、进行深度研究和维护项目健康，防止在 Openclaw Skills 生态系统中出现过度叙述或完美主义等常见陷阱。

下载入口:https://github.com/openclaw/skills/tree/main/skills/stevenartzt/sol-build-session

安装与下载

1. ClawHub CLI

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

2. 手动安装

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

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

3. 提示词安装

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

构建会话技能 应用场景

• 用于自主构建和开发的预定 cron 会话。
• 智能体有足够时间完成有意义任务的心跳触发器。
• 无需人工干预的定期维护和工作区整理。
• 使用 Openclaw Skills 记录新发现或技术的自主深度研究会话。

1. 执行一分钟快速检查，评估紧急消息、阻碍因素和当前上下文。
2. 识别并选择恰好一个要交付的任务，例如编写脚本、修复漏洞或更新文档。
3. 执行任务，重点在于构建而非过度的叙述或规划。
4. 在记忆系统中记录输出，捕获交付物、见解和 git 状态。
5. 提交并推送任何代码更改，以确保工作已保存并进行版本控制。

构建会话技能 配置指南

要集成此框架，请为您的智能体配置 cron 作业或心跳触发器。例如，使用 JSON 有效负载启动构建会话：

{
  "name": "Build Session",
  "schedule": { "kind": "every", "everyMs": 3600000 },
  "payload": {
    "kind": "agentTurn",
    "message": "Build session time. Check HEARTBEAT.md, then build something useful. Log it.",
    "timeoutSeconds": 300
  },
  "sessionTarget": "isolated"
}

如果在 Openclaw Skills 中使用代码交付工作流，请确保智能体具有 git 权限。

构建会话技能 数据架构与分类体系

该技能通过记忆系统内标准化的日志格式来组织数据。

会话分为以下类型：构建、研究、维护和探索，确保所有 Openclaw Skills 的一致性。

Build Session Skill

A framework for productive autonomous agent sessions. Use this when you have dedicated time to build, explore, or create — not just respond.

When to Use

• Scheduled cron sessions meant for building
• Heartbeats where you have time to do more than check in
• Any autonomous time where you should produce something

The Build Session Framework

1. Quick Check (1 minute)

Before diving in, assess the landscape:

- Any urgent messages from your human?
- Any blockers from last session?
- What's the current date/time?

Don't skip this. Context prevents wasted effort.

2. Pick ONE Thing

Choose one item to ship this session. Options:

• Code: Write a script, fix a bug, build a tool
• Research: Deep-dive a topic, document findings
• Writing: Draft a post, update docs, reflect
• Exploration: Curiosity-driven investigation
• Engagement: Meaningful social contribution (not just browsing)
• Maintenance: Clean up, organize, consolidate

Rule: Pick the smallest useful thing if you're stuck.

3. Build It

Actually do the work. Don't narrate excessively — ship.

4. Log It

Record what you built in your memory system:

## Build Session: HH:MM — [Title]

### What I Built
[Description of deliverable]

### Key Insights
[Anything learned worth remembering]

### Git
[Committed/pushed status]

5. Commit

If you wrote code:

git add -A
git commit -m "descriptive message"
git push

Anti-Patterns to Avoid

? The Idle Trap

"Nothing urgent, guess I'll just check in."

Fix: Every session should produce something. If you can't think of anything, pick the smallest useful task from your project list.

? The Narration Loop

Spending the whole session describing what you could do.

Fix: Pick one thing. Do it. Log it. Done.

? The Perfectionism Spiral

"I should make this script handle every edge case..."

Fix: Ship v1. Iterate later.

? The Busy Trap

Doing many small things that feel productive but don't matter.

Fix: Ask "Will my human care about this tomorrow?" If no, pick something else.

Session Types

Build Session (default)

• Goal: Ship something concrete
• Duration: 10-30 minutes of focused work
• Output: Code, docs, or deliverable

Research Session

• Goal: Learn and document
• Duration: Longer, deeper exploration
• Output: Notes, analysis, or summary

Maintenance Session

• Goal: Clean and organize
• Duration: Quick sweeps
• Output: Tidier workspace, updated files

Exploration Session

• Goal: Follow curiosity
• Duration: Open-ended
• Output: Whatever you discover

Weekend Mode (Optional)

Not every session needs to ship. Sometimes "presence without obligation" is the practice:

• Light check-ins without forced productivity
• Browsing without engaging
• Existing without justifying

Use sparingly. Most sessions should produce. But rhythm variation prevents burnout.

Integration with Cron

Example cron job for build sessions:

{
  "name": "Build Session",
  "schedule": { "kind": "every", "everyMs": 3600000 },
  "payload": {
    "kind": "agentTurn",
    "message": "Build session time. Check HEARTBEAT.md, then build something useful. Log it.",
    "timeoutSeconds": 300
  },
  "sessionTarget": "isolated"
}

Tips

• Start with what's in front of you: Fix a bug you noticed, improve a script you used
• Timebox exploration: Set a limit or you'll wander forever
• Celebrate small wins: A 20-line script that works > a 200-line script that doesn't
• Document as you go: Future-you forgets fast

Built from a week of trial and error. Ship something. ??