研究检索执行命令clawhub未标认证来源可访问clear审计通过

unraid-cli（unraid CLI 搜索）

Agent Skill

unraid-cli 用于查找、检索和筛选相关信息，适合在 OpenClaw 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

总安装

3,816

周安装

159

GitHub Stars

公开资料未说明

下载量

1,272

OpenClaw

安装说明

本站只整理中文说明和来源信息，不托管安装包，也不代用户安装。

GitHub

来源数

许可证

MIT-0

最后核验

2026-05-01

来源状态

来源可访问

安装方式

通过对话安装

复制提示词发给支持本地命令或 Skills 的 AI 助手，先确认命令和权限，再让它执行。

请帮我安装这个 Agent Skill：unraid-cli（unraid CLI 搜索）
来源仓库：https://github.com/ingodibella/unraid-cli
安装命令：
openclaw skills install unraid-cli
安装前请先检查当前环境是否支持对应 CLI，并向我确认将要执行的命令、安装目录、联网范围和文件读写权限；确认后再执行。

命令行安装

复制命令到本机终端执行。该命令会通过 OpenClaw 从第三方来源获取 Skill；本站只展示命令，不托管安装包，也不自动执行。

ClawHubOpenClaw

openclaw skills install unraid-cli

简介

TypeScript 编写的 Unraid Server GraphQL API 命令行接口。

包含系统、磁盘、容器等十二组管理命令模块。
便于远程监控与维护家庭媒体服务器环境。适用宿主包括 OpenClaw，接入前应确认版本、权限和运行环境要求。
需具备有效 API 密钥才能执行写操作命令。
unraid-cli 属于研究检索类 Skill，可作为该场景下的辅助能力补充。

SKILL.md

name: unraid-cli
description: TypeScript CLI for Unraid Server GraphQL API. 12 command groups for system, arrays, disks, containers, VMs, shares, logs, and diagnostics. Built for humans and AI agents.
version: 0.4.0
homepage: https://github.com/Ingodibella/unraid-cli
metadata
openclaw
emoji: 🖥️
requires
bins
env
install
kind: node
package: unraid-cli
bins
label: Install unraid-cli (npm)
author: Ingodibella
license: MIT

ucli agent guide

CLI: ucli [global flags] <group> <command> [args...]

Recommended defaults

ucli --output json --quiet <group> <command>

--output json for machine-readable output
--quiet to suppress decorative text
--fields to shrink payloads
--filter and --sort to shape data before it hits your context

Guardrails

Prefer read-only commands first. Inspect before acting.
Use --yes only in deliberate automation paths, never speculatively.
Pair destructive actions with explicit identifiers. No fuzzy matching in the shell.
Re-fetch state after any mutation. Do not trust a prior cache.
Treat exit code 0 as success. Non-zero: capture stderr, retry only on transient failures.

Command groups

Group	Typical use
`system`	`info`, `health`, `status`, `resources`, `uptime`
`array`	`status`, `devices`, `parity`, parity-check actions
`disks`	Inventory, SMART, temp, usage, mount
`containers`	`list`, `inspect`, `logs`, `stats`, lifecycle actions
`notifications`	`list`, `latest`, `get`, `create`, `archive`
`vms`	`list`, `inspect`, lifecycle actions
`shares`	`list`, `get`, usage
`logs`	`list`, `get`, `system`, `tail`, `search`
`services`	`list`, `get`, `status`
`network`	Interfaces, status
`schema`	API introspection
`diagnostics`	`ping`, `latency`, `env`, `doctor`

Workflow: health check

ucli system info --output json --quiet
ucli system health --output json --quiet
ucli array status --output json --quiet
ucli services status --output json --quiet

Fetch each separately. Fail fast on non-zero exits.
Summarize array state, service state, resource pressure, warnings.
Only pull logs if the snapshot shows trouble.

Workflow: container management

# list running
ucli containers list --output json --quiet --fields id,names,state,status --sort names:asc

# inspect one
ucli containers inspect <id> --output json --quiet

# restart
ucli containers restart <id> --yes --output json --quiet

Resolve target by id or names.
Inspect current state.
Execute with --yes when confirmation would block automation.
Re-read status after mutation.

Anti-patterns

Don't parse human-readable output. Always use --output json.
Don't assume partial success from human-readable text. Check exit codes.
Don't retry on non-transient errors (auth, bad arguments, missing resources).
Don't skip --fields on large result sets. Token waste adds up fast.
Don't chain mutations without re-fetching state between them.
Don't use --force unless you understand exactly what it skips.

Configuration

Default config path: ~/.config/ucli/config.yaml

default_profile: lab
profiles:
  lab:
    host: http://192.168.1.10:7777
    apiKey: YOUR_API_KEY
    output: json
    timeout: 30

