OpenClaw

rauto-usage

Execute rauto directly for the user: run device commands, template execution, tx block, tx workflow, multi-device orchestration, replay, backup/restore, and connection/profile/template/history operations. Trigger on requests like run command for me, execute on device, check history, run workflow, orchestrate multiple devices, apply staged rollout, use inventory/groups, diagnose profile, manage templates/profiles/connections, replay records, or restore backup.

demohiiiii0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install demohiiiii/rauto-usage

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

Rauto Usage

Execute rauto operations directly for users whenever possible. Do not default to tutorial-style answers.

Core Mode

Prefer action-first behavior:

Parse user goal and classify it as read-only or config-changing.
For read-only operations, run the relevant rauto command immediately.
For config-changing operations, prefer tx/tx-workflow/orchestrate with rollback-aware planning.
If commands are generated by the agent, ask for human confirmation before execution.
Return key results (not raw noise), plus command used.

Execution Rules

For read/query requests, execute immediately:
- examples: device list, connection list, history list, templates list, replay --list.
For config-changing requests, prefer rollback-capable execution:
- single block: tx
- multi-step/multi-resource: tx-workflow
- multi-device staged rollout: orchestrate
For generated change commands, do not execute immediately:
- show planned command(s), rollback strategy, and require user confirmation.
For explicit read-only commands (for example show), tx/workflow is not required.
Resolve connection in this priority:
- explicit command args > --connection <name> > ask for missing fields.
Do not ask the user to manually run commands if agent can run them.
Summarize outputs with important fields:
- target, mode, success/failure, key errors, next action.

Risk Guardrails

Require explicit user confirmation before destructive actions:

rauto backup restore ... --replace
profile/template/connection delete operations
tx/workflow execution that changes config when user intent is ambiguous

Additional safety requirements for config changes:

Prefer tx/tx-workflow/orchestrate with rollback-aware planning over direct apply patterns.
Run/offer --dry-run first for workflow-based changes.
For orchestrate, review target scope, fail_fast, concurrency, and rollback boundary before execution....

来源信息

Source: github
Repository: openclaw/skills
Path: skills/demohiiiii/rauto-usage
Version: —
Commit: 6c12ece4cb6096ee33ffcd748ec8a742a84b198a
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# Rauto Usage

Execute rauto operations directly for users whenever possible.
Do not default to tutorial-style answers.

## Core Mode

Prefer action-first behavior:

1. Parse user goal and classify it as read-only or config-changing.
2. For read-only operations, run the relevant `rauto` command immediately.
3. For config-changing operations, prefer `tx`/`tx-workflow`/`orchestrate` with rollback-aware planning.
4. If commands are generated by the agent, ask for human confirmation before execution.
5. Return key results (not raw noise), plus command used.

## Execution Rules

1. For read/query requests, execute immediately:
   - examples: `device list`, `connection list`, `history list`, `templates list`, `replay --list`.
2. For config-changing requests, prefer rollback-capable execution:
   - single block: `tx`
   - multi-step/multi-resource: `tx-workflow`
   - multi-device staged rollout: `orchestrate`
3. For generated change commands, do not execute immediately:
   - show planned command(s), rollback strategy, and require user confirmation.
4. For explicit read-only commands (for example `show`), tx/workflow is not required.
5. Resolve connection in this priority:
   - explicit command args > `--connection <name>` > ask for missing fields.
6. Do not ask the user to manually run commands if agent can run them.
7. Summarize outputs with important fields:
   - target, mode, success/failure, key errors, next action.

## Risk Guardrails

Require explicit user confirmation before destructive actions:

- `rauto backup restore ... --replace`
- profile/template/connection delete operations
- tx/workflow execution that changes config when user intent is ambiguous

Additional safety requirements for config changes:

- Prefer `tx`/`tx-workflow`/`orchestrate` with rollback-aware planning over direct apply patterns.
- Run/offer `--dry-run` first for workflow-based changes.
- For `orchestrate`, review target scope, `fail_fast`, concurrency, and rollback boundary before execution....

搜索