buildlog

SKILL.md content

---
name: buildlog
description: Record, export, and share your AI coding sessions as replayable buildlogs
version: 1.0.0
author: buildlog.ai
repository: https://github.com/buildlog/openclaw-skill
homepage: https://buildlog.ai
---

# Buildlog Skill

Record your OpenClaw coding sessions and share them on buildlog.ai.

## Overview

The buildlog skill captures your AI-assisted coding sessions in real-time, creating replayable recordings that can be shared with others. Perfect for:

- **Tutorials**: Share how you built something step-by-step
- **Documentation**: Create living documentation of complex implementations
- **Debugging**: Review sessions to understand what went wrong
- **Learning**: Study how others approach problems

## Commands

### Recording

- **"Start a buildlog [title]"** — Begin recording a new session
- **"Stop the buildlog"** — End recording and optionally upload
- **"Pause the buildlog"** — Temporarily pause recording
- **"Resume the buildlog"** — Continue a paused recording

### Exporting

- **"Export this session as a buildlog"** — Convert current session to buildlog format
- **"Export the last [N] messages"** — Export a portion of the session

### Uploading

- **"Upload the buildlog"** — Push to buildlog.ai
- **"Share the buildlog"** — Upload and get a shareable link

### Annotations

- **"Add a note: [text]"** — Add commentary to the current point
- **"Mark this as important"** — Flag the current exchange
- **"Add chapter: [title]"** — Create a chapter marker

### Status

- **"Buildlog status"** — Check recording state
- **"Show buildlog info"** — Display current recording details

## Configuration

Add to your OpenClaw configuration:

```json
{
  "skills": {
    "buildlog": {
      "apiKey": "your-api-key",
      "autoUpload": false,
      "defaultPublic": true,
      "includeFileContents": true,
      "maxFileSizeKb": 100
    }
  }
}
```

### Options

| Option | Type | Default | Description |
|--------|------|---------|-------------|
| `apiKey` | string | — | Your buildlog.ai API key (optional for public uploads) |
| `autoUpload` | boolean | `false` | Automatically upload when recording stops |
| `defaultPublic` | boolean | `true` | Make buildlogs public by default |
| `includeFileContents` | boolean | `true` | Include file content snapshots |
| `maxFileSizeKb` | number | `100` | Maximum file size to include |

## Events

The skill emits the following events:

- `buildlog:started` — Recording began
- `buildlog:stopped` — Recording ended
- `buildlog:paused` — Recording paused
- `buildlog:resumed` — Recording resumed
- `buildlog:uploaded` — Buildlog uploaded successfully
- `buildlog:error` — An error occurred

## Examples

### Basic Recording

```
You: Start a buildlog "Building a REST API"
Assistant: 🔴 Recording started: "Building a REST API"

You: Create an Express server with TypeScript
Assistant: [creates files...]

You: Stop the buildlog
Assistant: Recording stopped. 12 exchanges captured.
         Would you like to upload to buildlog.ai?
```

### Retroactive Export

```
You: Export this session as a buildlog
Assistant: Exported 24 exchanges as buildlog.
         Title: "Untitled Session"
         Ready to upload?
```

## Privacy

- Buildlogs can be public or private
- API keys are never included in exports
- You control what gets shared
- Delete buildlogs anytime at buildlog.ai

How this skill works

• The skill analyzes build logs to extract summaries, errors, warnings, and suggestions.
• Required input: buildlog (string containing the build log).
• Optional input: log_type (e.g., 'cmake', 'make', 'ninja').
• Outputs: summary, errors, warnings, fixes (all strings or lists).
• Uses a templated LLM prompt with instructions for structured analysis.
• Prompt includes sections for identifying key events, errors, warnings, and fixes.
• LLM response is expected in JSON format with specified keys.
• Parses JSON response and maps to output fields.

When to use it

• When parsing build logs to extract errors, warnings, and failure reasons
• When analyzing CI/CD pipeline logs to determine build status and duration
• When summarizing verbose build outputs for troubleshooting failed builds

Best practices

• Set BUILDLOG_API_KEY environment variable with a valid API key
• Set BUILDLOG_PROJECT_ID to the target project identifier
• Store sensitive configuration values securely, avoiding version control
• Verify API key permissions before enabling the skill

Example use cases

• Determine build success status: Parses the build log to output a boolean indicating if the build succeeded.
• Extract build errors: Identifies and lists specific error messages from the build log.
• Extract build warnings: Identifies and lists warning messages from the build log.
• Calculate build duration: Computes the total build time in seconds from timestamps in the log.
• List build artifacts: Extracts paths or names of produced artifacts from the log.

FAQs