Prefer --host and --api-key explicitly for isolated jobs, --profile <name> for stable environments.

ucli agent guide

CLI: ucli [global flags] <group> <command> [args...]

Recommended defaults

ucli --output json --quiet <group> <command>

--output json for machine-readable output
--quiet to suppress decorative text
--fields to shrink payloads
--filter and --sort to shape data before it hits your context

Guardrails

Prefer read-only commands first. Inspect before acting.
Use --yes only in deliberate automation paths, never speculatively.
Pair destructive actions with explicit identifiers. No fuzzy matching in the shell.
Re-fetch state after any mutation. Do not trust a prior cache.
Treat exit code 0 as success. Non-zero: capture stderr, retry only on transient failures.

Command groups

Group	Typical use
`system`	`info`, `health`, `status`, `resources`, `uptime`
`array`	`status`, `devices`, `parity`, parity-check actions
`disks`	Inventory, SMART, temp, usage, mount
`containers`	`list`, `inspect`, `logs`, `stats`, lifecycle actions
`notifications`	`list`, `latest`, `get`, `create`, `archive`
`vms`	`list`, `inspect`, lifecycle actions
`shares`	`list`, `get`, usage
`logs`	`list`, `get`, `system`, `tail`, `search`
`services`	`list`, `get`, `status`
`network`	Interfaces, status
`schema`	API introspection
`diagnostics`	`ping`, `latency`, `env`, `doctor`

Workflow: health check

ucli system info --output json --quiet
ucli system health --output json --quiet
ucli array status --output json --quiet
ucli services status --output json --quiet

Fetch each separately. Fail fast on non-zero exits.
Summarize array state, service state, resource pressure, warnings.
Only pull logs if the snapshot shows trouble.

Workflow: container management

# list running
ucli containers list --output json --quiet --fields id,names,state,status --sort names:asc

# inspect one
ucli containers inspect <id> --output json --quiet

# restart
ucli containers restart <id> --yes --output json --quiet

Resolve target by id or names.
Inspect current state.
Execute with --yes when confirmation would block automation.
Re-read status after mutation.

Anti-patterns

Don't parse human-readable output. Always use --output json.
Don't assume partial success from human-readable text. Check exit codes.
Don't retry on non-transient errors (auth, bad arguments, missing resources).
Don't skip --fields on large result sets. Token waste adds up fast.
Don't chain mutations without re-fetching state between them.
Don't use --force unless you understand exactly what it skips.

Configuration

Default config path: ~/.config/ucli/config.yaml

default_profile: lab
profiles:
  lab:
    host: http://192.168.1.10:7777
    apiKey: YOUR_API_KEY
    output: json
    timeout: 30

Prefer --host and --api-key explicitly for isolated jobs, --profile <name> for stable environments.

适合场景

OpenClaw 用户查找和安装 Skill 时

用户想查找某类 Agent Skill 时

需要根据任务场景推荐可安装能力包时

需要对比不同来源的安装命令和来源信息时

能力概览

能力 1

按任务关键词查找相关 Skills

能力 2

展示可复制的安装命令

能力 3

保留来源站点、仓库和原始说明，方便继续核验

能力 4

补充不同宿主或平台的使用分布数据

能力 5

展示第三方安全扫描或审计结果

安装后应在对应宿主中按原始 README 的触发条件使用；具体调用方式请以来源页面和 README 为准。

平台分布

OpenClaw

98.02%

按下载量换算1,247

安全审计

VirusTotal

通过

ClawScan

通过

Static analysis

通过

权限和风险

执行命令

安装流程涉及命令执行，可能通过 openclaw skills install unraid-cli 联网下载 Skill 或依赖。用户安装前应确认命令来源、仓库内容和执行环境。

安装前确认

本站仅展示第三方公开信息，不托管安装包，不提供自动安装或运行环境。安装前应自行审查源码、依赖和命令行为。当前只有一个来源，正式发布前建议补源仓库或其他目录站核验。

来源信息

GitHub 仓库

github.com

/ingodibella/unraid-cli

SKILL.md 来源

clawhub.ai

/ingodibella/unraid-cli

继续浏览同类 Skills

更多研究检索 Skills（73,675）返回 Skills 目录

上一个 Skill

unraid（unraid 搜索）

unraid 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。

下一个 Skill

unreal-engine（unreal 引擎）

unreal-engine 用于查找、检索和筛选相关信息，适合在 Codex、Claude、Cursor、Gemini CLI 中需要根据关键词、任务场景或来源线索快速定位候选结果时使用。可结合来源仓库、安装命令和原始 README 继续核验具体用法。安装前建议确认权限范围、维护状态，以及是否会触发联网、命令执行或文件读写。