Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -99,6 +99,7 @@ This section will list available skills as they are added.
| [cn-punctuation-checker](skills/cn-punctuation-checker/SKILL.md) | Checks Chinese text for incorrect English punctuation marks and supports batch fixing. | Chinese Copy Editing, Punctuation Correction | Stable |
| [wechat-mini-program-development](skills/wechat-mini-program-development/SKILL.md) | WeChat mini-program development skill with standard project structure, request wrapper, and API management. | WeChat Mini-Program Development, Project Scaffolding | Stable |
| [kz-article-deep-analysis](skills/kz-article-deep-analysis/SKILL.md) | Deeply interpret non-academic articles (blogs, essays, commentary) and output a structured analysis report (core issue, thesis, argument map, cognitive gains). | Reading, Article Analysis | Stable |
| [trae-claw-install](skills/trae-claw-install/SKILL.md) | Repository-driven OpenClaw deployment workflow with platform routing, acceptance checks, and unified troubleshooting steps. | OpenClaw Deployment, DevOps Workflow, Troubleshooting | Stable |


> Tip: To add your skill to this catalog, update this table in your PR.
Expand Down
51 changes: 51 additions & 0 deletions skills/trae-claw-install/SKILL.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,51 @@
---
name: trae-claw-install
description: Run a repository-driven OpenClaw deployment workflow with platform routing, setup/start/check, acceptance checks, and unified troubleshooting.
---

# TraeClawInstall

## Description
This skill executes an end-to-end OpenClaw deployment workflow from a repository that already provides platform scripts and operational documents.

## Usage Scenario
Use this skill when:
- The user asks for one-stop OpenClaw local deployment.
- The user wants to follow a repository-standard install/start/check flow.
- The user has setup/start failures and needs structured troubleshooting.

## Preconditions
- Current working directory is the repository root.
- Terminal execution is available.
- Repository contains platform scripts and troubleshooting docs.

## Instructions
1. Detect platform and route scripts:
- Windows: prefer WSL2 and use `scripts/windows/wsl/*.sh`
- macOS: use `scripts/macos/*.sh`
- Linux: use `scripts/linux/*.sh`
2. Validate baseline:
- `node --version` major version is `>=22`
- `npm --version` is available
- if `openclaw --version` is missing, continue with setup step
3. Execute standard flow:
- `setup -> start -> check`
4. Run minimum acceptance:
- `openclaw doctor`
- `openclaw status`
- `openclaw dashboard`
5. If any step fails, run troubleshooting workflow:
- capture the first error line
- rerun doctor/status
- verify binary paths and versions
- apply fixes from repository troubleshooting docs
- change one variable at a time and re-verify

## Output Contract
- Success: platform, executed steps, acceptance results, and service accessibility.
- Failure: first error, diagnostics performed, and next actionable fix.

## Constraints
- Reuse repository scripts and docs; do not create a parallel flow.
- Never write real secrets; only use example configuration.
- On Windows, prefer execution inside WSL2 Linux filesystem.
7 changes: 7 additions & 0 deletions skills/trae-claw-install/examples/input.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,7 @@
User request:

Please deploy OpenClaw in this repository on macOS and verify everything is healthy.

Repository context:
- Scripts exist under scripts/macos/
- Operational docs exist under docs/common/
16 changes: 16 additions & 0 deletions skills/trae-claw-install/examples/output.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,16 @@
Execution summary:
- Platform routed: macOS
- Baseline check: node >=22, npm available
- Flow executed: setup -> start -> check
- Acceptance check: doctor/status/dashboard executed

Result:
- Deployment status: passed
- Service state: running
- Dashboard: reachable

If failed:
- First error line captured
- doctor/status rerun completed
- Binary path/version diagnostics captured
- Next fix action listed from troubleshooting docs
Loading