Share AI agent conversations as public web pages.
| Agent | Profile |
|---|---|
| ------- | --------- |
| OpenClaw | references/platforms/openclaw.md |
| _(unknown)_ | references/platforms/unknown.md — generic skill-based fallback |
| _(new platform)_ | Add a file following references/platforms/TEMPLATE.md |
Follow the Conversion section in the platform profile detected in Step 1.
Save the result to {projectDir}/chats/.tmp/{timestamp}.yaml.
The CLI auto-fills structural fields. The Skill's job is to fill in the human-facing metadata:
| Field | CLI default | Action |
|---|---|---|
| ------- | ------------- | -------- |
date, sessionId, model, totalMessages, totalTokens, defaultShowProcess | Auto-filled | Review only |
visibility | private | Update to public |
participants | Generic role names (user, assistant) | Ask user for display names → rename keys; if no name is provided, use Human / Agent for single-speaker or Human 1 / Human 2 … for multi-speaker |
title | 'Session Export' (generic) | Skim generated YAML → suggest → confirm |
description | _(absent)_ | Write one-sentence summary → confirm |
channel | _(absent)_ | Ask user — set to platform name (e.g. discord) if applicable; omit otherwise |
cover | _(absent)_ | Skip (user adds custom OG image URL manually later) |
tags | _(absent)_ | Skip (user adds manually later) |
Review the generated YAML and replace sensitive information with [REDACTED]:
[REDACTED]/Users/xxx → ~)[REDACTED][REDACTED]Do not silently remove content — always substitute [REDACTED] so the reader can see that content was present but withheld.
{YYYYMMDD}-{topic}.yaml```bash
cd {projectDir}
git checkout main
git pull origin main
git checkout -b chat/{YYYYMMDD}-{topic}
```
{projectDir}/chats/.tmp/{timestamp}.yaml → {projectDir}/chats/{YYYYMMDD}-{topic}.yaml```bash
git add chats/{YYYYMMDD}-{topic}.yaml
git commit -m "docs: add {topic}"
```
> Why create a branch here? Saving on the default branch risks mixing unrelated changes into a future PR. Always commit each chat file on its own dedicated branch.
Push the branch created in step 6 and open a PR.
See references/publish.md. Only proceed after explicit user request.
共 2 个版本