O

Skill 详情

openclaw-1panel

用于OpenClaw的一面板操作技巧。当用户希望OpenClaw与一个一面板实例进行交互,以监控资源、网站、证书、应用程序状态、容器状态、日志、定时任务、任务中心记录、节点管理状态以及未来的管理动作时使用。当前实现主要集中在查询和检查接口上,并保留了按模块分组的变更定义以便于后续扩展。

来源平台:ModelScope
来源标识:ModelScope/1Panel-dev/1Panel-skills
源文件:原始说明
AI 平台与模型 热门 ModelScope 高 风险 下载 131访问 1.7千Stars 6 ModelScopeGitHub Copilot
来源平台ModelScope
文档版本master
热度热门
排名信号下载 131
概述 安装 文档 下载

快速判断

用于OpenClaw的一面板操作技巧。当用户希望OpenClaw与一个一面板实例进行交互,以监控资源、网站、证书、应用程序状态、容器状态、日志、定时任务、任务中心记录、节点管理状态以及未来的管理动作时使用。当前实现主要集中在查询和检查接口上,并保留了按模块分组的变更定义以便于后续扩展。

最后校验2026-05-18
来源平台ModelScope
安全提示
下载副本ZIP 可用

适合任务

  • 按 ModelScope 收录说明完成平台、开发或工作流任务。
  • 通过下载包离线保存 Skill 内容。
  • 结合下载量、访问量和喜欢数评估优先级。

输入与输出

输入:任务目标、上下文材料、平台信息、文件路径、约束条件或需要处理的内容。

输出:按 Skill 说明生成的文档、代码、检查结果、计划、建议或操作步骤。

示例任务

  • 使用 openclaw-1panel 帮我完成当前任务,并先确认必要上下文。
  • 根据 openclaw-1panel 的说明,列出操作步骤和风险检查点。

安装方式

  1. 下载本站提供的 Skill ZIP 并解压。
  2. 把解压后的 Skill 目录放入当前 AI 工具支持的 skills 目录。
  3. 如需在线查看原始内容,可打开 GitHub 的 SKILL.md

在线原始地址:modelscope-1panel-dev-1panel-skills/SKILL.md

风险边界

使用前请检查权限、外部依赖和要处理的数据类型。第三方平台数据、支付、部署、账号和密钥相关内容应先核对官方说明。

SKILL.md 文档介绍

OpenClaw 1Panel

Overview

Use this skill to interact with a 1Panel instance through authenticated HTTP API calls. The bundled resources are TypeScript source files grouped by module, with query-oriented actions implemented now and mutation endpoints reserved for later expansion.

Requirements

  • Require a 1Panel API key with access to the target instance.
  • Require these environment variables when executing the TypeScript resources in an OpenClaw runtime:
  • ONEPANEL_BASE_URL
  • ONEPANEL_API_KEY
  • optional: ONEPANEL_TIMEOUT_MS
  • optional: ONEPANEL_SKIP_TLS_VERIFY=true

Workflow

1. Choose the module that matches the user's request.

2. Start with a list or search action to identify the exact target.

3. Read detail, status, or logs only after the target is confirmed.

4. If the user asks for create, update, delete, restart, stop, or any other mutation:

  • do not fabricate or guess a write workflow
  • surface the matching reserved mutation endpoint from the module
  • implement the write path only when that behavior is intentionally added to the skill

Module Groups

  • monitoring

Resource monitoring, dashboard current status, top processes, historical monitor data, GPU history.

  • websites

Website list/detail, Nginx config reads, domain list, HTTPS config, SSL certificate reads, website log reads.

  • apps

App catalog lookup, installed app list, installed app detail, service list, port/connection info.

  • containers

Container list/status/detail, inspect, stats, streaming log reads.

  • logs

Operation logs, login logs, system log file list, generic line-by-line log reads.

  • cronjobs

Cronjob list/detail, next execution preview, execution records, record log reads.

  • task-center

1Panel task-center list and executing count.

  • nodes

Node list, simple node list, node options, node summary. Some endpoints may require Pro/XPack.

Resources

  • [references/module-groups.md](references/module-groups.md)

Human-readable overview of module boundaries, common entrypoints, and reserved write scope.

  • [scripts/client.ts](scripts/client.ts)

Shared authenticated 1Panel client.

  • [scripts/cli.ts](scripts/cli.ts)

Executable CLI entry for OpenClaw or shell-based tool calls.

  • [scripts/index.ts](scripts/index.ts)

Registry of all module definitions.

  • scripts/modules/*.ts

Module-specific actions and reserved mutation endpoint definitions.

Execution Notes

  • Prefer the CLI instead of letting the model construct signed HTTP requests itself.
  • The repository can ship prebuilt runtime files under dist/, so normal use should call node dist/scripts/cli.js ... directly without rebuilding first.
  • Run npm run build only after changing TypeScript source files such as plugin.ts or scripts/**/*.ts.
  • OpenClaw plugin loading should target the compiled entry at dist/plugin.js, not the TypeScript source file.
  • If the OpenClaw runtime can execute TypeScript directly, import from [scripts/index.ts](scripts/index.ts) and call the module actions.
  • If the runtime cannot execute TypeScript directly, use the TypeScript files as the source of truth for methods, paths, query parameters, and request payload shapes.
  • The current implementation focuses on query and inspection actions; extend the reserved mutation definitions when you intentionally add managed write flows.
建议反馈